AlertOps and BMC Software Integration

You can now send alerts from Remedy to AlertOps using our Generic Email API.

Depending on what version of Remedy you have, you may also use the Generic Rest API. AlertOps will automatically create new incidents when it receives an alert with problem status. AlertOps will automatically close the alert when it receives the ok status.

You can send several fields from Remedy to AlertOps:

• Source URL: So users can click a link in AlertOps and go straight to the ticket in Remedy
• Assignee Email: Send the ticket owner to AlertOps and AlertOps will assign the owner
• Recipient User: Specify the user who will receive the alert
• Recipient Group: Specify the group to receive the alert
• Topic: Specify the alert topic, which AlertOps can use to assign the alert
• Bridge number: Pass along a bridge number to be dialed so users can one-click to access a conference
• Bridge Access Code: Specify the access code for connecting to the conference bridge

Learn how to configure Remedy to AlertOps, learn more about AlertOps’ Generic API and ourOutbound API.

These are just some of the things you can do with BMC Software when it’s integrated with AlertOps. AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day! If you’re new to AlertOps sign up for afree trial to get started today!

AlertOps and BMC Software Integration

Discover How Powerful the New Relic Integration Is!

New Relic is one of our most requested integrations and it is here! New Relic is a unique platform that allows Dev and Ops teams to watch all aspects of the software as it runs. It allows you to leverage your alerting and collaboration by integrating New Relic with AlertOps. New Relic and AlertOps will work tirelessly on every part of your software instantaneously from performance of your applications to the customer experience.

In today’s IT operations world, performance is more critical than ever before.  With internet facing customer sites, internal facing customer sites, web services, FTP services, you’re getting popped and pinged from every direction, that’s why you need to use a tool like New Relic because you need to know when any of your critical systems go down and when they come back up.

AlertOps and New Relic can make you life better! You can route your New Relic web hook notifications to AlertOps, using our generic Rest API and rest easy knowing that the notifications will get to the right person or team and with the right level of urgency.  New Relic and AlertOps users get application performance with the ability to collaborate issues as they occur.  This helps by reducing time to resolution and saving the company money.  When New Relic sends the “closed” status notification AlertOps will shut down the alert.

These are just a few examples of the New Relic and AlertOps integrations. AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

Enjoy the powerful experience of the New Relic integration.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

Discover How Powerful the New Relic Integration Is!

Why We Love Slack Integration (And You Should, Too!)

Slack is a chat service team communication platform aimed to “make your work life simpler, more pleasant and more productive.”  Slack uses real time messaging, archiving and search features to live up to their mission statement.

AlertOps with Slack integration allows you to create three-way integrations: connecting your monitoring tools, service desk and slack to your teams all within AlertOps.  The Slack integration gives you stronger communication and collaboration between teams.

Now when an alert is received from your monitoring tool, AlertOps will send a notification to your team on their Slack channel. AlertOps will then open the incident in your service desk.  AlertOps will then consult the team’s on-call schedule and alert the primary on-call person using voice, text and email.  AlertOps will use the team’s on-call schedule if the primary person does not take the assignment, alerting each person until the alert is answered.  In Slack a user can take an assignment, and when they do AlertOps will update the incident in your service desk and show the assignment.  When an incident is closed in Slack, AlertOps will close the incident in your service desk.

Once you connect Slack to AlertOps you create a flow of conservations, alerts and monitoring data.  The synchronized conservations and tools help to make the transition easier.  AlertOps integration with Slack allows you to have access to the most current platform of Slack.

These are just a few examples of the Slack and AlertOps integrations.  AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

Learn how to configure the Slack to AlertOps integration.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

Why We Love Slack Integration (And You Should, Too!)

AlertOps Workflows

Workflows in AlertOps are escalations on steroids!

Incident management often involves several workflows for a single incident. Workflows are usually triggered by an event, such as a change in status. Or they are time based, triggered by the passage of specific amount of time, such as before or after conditions.  But so many incident management systems are missing this simple but effective functionality.  Most systems include escalations, that usually looks some thing like this:

1. 30 minutes after notifying Tom, notify Jeff.
2. 30 minutes after notifying Jeff, notify Sally.
3. And so on…

AlertOps includes a workflow engine, and we built all of our escalations using this engine.  At the end of the day, a workflow usually ends up sending a notification to someone.

Here is an out-of-the-box workflow to notify the manager, before SLA if an incident is still unresolved.

Here is a workflow to resolve a JIRA issue when AlertOps incident is closed.

With AlertOps you can just as easily send a notification or message to a system such as JIRA when an incident occurs. Like when an incident is created, updated or resolved. But why stop with sending notifications to people? Why not send notifications to systems as well? When an incident is created, open an issue with JIRA. When an incident is assigned update the issue status in JIRA. When the incident is resolved, close the status in JIRA. You can do all of this in AlertOps not only with JIRA, but with any other system with a Rest API. All you need to do is configure the outbound integration in AlertOps to send the necessary messages to JIRA or any external systems and then plug the calls into workflows.

These are just some of the possibilities of what you can do with workflows in AlertOps. AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day! If you’re new to AlertOps sign up for afree trial to get started today!

AlertOps Workflows

AlertOps Integration with Amazon Web Service Cloud Watch

AlertOps is integrated with Amazon Web Service Amazon Cloud Watch, a monitoring service for AWS recourses on the application.  You can use AWS Cloud Watch and AlertOps to collect and track metrics, monitor log files, set alarms and automatically react to changes in your AWS resources.

You can now send alerts from AWS Cloud Watch to AlertOps using our generic Rest API.  AlertOps will automatically create a new incident when it receives an alert with alarm status.  AlertOps will automatically close the alert when it receives the OK status.

In AlertOps you can craft a custom message to be sent out with the alert using any field from the inbound JSON.  You can map any inbound field to a custom field in AlertOps.  You can also map any inbound field in AlertOps and use topics to track incidents and also to route incidents to teams, allowing you to send multi-channel alerts of text, voice, email and mobile push notifications.  You can enable escalations and workflows.

You can route the alert to other systems, such as ticketing systems.  These are just some of the things you can do with Amazon Web Services Cloud Watch when it’s integrated with AlertOps. AlertOps has many features to make your incident management life easier: multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

Experience and configure the Amazon Web Service Cloud Watch and AlertOps integration.  Learn more about AlertOps Generic Rest API and AlertOps Outbound API.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day! 

If you’re new to AlertOps sign up for a free trial to get started today!

AlertOps Integration with Amazon Web Service Cloud Watch

Think You’re Cut Out for HipChat Integration?

HipChat is a chat service team communication platform aimed to make your work life simpler, more pleasant and more productive. Persistent, searchable, and loaded with goodies: video calling, screen sharing, and the security your IT team craves.

AlertOps with HipChat integration allows you to create three-way integrations: connecting your monitoring tools, service desk and HipChat to your teams all within AlertOps.  The HipChat integration gives you stronger communication and collaboration between teams.

Now when an alert is received from your monitoring tool, AlertOps will send a notification to your team on their HipChat channel. AlertOps will then open the incident in your service desk.  AlertOps will then consult the team’s on-call schedule and alert the primary on-call person using voice, text and email.  AlertOps will use the team’s on-call schedule if the primary person does not take the assignment, alerting each person until the alert is answered.  In HipChat a user can take an assignment, and when they do AlertOps will update the incident in your service desk and show the assignment.  When an incident is closed in HipChat, AlertOps will close the incident in your service desk.

Once you connect HipChat to AlertOps you create a flow of conservations, alerts and monitoring data.  The synchronized conservations and tools help to make the transition easier.  AlertOps integration with HipChat allows you to have access to the most current platform of HipChat.

These are just a few examples of the HipChat and AlertOps integrations.  AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

Learn how to configure the HipChat to AlertOps integration.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

Think You’re Cut Out for HipChat Integration?

AlertOps and Nagios Integration

You can send alerts from Nagios to AlertOps using our Generic Email API.

AlertOps will automatically create new incident when it receives an alert with PROBLEM status.

AlertOps will automatically close the alert in when it receives the OK status.

AlertOps has many features to make your incident management life easier: multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLA-based severity management, and much more.

