Configure Logz.io to send notifications to your preferred endpoints. Notifications are typically sent when alerts are triggered, when a user shares an OpenSearch Dashboards object, or when Logz.io Insights identifies new exceptions in your logs.
Preconfigured vs. custom endpoints
There are two types of endpoints.
Preconfigured endpoints: For these, the body, method, and headers are preconfigured. You'll need to specify authentication information, such as your API key, service key, or token.
Supported apps include Opsgenie (only if hosted by the US data center), BigPanda, PagerDuty, Slack, VictorOps, ServiceNow, and Microsoft Teams.
Custom endpoints: You'll need to specify the URL, method, and headers, and optionally the message body.
Click for detailed instructions.
Manage notification endpoints
To add a new endpoint, click Add endpoint, fill in the required information, and click Save.
To test an endpoint after it's created, open it in edit mode. Click Run the test and make sure the test message was received.
Logz.io will notify you if the message couldn't be sent, but you'll need to confirm that the message was received.
To edit or delete an endpoint, hover over the endpoint, and click (edit) or (delete).
Alerts can only be sent on ports 80 & 443. If you accidently set a custom port for an alert endpoint, the alert will not be sent.
Example - Adding an Opsgenie endpoint
Opsgenie is a typical example for a preconfigured endpoint. To add it, select Opsgenie from the dropdown list, name the endpoint, and fill in your Opsgenie API key.
See Opsgenie notifications for resolved metrics alerts for related information.
Typical use case
If your team is using Slack, you likely have multiple Slack channels to organize different projects.
You can configure your Logz.io alerts to reach the right Slack channel by configuring a Slack endpoint for each channel.
The example below shows different Slack channels dedicated to production and security alerts, application updates, and account overage.