Examples of Events in Sematext
Events originate from internal and external sources.
Internal Events¶
Internal events come from sources such as:
- Kubernetes events collected by Sematext Agent
- Container events collected by Sematext Agent
- Linux events like OOM Killer events
- Sematext Agent events, such as agent starting and stopping
- Alert events generated when an alert is triggered
External Events¶
External events are any events that are pushed into Sematext, whether through the events API or via the UI.
The following are just some examples of the types of data one can send to Sematext as events.
Application Deployment Tracking¶
Bugs, performance regressions, etc. happen after modified applications are deployed.
When you send a deployment event to Sematext you are able to promptly identify and investigate deployments that caused performance degradation
or caused new errors to appear. If your deployment events include an identifier that lets you see individual commits you will be able to
trace issues down to a specific commit.
Infrastructure Changes¶
Any changes in the infrastructure or its configuration can cause performance changes - whether positive or negative. A reduction or misconfiguration of infrastructure could cause errors caused by insufficient capacity. Sending an event when infrastructure changes are made in production helps you track track the root cause of issues.
Builds¶
Use functionality such as Github Actions to add events with information about builds to Sematext using the Sematext Events API.
Host Boot / Shutdown Events¶
It's a little retro, perhaps, but a call to the Events API can be made from /etc/rc.local to send an event when a host is started.
Systemd Service Start / Stop Events¶
You can add events when your application or a service starts or right before it stops. For example, when things are run under Systemd you can send events by adjusting the Systemd unit file for a service. In the example below we are using the Events API to send an event when the Elasticsearch service is started and when it's stopped:
ExecStartPre=/usr/bin/curl -s -XPOST "{{ event_receiver_url }}/{{ app_token }}/event" -d '{"message" : "Starting Elasticsearch on node {{ ansible_hostname }}","type" : "server_start"}'
ExecStopPost=/usr/bin/curl -s -XPOST "{{ event_receiver_url }}/{{ app_token }}/event" -d '{"message" : "Stopped Elasticsearch on node {{ ansible_hostname }}","type" : "server_stop"}'