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

Jump to bottom

Investigate ELK stack to replace Prometheus #8

Open
thanethomson opened this issue Jun 23, 2022 · 0 comments
Open

Investigate ELK stack to replace Prometheus #8

thanethomson opened this issue Jun 23, 2022 · 0 comments
Labels
logs Issues relating to log processing, analysis and management monitoring

Comments

@thanethomson
Copy link
Contributor

Following from #7 (comment), and related to #6, I'd recommend we eventually replace our current testnet monitoring setup with an ELK stack.

The ELK stack seems to be used by many operators, and beyond just metric monitoring with Metricbeat, it also offers advanced log analysis that Prometheus doesn't. This could be tremendously valuable in allowing us to quickly debug complex issues across large numbers of nodes.
@thanethomson thanethomson added logs Issues relating to log processing, analysis and management monitoring labels Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
logs Issues relating to log processing, analysis and management monitoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thanethomson