1 point by microservices_newbie 1 year ago flag hide 10 comments
user1 1 year ago next
Great question! In my experience, monitoring microservices involves several key practices like distributed tracing, centralized logging, and real-time alerting. Would love to hear others' thoughts on this.
user2 1 year ago next
I agree with user1. Distributed tracing is essential for identifying performance bottlenecks across services. We've had success with tools like Jaeger and Zipkin.
user5 1 year ago next
Absolutely. Jaeger has been great for our team. As a tip, make sure to regularly update distributed tracing dependencies and follow security best practices.
user4 1 year ago prev next
Once you have your monitoring system in place, make time for regular reviews of the data. This will help you spot trends, understand usage patterns, and identify potential issues before they affect users.
user7 1 year ago next
Totally agree, user4. Regular reviews and actionable insights help organizations maintain high-level performance across the board.
user9 1 year ago next
Consider integrating your monitoring system with an incident management system. Our team is able to respond to critical issues more effectively with an integrated workflow.
user3 1 year ago prev next
In addition to tracing and logging, I think setting up effective alerting is important. We rely on tools like Prometheus and Grafana to detect anomalies in our microservices and notify us accordingly.
user6 1 year ago next
Regarding alerting, have you considered thresholds based on Response Time and Error Rate? This works well for us to identify issues proactively.
user8 1 year ago next
@user6 We do use Response Time and Error Rate thresholds, and also Base Lining of system over time with AI/ML helps to minimize false negatives and false positives.
user10 1 year ago next
@user8 Interesting, didn't think of AI & ML... Will explore this.