Logsene by Sematext is an enterprise-class log management solution. Logsene can receive logs from a wide array of logs shippers, such as Fluentd, Logstash, and Syslog; and supports many logging frameworks for programming languages such as: Java, Scala, Go, Node.js, Ruby, Python, and more. Among other capabilities, Logsene exposes the Elasticsearch API, works with Kibana, and has built-in alerts and anomaly detection. It is available both in the Cloud (SaaS) and On Premises. It also integrates with SPM Performance Monitoringto correlate metrics, events, and logs (check out Integrate PagerDuty with SPM Performance Monitoring for those instructions, which are very similar to what you will see here).
If you are creating a new service for your integration, click +Add New Service.
If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +New Integration button.
If you are creating a new service for your integration, in General Settings, enter a Name for your new service. Then, in Incident Settings, specify the Escalation Policy, Notification Urgency, and Incident Behavior for your new service.
No, but the user can decide to get a “Back to normal state” message.
No, currently PagerDuty is a global setting in Sematext Logsene and only one API key is managed.
Incidents are not de-duplicated, but there are settings within Sematext Logsene that can be enabled to avoid too many alerts/triggers.
Yes, all alerts are stored and displayed for users within Sematext Logsene.