Using OpenTelemetry, Splunk, and CI(Jenkins) to deliver a Monitoring Solution for Financi...
summary
Murex adopts OpenTelemetry to export logs and metrics, uses Python probes that later shift to Go, and ingests data into Splunk where six APM dashboards report near–real‑time state with 10-second dashboard refresh rate. Metrics replace heavy log pulls to cut dashboard load from seconds to under one second for many views; a CI system built as a Jenkins pipeline runs nightly tests that curl Splunk panels to CSV and compare against golden masters, catching layout or data-attribute regressions. Python probes handle initial extraction.
AI-written summary · about
chapters (11)
- 0:00Project introduction
- 3:46Architecture overview
- 6:43Otel implementation details
- 10:04Splunk visualization tools
- 13:16Deep dive into probes
- 15:54APM dashboard development
- 19:49Performance testing insights
- 24:27Automated testing with CI
- 30:34Jenkins testing workflow
- 37:39Conclusion and roadmap
- 41:27Q&A session
related talks
49mAdding OpenTelemetry to Production Apps Lessons Learned
41mCustomer Centric Observability at Scale Leveraging AIOps & OpenTelemetry
35mGaining Observability Into Your CI/CD Pipeline
44mIterative metrics, dashboards and monitors
44mHow We Gained Observability Into Our CI CD Pipeline
17mOpenTelemetry Looks Good To Me: Loki, Grafana, Tempo, Mimir
43mHow We Gained Observability Into Our CI/CD Pipeline
28mImprove Monitoring and Observability for Kubernetes with OSS Tools