integration

How PagerDuty integrates with AppDynamics, Micro Focus, ServiceNow, and Splunk

How PagerDuty integrates with AppDynamics, Micro Focus, ServiceNow, and Splunk

At its core, PagerDuty is an incident management platform targeted at people in IT Operations. However, it can be extended and used for more than just alerting, incident escalation, and rostering. 

Using PagerDuty’s machine learning algorithms, you can take alerts from disparate vendors, tools, and sources to reduce noise so incident responders can start working on what’s important to ensure your IT works.

The good news is, PagerDuty integrates with all four of our premier partners at JDS: AppDynamics, Micro Focus, ServiceNow, and Splunk. Some out-of-the-box integrations exist, for a start. However, by accessing our expert integration specialists, you can explore even more functionality and integrations between PagerDuty and your enterprise software.

Here’s an overview of how PagerDuty works with each of our premier partners.

AppDynamics integration

There is an AppDynamics integration for use with PagerDuty. If you already have alerting and health rules setup in AppDynamics, it is simple to extend the alerting using the extension. Learn more.

AppDynamics not only integrates with PagerDuty, the company uses PagerDuty in their IT operations for incident management. See this webpage to learn how AppDynamics use PagerDuty to reduce incident times.

Micro Focus integration

PagerDuty integrates with Micro Focus SiteScope and uses email to send alerts to PagerDuty. By configuring the SiteScope alerts to send information to PagerDuty, you can leverage the powerful machine learning processes to help triage future incidents and reduce time to resolution. See this webpage for details.

ServiceNow integration

There is a bi-directional integration between ServiceNow and PagerDuty. Incidents can be acknowledged, delegated, and resolved in either system. There are a few steps involved in this, but our expert technical consultants can help you set it up properly in your ServiceNow instance. Learn more.

Splunk integration

PagerDuty comes with an out-of-the-box Splunk integration. By installing the PagerDuty Splunk app, you can reduce noise from Splunk alerts by correlating the alerts under one incident. Alert correlation can be done in the fields in Splunk, including component, host, source, or by the search name. See this video for an overview of how to set up this integration.

Try it for free

Haven’t yet tried PagerDuty? Register for a two-week free trial today and we’ll help ensure you embrace all the functionality this excellent major incident response tool has to offer.

Our team on the case

Just do it.

Chris Barbour

Consultant

Length of Time at JDS

2.5 years

Skills

AppDynamics, Splunk, CA UIM, HP VuGen, Web Development, CSS, NodeJS, Java, .NET, SQL

Workplace Passion

Application Performance Monitoring, Infrastructure monitoring, Business Analytics and Dashboarding

Ensure IT works.

Ryan Castles

Consultant

Length of Time at JDS

8 years

Skills

Consulting in application performance management across AppDynamics, CA, HPE and Splunk products.

Workplace Passion

Enabling customers to quickly triage application performance problems and outages.

When you've had enough sleep, an impossible task becomes an interesting challenge.

Jillian Hunter

Support Consultant

Length of Time at JDS

1.5 years

Skills

ServiceNow, HP ALM/QC, Historical fencing.

Workplace Solutions

Supporting both our clients and our own consultants.

Our PagerDuty stories

Posted by Amy Clarke in AppDynamics, Micro Focus, PagerDuty, ServiceNow, Splunk, Tech Tips
Integrating OMi (Operations Manager i) with ServiceNow

Integrating OMi (Operations Manager i) with ServiceNow

We have delivered Micro Focus solutions and migrated "Operations Manager for Windows" (OMW) to the innovative new OMi for a number of customers. In most of these cases, the requirement was also to integrate ServiceNow—a request that has been growing in popularity. In each case where JDS has provided OMi to ServiceNow integration, it has proven successful and satisfying for our customers.

OMi has been tested over time, built on a firm foundation. It is robust in design and suitable for every known event and service model situation possible. The possibilities are endless and the GUI is customisable—and as for the designs provided out-of-the-box, they are a fully featured event and service model, driven to work well from the operations and support personnel perspectives.

The integration with ServiceNow is relatively straightforward and simple. It requires a little groovy script programming knowledge. Generally speaking, someone who has an intermediate breadth in JavaScripting can sufficiently develop a connector script. The script is set under the Connected Servers option in the managed scripts.

There are some examples provided; one in particular is the "LogFile Adapter", and with the use of the OMi extensibility guide, these examples can easily translate into useful real-world cases.

You will need to create an account in ServiceNow and enable the "Web service access" role to be allowed to make Web service API protocol calls. Additionally, you will need an account in OMi in order for ServiceNow to interact with OMi WebServices.

Once the OMi connected server to ServiceNow is enabled, Event Forwarding rules can be tailored to use simple event filtering. These filters are used to select and automate events for forwarding and synchronisation with the Connected Server. As an additional option, the integration allows you to right-click on an event and manually transfer it to ServiceNow for incident creation and synchronisation.

With this sample filter shown here, the selection is made when an event matches the filter as a critical event with any lifecycle state that has the priority either set to highest, high, or unknown will be forwarded.

In ServiceNow, it's good practice to have an import table where a transformation map is executed, thereby transforming the forwarded event values to matching values in the ServiceNow incident table. A ServiceNow Business Rule can also be applied to further shape the event data before it's inserted into the incident table.

An example of an import table containing the event data fields we want to transform is below:

Here is an example of a transformation map source field for “description”. The target is set for the incident table to match on the target field “description”.

The incident table can be modified to include the OMi event ID field and be transformed similarly as the description example as shown above. This is important so that the incident can be identified easily as originating from OMi. A Business Rule can check for this field if it contains a GUID value. If an event ID GUID exists in the incident omi_id field, the Business Rule advanced actions can be triggered based on the conditions to sync any changes to the incident back to the event in OMi.

The change of the incident Status, Priority, Assigned to, Description, Cause, Work Notes (Annotation), etc. can match that from the ServiceNow incident back to the event’s fields in OMi.

Once the incident in ServiceNow is closed, a Business Rule can trigger the closure of the event and provide:

  • The Work Notes to the event annotation
  • Resolution notes to the solutions field
  • Resolution code to the description field back to the event in OMi

In ServiceNow, when we solve the incident and close it, the incident that was created by the OMi integration will then note the state is set to Closed.

The incident Work Notes are required each time an update to the incident is made and are also added.

Upon incident closure, you are required to populate the incident resolution fields.

After the operator submits and updates the incident, the Business Rule for an OMi generated incident is triggered to then sync the incident details back to the Event and closes it.

The event is closed by an outgoing WebService request from ServiceNow Business Rule that call a REST Message with an xml payload in a REST POST to OMi.

The Solution here is updated by the incident’s resolution information.

Event annotation is updated by the incident’s Work Notes.

Event history details showing the flow of updates to the event that occurred.

In summary, keeping the event in sync with ServiceNow ticketing system is relatively simple. OMi can forward events to an external event processing server via Connected Servers. This clearly makes integrating event management systems with ticketing systems an all-round solid solution to tracking events and incidents. Some JavaScripting is required, along with an in-depth OMi and ServiceNow product knowledge.

JDS has several consultants on the team with this combination of skills and knowledge, and we would be happy to discuss implementing a similar solution for your organisation at any time.

Our team on the case

Be open and friendly, engaging, and always add value.

Jim Tsetsos

Consultant

Length of Time at JDS

2.5 years

Skills

IT: HPE OMi, OMW, OMU, BSM, Sitescope, VuGen, Operations Agent, Service Manager, HP-UX, Solaris, Linux, Windows, SQL and ITIL.

Personal: Playing guitar, sound engineering, photography, chess, reading.

Workplace Solutions

Infrastructure/Application Performance and Availability Monitoring.

Tech tips from JDS

Posted by Amy Clarke in AppDynamics, Micro Focus, PagerDuty, ServiceNow, Splunk, Tech Tips
Vugen and GitHub Integration

Vugen and GitHub Integration

With the release of LoadRunner 12.53, VuGen now has built in GitHub integration. That means you not only have access to GitHub for saving versions of your script, but also other tools like bug tracking, access control and wikis.

Here’s an overview to VuGen’s GitHub integration to get you up and running.

Getting Started

First off, you’ll need a personal Git login. You can sign up for free at github.com/join.  Note that free repositories are publicly available.

You’ll also need LoadRunner 12.53 or higher from HPE.

GitHub Overview

VuGen’s GitHub integration (and GitHub in general) works by managing three versions of your script at a time.

Vugen and GitHub Integration 1

  1. The one you see in VuGen is your working copy. You can develop / replay your script as usual, and save it locally when you want.
  2. When you want a backup of your script – e.g. before doing correlation or rerecording, you can make a check point – or commit the script. This saves the script to a local staging area.
  3. After several commits, or perhaps at the end of the day, you might be ready to save everything to GitHub. To do this you Push the script.

Using GitHub integration straight from VuGen

The following example shows you how to push your first VuGen script to GitHub.

1. Starting out – Creating a Repository

Log into GitHub and create a new repository:

Vugen and GitHub Integration 2

Fill in the details and click “Create Repository”. With a free GitHub account the script will be publicly available, with a paying account you can make it private.

Vugen and GitHub Integration 3

2. VuGen Version Control – Create Local Git Repository
Now create a script in VuGen – in our example it’s ‘BankofSunshine’.

You’ll see a new ‘Version Control’ menu available in VuGen. Chose the option to ‘Create a local Git Repository’.

Vugen and GitHub Integration 4

VuGen manages the files to include so you don’t need to create a .gitignore file. If you prefer to manage it yourself, you can do that too.

3. Commit Changes to the Staging Area

Now you need to commit your script to the local repository. Do this each time you’ve made changes that you might want to push to Git Hub, or if you want to be able to roll back any changes.

When you commit, your local repository is ready to be pushed up to GitHub – but is still only available to you.

Vugen and GitHub Integration 5

4. Push Changes to GitHub

Once you are ready to save your script up to GitHub, you will need to Push the changes.

The first time you do this with your script you will need to tell VuGen some details about the GitHub repository.

Enter your details that you created in Step 1:

Vugen and GitHub Integration 7

Now your newly created script is saved to GitHub.

5. There’s no step 5.

That’s all you need to do. When you go to GitHub and click on your repository, you will see all the files that you just pushed:

Vugen and GitHub Integration 8

To keep track of changes made locally to the script, VuGen will show you which files have updated with a red tick:

Vugen and GitHub Integration 9

While you can access your scripts in ALM from the Controller, you can’t yet access your scripts in GitHub from the Controller. You’ll need to pull down a local copy before you run your test.

Now you are up and running, how about exploring more of what GitHub has to offer. Each script saved to GitHub comes with a Wiki and issues register. These could come in handy when you have large or tricky scripts or for handover to another team

Share your thoughts on VuGen GitHub integration below.

Posted by Daniel Spavin in Micro Focus, Tech Tips