Loggly provides the infrastructure to aggregate and normalize log events so they are available to explore interactively, build visualizations, or create threshold-based alerting. In general, any method to send logs from a system or application to an external source can be adapted to send logs to Loggly. The following instructions provide one scenario for sending logs to Loggly.
Many cloud-based services can send events from their webhook interfaces to Loggly’s HTTP/S Event Endpoint. This allows you to correlate changes in external cloud systems with things that are happening on your internal systems. Here are examples of popular services with webhooks.
Log events from GitHub’s Webhook API. Correlate deployments to changes in QA or production system behavior.
- Push – Git push to the repository.
- Deployment – Repository deployed.
- Pull Request – Pull Request opened, closed, or synchronized.
- Release – Release published in the repository.
- And more!
Log events from PagerDuty’s Webhook API. Correlate alert triggers and resolution with your system behavior. Read our PagerDuty capabilities post on how to see time to resolution, and who is resolving the most alerts.
- incident.trigger – Sent when an incident is newly created/triggered.
- incident.acknowledge – Sent when an incident has had its status changed from triggered to acknowledged.
- incident.resolve – Sent when an incident has been resolved.
- And more!
You can send events from any REST or HTTP/S Webhook using our HTTP/S Event Endpoint. Common data formats like JSON are automatically parsed by Loggly. This lets you search and analyze the data easily.