Documentation forLoggly

Alert Endpoints

Our alert notification methods are versatile. We support several methods for sending notifications:

  1. Email a user on your Loggly account
  3. PagerDuty
  4. Slack
  5. Microsoft Teams
  6. VictorOps
  7. GitHub
  8. OpsGenie

If there are other alert integrations you’d like to see, please leave a comment below.

You can establish multiple endpoints in your account and configure alerts in your system to terminate at different endpoints. Alert endpoints are shared across your account so you can also utilize endpoints that other users have set up. This section reviews how to set up your endpoints.

Alert endpoints can be configured during the Alert setup or separately from the Alert Endpoint page.

Email Notifications

An email will be sent to any users that are configured to receive a notification on a triggered event. If the alert is configured to check for events every minute, an email will be sent every minute while the alert is triggered.

Email recipients must be registered Loggly users.

HTTP Endpoints

If you’d like to integrated Loggly alerting with your own notification services, provide a URL and choose whether to send a POST or GET request. It will send an event as a JSON object. Here is an example output with the 10 most recent events turned off.

  "alert_name" : "IndexOutOfBounds Exception",
  "edit_alert_link" : "",
  "source_group" : "N/A",
  "start_time" : "Mar 17 11:41:40",
  "end_time" : "Mar 17 11:46:40",
  "search_link" : "",
  "query" : "* ",
  "num_hits" : 225,
  "recent_hits" : [ ],
  "owner_username" : "sample",
  "owner_subdomain" : "sample",
  "owner_email" : ""


PagerDuty is a 3rd party service that provides sanity to your escalation policies (among other features). If you’ve already got a PagerDuty account, this integration will help keep your notifications in one place. Simply provide a PagerDuty generic API key, which can be created on the PagerDuty Services page. Add a new service with a "Generic API System" service Type. Supply the Loggly Alert endpoint setup with that API Key. See PagerDuty Integration for more information.



Loggly provides Slack integration for sending alerts to a Slack channel. Loggly supports sending static alert messages to Slack and we can also insert data from the alert into the message.

Microsoft Teams

Loggly provides Microsoft Teams integration for sending alerts to a Teams channel. Loggly supports sending static alert messages to Teams and we can also insert data from the alert into the message.


This integration utilizes the Generic Email Endpoint to create an Incident in the timeline whenever a Loggly alert is fired. Here are the instructions.


You can send alerts to GitHub using the loggly-github library created by Cargo Media.


Loggly can send alerts via email and using webhook. Either method can be used to forward Loggly alerts to OpsGenie. How to create alerts via both method in OpsGenie are described here.


Have more questions or don’t see an endpoint listed that you want? Ask about it in our community forum.

When the APM Integrated Experience is enabled, Loggly shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate the product and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.