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.

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

Add ELK Stack #142

Closed
algarfer opened this issue Apr 16, 2024 · 0 comments · Fixed by #143
Closed

Add ELK Stack #142

algarfer opened this issue Apr 16, 2024 · 0 comments · Fixed by #143

Comments

@algarfer
Copy link
Contributor

A logging system is essential for debugging and monitoring purposes.

This system should track various requests between services and capture any potential errors that may arise.

Logging can also extend to the reverse proxy to gather statistics such as request volume, frequently accessed routes, and client locations via IP analysis.

The latter example could prove valuable for future scalability efforts, particularly if we need to deploy additional servers in specific regions to meet demand.

To achieve this, alongside configuring a logger for each node.js server, we should establish a LogStash instance for data ingestion and post-processing, utilize ElasticSearch for log indexing, and deploy Kibana for information display. Additionally, considering alternative BI tools like PowerBI or Apache Superset could enhance our analytics capabilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant