//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfilePosts







Loading...
Modern #compliance requirements demand more than #monitoring dashboards, they require verifiable, long-term observability. In this article from Ayedo, explore how to build a compliance-ready #observability platform using:
🟣 #VictoriaMetrics for high-performance metrics & long-term retention 🟣 #VictoriaLogs for structured, tamper-resistant logging 🟣 Grafana for visualization & reporting 🟣 Tracing backends for end-to-end visibility
This talk empowers developers to use #OpenTelemetry (#OTel) for troubleshooting their own code, covering instrumentation basics, visualization tools, best practices for adding #traces, #metrics, and #logs, a practical workflow, and common pitfalls.
Our Developer Experience Engineer, @didiviking.bsky.social, presented with @adrianamvillela.bsky.social, Principal Developer Advocate at Dynatrace, at Devoxx Greece, “The lazy developer’s guide to observing your own code.”