To learn more about Nagios, click here.

To learn how to configure the Nagios to AlertOps integration, click here.

To learn more about the AlertOps Generic Email API, click here.

To learn more about the AlertOps Outbound API, click here.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

AlertOps and Nagios Integration

AlertOps Team Management for Enterprises

Managing thousands of users across hundreds of teams doesn’t need to create administrative headaches for your support teams.  Delegated administration, exchange synchronization and bulk imports can automate and simplify your world.

AlertOps’ team management for enterprises delegated administration gives role-based security, allowing you to delegate team administration tasks to delegated team admins.

AlertOps’ team management for enterprises allows exchange synchronization integration. You can automate your group member changes by pushing any changes from your premise-hosted exchange to your AlertOps cloud instantly.

AlertOps’ team management for enterprises has a multi-team hierarchy that allows trouble-shooting of major incidents. Sometimes those incidents require a multi-team approach. AlertOps multi-team hierarchy support makes this easy, allowing you to combine in-house teams and out sourced teams together within a single team and delegate administration to each group.

AlertOps’ team management for enterprises allows you to perform bulk imports. You can import users, groups and group user assignments using excel templates.  You can also use the same templates for doing bulk updates.

AlertOps’ team management for enterprises offers team contacts. If your team members share a pager, or whether your teams have designated chat channels or simply designated phone or email. AlertOps allows you to assign teams or group contacts.

These are just a few examples of the AlertOps team management for enterprises. AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

AlertOps Team Management for Enterprises

AlertOps and JIRA Integration

Whether you are using JIRA for issue tracking or as a service desk tool, you can easily integrate your tool with AlertOps.

• You can create two-way integrations using JIRA and AlertOps.
• You can send alerts from JIRA to AlertOps using our Generic REST API.
• You can create the following scenarios:
• When a JIRA Issue is created, create an AlertOps alert.
• When an issue is assigned in JIRA, assign the owner in AlertOps.
• When an issue is closed in JIRA, close the alert in AlertOps.
• When an alert is created in AlertOps, create an issue in JIRA.
• When an alert is assigned in AlertOps, update the issue in JIRA.
• When an alert is closed in AlertOps, close the issue in JIRA.
• Allow the user to click a link in the AlertOps alert detail and go directly to AlertOps.

These are examples of just some of the things you can do with JIRA and AlertOps.

AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLA-based severity management, and much more.

To learn more about JIRA, click here.

To learn how to configure the JIRA to AlertOps integration, click here.

To learn more about the AlertOps Generic REST API, click here.

To learn more about the AlertOps Outbound API, click here.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

AlertOps and Jira Integration

AlertOps and Service Now Integration

Using Service Now and AlertOps you can create two-way integrations.  Service Now allows you to send alerts to AlertOps using the Generic Rest API.  You can do this using any of Service Now’s modules and you can send any field from Service Now.  You can also send messages to Service Now from AlertOps using the Outbound API.

Using these features you can create powerful automation scenarios!

• When a critical Service Now incident is created, create an AlertOps alert
• When an AlertOps alert is created, create a Service Now incident
• When an alert owner is assigned in AlertOps, update the status in Service Now
• When an incident owner is assigned in Service Now, update the owner in AlertOps
• When the alert is closed in AlertOps, close the incident in Service Now
• When an incident is closed in Service Now, close the alert in AlertOps

These are just some examples of ways you can make Service Now and AlertOps talk to each other.  This can all be done without writing any code.

To learn more about Outbound Services click here

To learn more about Workflows click here

To learn more about Message Rules click here

To learn more about custom fields click here.

To learn more about the Generic REST API click here.

These are just some of the things you can do with Service Now when it’s integrated with AlertOps. AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day!  If you’re new to AlertOps sign up for afree trial to get started today!

AlertOps and Servicenow Integration

AlertOps Service Management for Enterprise

Service management is usually treated as escalations in other alert management tools.  But at AlertOps, we recognize that there is a much more to it than simple call trees.  SLA based escalations, workflows and more can make AlertOps an integral part of your critical incident management ecosphere.

