LogDNA is releasing Custom Webhooks, enabling customers to easily integrate LogDNA alerts with 3rd-party services. Custom Webhooks allows you to configure a webhook’s header and body and add specific LogDNA tokens to your alerts going through that webhook.
If you’re using LogDNA alerts to inform your team of infrastructure or development issues, the next step in your workflow might be to create a ticket to track the task required to resolve the error from the alert. To do so, you now can trigger an API call from the LogDNA log alert. For example, if 100 loglines match a specified query, you can set up an alert to trigger an external webhook like Jira to create a new work ticket.
You can find this feature under the Alerts section: /manage/alerts
We’ve included the five most commonly used HTTP methods (POST, PUT, PATCH, GET, DELETE) to allow for maximum configurability. Custom Webhooks also allow for authentication via header fields, allowing users to secure the webhook URL.
Lastly, the body (payload) can be configured with JSON or plain text, hard-coded content, and tokens that map to data from the LogDNA alert. Tokens (template variables) we currently offer include:
Without configuration, LogDNA will provide a preset template. I’m excited to see the creative ways you’ll use Custom Webhooks! If you have ideas on additional tokens we should include, please let me know at email@example.com.
Custom Webhooks docs can be found here.