Anyone working in the SAP market in 2025 is aware of two big topics: migration to cloud-based ERP and the end of many long-used tools for managing SAP operations including Focused Run, Landscape Manager and Solution Manager. Both are impossible to ignore. Cloud-based ERP presents a new era of business software possibilities, and with it the opportunities and complexities of migration, transformation, and leveraging the elastic capacity and scalability of cloud-based designs. But right behind it, the question becomes "how are we going to run and manage this?"
In this video, Stefan (Playwright Ambassador) dives into his favorite topic, Playwright fixtures, and shows how to set up automatic network monitoring in your Playwright end-to-end tests to catch failed HTTP requests (404s, 500s) to maintain high-quality standards.
Datadog Data Observability provides a complete solution with quality checks (e.g., volume, row changes, freshness), custom SQL-based monitors, anomaly detection, column-level lineage across systems like Snowflake and Tableau, full pipeline visibility, and targeted alerts when data issues arise.
Debugging complex microservices just got an upgrade. This video demonstrates Speedscale's innovative Notebook capability, allowing you to perform advanced substring searches and filter production traffic based on deeply nested JSON fields within request and response bodies. Unlike traditional observability tools that only record telemetry, Speedscale's always-on recorder captures full traffic payloads, empowering you to precisely pinpoint issues, identify specific user calls, or validate API versions. Streamline your troubleshooting, enhance your testing, and gain unprecedented visibility into your production environment.
Every day I seem to run into yet another post with someone solemnly opining that “writing code has never been the hardest part of software engineering. And hey, that’s smashing. As an engineer from the ops/infra/SRE side of the house, I feel like I’ve been saying this my whole career. (Is there anything more satisfying than being proven right in public? Not in my book.) So, which is it?
Grafana Loki is up and running, log ingestion looks healthy, and dashboards are rendering without issues. But when you query logs from a few weeks ago, the data's missing. This is a recurring problem for many teams using Loki in production: while the system handles short-term log visibility well, it often lacks the retention guarantees developers expect for historical analysis and incident review.
As distributed systems scale, maintaining manual instrumentation across services quickly becomes unsustainable. The OTel Injector addresses this by automatically attaching OpenTelemetry instrumentation to applications, no code changes needed. This blog covers how the OTel Injector works, how it integrates with Linux environments, and how to set it up for consistent telemetry across your stack.
Cortex gives engineering teams full visibility and control over their services, from ownership and standards to service history and production readiness. Our goal is to help teams stay aligned and move faster so they are ready for whatever is ahead. The reality for any engineering team is that developers spend the most of their time in their IDE, not their IDP. And while developers love the context Cortex provides, they don’t love context switching.
Ask any embedded developer about their worst debugging experience, and chances are you’ll hear stories of unreproducible bugs, late-night watchdog resets, or CI test failures with no trace. Traditional tools often leave us blind at the exact moment we need insight.