AlertOps’ service management for enterprises will notify stakeholders.  Whether they work for another department in your organization, or whether they are a customer or even a regulatory agency.  Sometimes you need to notify people besides your support team when a major incident occurs.  AlertOps workflows can automate this process to ensure the message goes out every time, on time.  You can send regular status updates as well as closure updates.

AlertOps’ service management for enterprises workflows can manage your service level escalations.  Allowing you to send reminders to incident owners at regular intervals or send reminders based off of an SLA deadline.  Workflows can also trigger notifications to systems as well as to people.  You can trigger other flows as well, such as change control processes needed to resolve a major incident.

AlertOps’ service management for enterprises allows you to define global SLAs based on priority or severity levels.  You can also create overrides as needed.  Use SLA based management in AlertOps to trigger time based escalations and notifications off of you SLAs.

AlertOps’ service management for enterprises message rule and workflow engines give you the flexibility to configure and enhance your incident management solutions to fit your needs.

These are just a few examples of the AlertOps service management for enterprises.  AlertOps has many features to make your incident management life easier; multi-modal communication, teams with on-call schedules, customizable message routing rules, customizable workflows and escalations, SLAs based severity management and much more.

At AlertOps we offer over 30 of the top third party integrations for monitoring, service desk, hosting and chat tools and we are adding more every day! Contact sales@alertops.com or call (844) 292-8255 or sign up for a free trial to get started today!

AlertOps Service Management for Enterprise

Do You Need to Notify Your Customers When Personal Information is Leaked Due to a Data Breach?

Has your corporation been targeted for consumers’ personal information during a data breach? With the current announcements of personal information data breaches, it seems to be happing quite frequently.  Some of the most known personal information data breaches are: Anthem,Ashley Madison, EBay, JP Morgan Chase, Sony Pictures Entertainment, and Tricare.

The most recent announcement came from Verizon Enterprise Solutions data breach, their massive data breach affected more than 1.5 million customers of their computer security wing.  This breach caused a major ripple effect since this particular division of Verizon helps other corporations when they are victims of data breaches.

When a data breach occurs, according to the Security Breach Notification Laws,

“Forty-seven states, the District of Columbia, Guam, Puerto Rico and the Virgin Islands have enacted legislation requiring private, governmental or educational entities to notify individuals of security breaches of information involving personally identifiable information.  Security breach laws typically have provisions regarding who must comply with the law (e.g., businesses, data/ information brokers, government entities, etc); definitions of “personal information” (e.g., name combined with SSN, drivers license or state ID, account numbers, etc.); what constitutes a breach (e.g., unauthorized acquisition of data); requirements for notice (e.g., timing or method of notice, who must be notified); and exemptions (e.g., for encrypted information).”

How do cybercriminals target devices for the data that they store?  It’s based on how easy you are to exploit and how clear of a path you have to critical systems and valuable data.  Malware was a factor in over 50% of all personal information data breaches.  The cybercriminals use it as part of the initial compromise in order to capture the valuable data thus allowing them to “leapfrog” into other systems and extract the info and cover their tracks.

AlertOps has multiple ways to notify you; although we can’t stop a person information data breach from happening we can ensure that you receive the proper notifications to manage the service levels.  With AlertOps’ workflows helping to manage escalations, so if and when a data breach occurs, AlertOps can trigger notifications to people and systems simultaneously.  AlertOps will send reminders to the incident owners at regular intervals along with sending reminders based off of an SLA deadline.  Allowing you to trigger other flows, such as changing the control processes needed to resolve major data breach incidents.

AlertOps’ SLAs are set based on priority and severity levels, which allows you to create over rides when needed.  AlertOps’ message rules and workflow engines give you the flexibility to configure and enhance your incident management solution to fit your needs and prevent personal information data breaches.

