Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve docs on logit elastalert #350

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Improve docs on logit elastalert #350

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion documentation/logit-io.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,18 @@ To create a new stack:
## Monitoring and Alerting

We have enabled Logit stack alerts and notification (elastalert).
Each stack has a monitor for too many logs per hour, and no logs in 30 minutes.

Each stack has a monitor for
- too many logs per hour
- no logs in 30 minutes
- email addresses in the logs

When triggered, an email alert will be sent to the TS Infra team email address, and we should investigate why there are too many or missing logs.

It will re-alert every 3 hours until any issue is resolved.

See [Elastart docs](https://elastalert.readthedocs.io/) for info on writing alerts.

## Logstash inputs
Filebeat sends logs to logstash as json so they can be decoded to create fields in ElasticSearch and query them with Kibana.

Expand Down
Loading