Operations | Monitoring | ITSM | DevOps | Cloud

TL;DR Metrics, logs, and traces each have a different shape, so each needs a different backend. Aiven for Metrics handles metrics and alerting, Aiven for OpenSearch handles keyword search across logs, and Aiven for ClickHouse handles analysis of high-volume, high-cardinality events. All three are upstream open source engines on the same Aiven platform, so you can start with one and add the others as your needs change.

How Qovery assessed a growing B2B SaaS company's infrastructure across about 150 controls, what the review with their team changed, and why a Typesense high-availability project turned into a sharding plan. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

In February we planned to move every Qovery-managed cluster from ingress-nginx to Envoy Gateway by the end of March. It took until October. Here is the rollout model, every class of problem we hit, and what I would do differently. Benjamin is a staff engineer at Qovery focused on infrastructure automation, Kubernetes internals, and building the deployment engine that powers thousands of clusters.

DevOps Team Extension gives growing engineering teams a named Qovery engineer, a continuous infrastructure scan, and a monthly remediation plan, so they can scale reliability, security and compliance without hiring a DevOps team first. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

New versions of SecureBridge, EntityDAC, and dbExpress drivers are out. All three now work with RAD Studio 13 Florence Release 2 and offer improved support for the Arm64EC target platform. Devart dbExpress drivers also add support for Microsoft SQL Server 2025 and MySQL 9.7, while SecureBridge gains SFTP upload resume, multipart/form-data support, and a new SSL/TLS demo.

This post is about a recent change to the Sentry JavaScript SDKs. If you don’t use Sentry with JavaScript, it may still be useful as a look at how we made the change and why. In the Sentry JavaScript SDK v11, we rebuilt how our tracing integrations work. While we still support the OpenTelemetry standard (described in more detail below), we now instrument your dependencies with a code transformer instead of using the OpenTelemetry instrumentation classes as we did in previous versions.