State	Citation
Alaska	Alaska Stat. § 45.48.010 et seq.
Arizona	Ariz. Rev. Stat. § 44-7501
Arkansas	Ark. Code § 4-110-101 et seq.
California	Cal. Civ. Code §§ 1798.29, 1798.80 et seq.
Colorado	Colo. Rev. Stat. § 6-1-716
Connecticut	Conn. Gen Stat. § 36a-701b, 2015 S.B. 949, Public Act 15-142
Delaware	Del. Code tit. 6, § 12B-101 et seq.
Florida	Fla. Stat. §§ 501.171, 282.0041, 282.318(2)(i)
Georgia	Ga. Code §§ 10-1-910, -911, -912; § 46-5-214
Hawaii	Haw. Rev. Stat. § 487N-1 et seq.
Idaho	Idaho Stat. §§ 28-51-104 to -107
Illinois	815 ILCS §§ 530/1 to 530/25
Indiana	Ind. Code §§ 4-1-11 et seq., 24-4.9 et seq.
Iowa	Iowa Code §§ 715C.1, 715C.2
Kansas	Kan. Stat. § 50-7a01 et seq.
Kentucky	KRS § 365.732, KRS §§ 61.931 to 61.934
Louisiana	La. Rev. Stat. §§ 51:3071 et seq., 40:1300.111  to .116
Maine	Me. Rev. Stat. tit. 10 § 1347 et seq.
Maryland	Md. Code Com. Law §§ 14-3501 et seq., Md. State Govt. Code §§ 10-1301 to -1308
Massachusetts	Mass. Gen. Laws § 93H-1 et seq.
Michigan	Mich. Comp. Laws §§ 445.63, 445.72
Minnesota	Minn. Stat. §§ 325E.61, 325E.64
Mississippi	Miss. Code § 75-24-29
Missouri	Mo. Rev. Stat. § 407.1500
Montana	Mont. Code §§ 2-6-1501 to -1503, 30-14-1701 et seq., 33-19-321
Nebraska	Neb. Rev. Stat. §§ 87-801, -802, -803, -804, -805, -806, -807
Nevada	Nev. Rev. Stat. §§  603A.010 et seq., 242.183
New Hampshire	N.H. Rev. Stat. §§ 359-C:19, -C:20, -C:21; 189:66
New Jersey	N.J. Stat. § 56:8-161, -163
New York	N.Y. Gen. Bus. Law § 899-aa, N.Y. State Tech. Law 208
North Carolina	N.C. Gen. Stat §§ 75-61, 75-65
North Dakota	N.D. Cent. Code §§ 51-30-01 et seq., 51-59-34(4)(d)
Ohio	Ohio Rev. Code §§ 1347.12, 1349.19, 1349.191, 1349.192
Oklahoma	Okla. Stat. §§ 74-3113.1, 24-161 to -166
Oregon	Oregon Rev. Stat. § 646A.600 to .628, 2015 S.B. 601, Chap. 357
Pennsylvania	73 Pa. Stat. § 2301 et seq.
Rhode Island	R.I. Gen. Laws § 11-49.2-1 et seq., 2015 S.B. 134, Public Law 2015-138, 2015 H.B. 5220, Public Law 2015-148
South Carolina	S.C. Code § 39-1-90, 2013 H.B. 3248
Tennessee	Tenn. Code § 47-18-2107; § 8-4-119 (2015 S.B. 416, Chap. 42)
Texas	Tex. Bus. & Com. Code §§ 521.002, 521.053; Tex. Ed. Code § 37.007(b)(5); Tex. Pen. Code § 33.02
Utah	Utah Code §§ 13-44-101 et seq.; § 53A-13-301(6)
Vermont	Vt. Stat. tit. 9 § 2430, 2435
Virginia	Va. Code § 18.2-186.6, § 32.1-127.1:05, § 22.1-20.2
Washington	Wash. Rev. Code § 19.255.010, 42.56.590, 2015 H.B. 1078, Chapter 65
West Virginia	W.V. Code §§ 46A-2A-101 et seq.
Wisconsin	Wis. Stat. § 134.98
Wyoming	Wyo. Stat. § 40-12-501 et seq.
District of Columbia	D.C. Code § 28- 3851 et seq.
Guam	9 GCA § 48-10 et seq.
Puerto Rico	10 Laws of Puerto Rico § 4051 et seq.
Virgin Islands	V.I. Code tit. 14, § 2208

Do you need to notify your customers when personal information is leaked due to a data breach?