Monitoring, tracing, observability in DevOps

[monperrus]

• https://en.wikipedia.org/wiki/Tracing_(software)
• https://en.wikipedia.org/wiki/System_monitoring
• https://en.wikipedia.org/wiki/Network_monitoring
• https://en.wikipedia.org/wiki/Crash_reporter
• https://en.wikipedia.org/wiki/Application_performance_management
• https://en.wikipedia.org/wiki/Website_monitoring
• https://en.wikipedia.org/wiki/Provenance#Computer_science
• https://en.wikipedia.org/wiki/Log_analysis

[monperrus]

See also icinga (thanks to @henriklb for the suggestion)

[monperrus]

Log analysis @eclipse https://projects.eclipse.org/projects/tools.tracecompass

[MatsJonsson]

We've found Istio ( https://istio.io/ ) to be increasingly useful in this context. KubeSpy ( https://github.com/pulumi/kubespy )is an excellent tool for troubleshooting and diagnosing Kubernetes deployments.

[lsc]

• Prometheus
• Sensu https://sensu.io/
• Zipkin
• the ELK stack.

[MatsJonsson]

+1 for Prometheus

[bittermandel]

Sentry for Error Reporting. https://sentry.io/welcome/

[monperrus]

• OpenZipkin
• Jaeger https://github.com/jaegertracing/jaeger
• https://medium.com/@rakyll/cpdd-critical-path-driven-development-6c2592fb8ea4

(from #16 (comment))

[monperrus]

See also Runtime application self-protection #18 (comment)

[monperrus]

Analytics

[monperrus]

Tools and Benchmarks for Automated Log Parsing.
http://arxiv.org/abs/1811.03509

[monperrus]

Does the Fault Reside in a Stack Trace? Assisting Crash Localization by Predicting Crashing Fault Residence
https://www.sciencedirect.com/science/article/pii/S0164121218302401