You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel prometheus would be a good choice owing to its in built alerting mechanisms, centralised control and web ui for visualization and also the presence of PromQL
Some questions regarding monitoring:
Is the logging system in the backend app in place?
2)If yes, whats the structure of logs , do we need to implement a middleware to transform the logs so that it becomes compatible with prometheus worker. @iskitsas
The text was updated successfully, but these errors were encountered:
In the app you will find just the usual application logs. In the past we had used the ELK stack, so we had logstash and filebeat in place, to collect and parse logs, pushed to ES. If you are more familiar with this stack, you can use it.
On the other hand, you should implement anything needed to support Prometheus and be compatible with it. Propose an architecture so we can review it together, and help you where needed. You can change the structure of the logs to any format that is convenient for the integration.
I feel prometheus would be a good choice owing to its in built alerting mechanisms, centralised control and web ui for visualization and also the presence of PromQL
Some questions regarding monitoring:
2)If yes, whats the structure of logs , do we need to implement a middleware to transform the logs so that it becomes compatible with prometheus worker.
@iskitsas
The text was updated successfully, but these errors were encountered: