One of the most popular features Logz.io provides its users with is the built-in alerting mechanism. Coupled with the rich indexing and querying capabilities that are part and parcel ofElasticsearch andKibana, Logz.io Alerts is a powerful tool to have on your side in day-to-day operations.
This article will introduce you to some of the latest updates to the feature applied over the past few weeks, namely — the ability to trigger alerts on field aggregations and the new integration with PagerDuty.
Integrating with PagerDuty
For starters, I’m going to describe how to integrate Logz.io with PagerDuty. The result of the steps described below is an ability to get alerted when specific conditions that you define are triggered in yourELK Stack environment via PagerDuty.
Retrieving a PagerDuty Service Key
We will start with a crucial element required for integrating Logz.io with PagerDuty — the service key. PagerDuty service keys are basically integration API keys that are required for integrating with PagerDuty services.
To retrieve a service key, first log into PagerDuty and go to Configuration | Services .
You now have the choice of either using an existing service or creating a new one. As a best practice and for the sake of order and segregation of services, I recommend creating a new service for integrating with Logz.io.
To do this, click Add New Service (if you want to add the Logz.io integration to an existing service, select it from the list of services, go to Integrations , and click New Integration ).
Name the new service, and in the Integration Settings section select the Use our API directly option.
There are some additional settings to services, such as escalation policy and incident timeouts, but for now you can do with the default settings.
To create the service, name the new integration, and hit the Add Service button at the bottom of the page.