Operations | Monitoring | ITSM | DevOps | Cloud

ServiceNow Integration for Obkio's Network Monitoring Tool: Now Live

Obkio's ServiceNow integration is now live. When Obkio detects a network issue, it opens an incident in ServiceNow. When the issue recovers, it resolves that same incident. Your team works the problem in the platform they already use for incident management, with the monitoring context already attached.

Meet Rosetta

During an incident, the answers an engineer needs are spread across tools. Telemetry sits in one place, configurations in another, and tickets in a third. Building a complete picture means knowing which tool holds which piece and how to query each one, usually under time pressure. Rosetta is the conversational interface for Selector Foundry, the agentic NetOps platform built on Selector’s existing AIOps and Observability solution.

Sentry JavaScript SDK v11 adds tracing for all JS platforms

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.

Announcing Gremlin Foresight AI

Today we're launching Foresight AI, Gremlin’s agentic resilience product that analyzes and tests your systems for potential failures, fixes them, and verifies reliability at the speed of AI. I've spent most of my career on call. At Amazon and Netflix, I served as a Call Leader, the person running the bridge when something big broke. Those years taught me the same lesson we founded Gremlin on: the best incident is the one that never happens.
Sponsored Post

Raygun APM Agent 3.1: async traces that stay with the right request

Raygun APM Agent 3.1 introduces more accurate asynchronous request tracing for Windows, Linux, and Azure App Service. Version 3.0 rebuilt the foundation of the Agent, profiler, installers, and release pipeline. Version 3.1 builds on that work with a focused improvement for ASP.NET Core: automatic request correlation that follows asynchronous execution without requiring developers to instrument their application. The result is a more accurate trace, with less duplication and a clearer view of the work performed for each web request.

Tempo 3.1 release: new features for Kafka, TraceQL metrics updates, trace redaction, and more

Building on the major release of Tempo 3.0, Tempo 3.1 is here, delivering community-contributed Kafka client improvements, query-based trace redaction, sampling-aware TraceQL metrics, and more. Together, the updates in 3.1 make it easier to operate Tempo, get accurate insights from your trace data, and investigate issues more efficiently. You can continue reading and check out the video below to learn more about the latest features.

Icinga Director v1.12.0 Release

Icinga Director 1.12.0 is out now. This release finally gives custom variables full support for dictionaries, fixes a long standing bug that broke user group restores, and raises the module’s minimum requirements to match the rest of the Icinga Web ecosystem. You can find issues and feature requests related to this release on our roadmap.

VictoriaTraces in VictoriaMetrics Cloud: Complete Observability is Here

Earlier this year, we launched VictoriaLogs in VictoriaMetrics Cloud, bringing fast and cost-effective log management to everyone. Today we launch the final major step toward full observability: VictoriaTraces is now available to all cloud users. With this release, you can now manage all three signals, metrics, logs, and traces, in one place with the predictable pricing, reliability, and the operational simplicity you’ve come to expect from VictoriaMetrics.

Introducing the Harness Connector for OpenAI: Bring software delivery into ChatGPT and Codex

Harness Connector for OpenAI: Bring CI/CD Context to ChatGPT & Codex A pipeline fails while you are working through a change in ChatGPT or Codex. To understand what happened, you need the execution details, the failed step, and the relevant pipeline configuration. Gathering that context can interrupt the work you were doing before you can even begin to solve the problem. The Harness Connector for OpenAI brings that delivery context into your AI workflow.