Skip to content
The whole stack
Stack · Infra

OpenTelemetry

Traces, metrics and slow queries: knowing why it is slow before guessing.

1 place2 challenges

My experience

Filetable's traces and metrics: tying a slow page to the queries that slow it down, before guessing.

Where I used it

The challenges

See the 2 posts on the blog

In the same family

DockerDockerIdentical environments from laptop to production, reproducible CI builds.Used atFiletableBranchlateCYSECSee the details →KubernetesKubernetesZero-downtime deployments and migrations, rolling updates and scaling.Used atFiletableCYSECSee the details →TemporalTemporalDurable workflows for AI and long-running jobs: retries, priority queues, open source and self-hosted.Used atFiletableSee the details →GitLab CIGitLab CIFull CI/CD: tests, builds and automated deployments on every merge.Used atOneDocCYSECID QuantiqueSee the details →NginxNginxReverse proxy and TLS in front of SaaS services.Used atCYSECSee the details →LinuxLinuxServers, scripting and deployment automation.Used atPictetCYSECSee the details →