JetBrains announced on August 27 that its OpenTelemetry plugin is now available across IntelliJ IDEA, GoLand, PyCharm, and WebStorm in the 2026.2 release, ending Rider's two-year exclusivity as the only JetBrains IDE with first-party distributed-tracing support. The plugin, which JetBrains says has more than 1.2 million installs in Rider, brings logs, metrics, traces, and the service map from local applications into the IDE without requiring developers to set up a separate local observability backend.
What the Plugin Does
The plugin reads OpenTelemetry data emitted by the application under development via a built-in OTLP receiver. Developers can search logs, follow traces across services, view CPU and memory metrics in real time, and inspect the dependency graph that a given request touched, all from a dedicated tool window. The OpenTelemetry tool window can be opened directly from the editor or via the Plugins marketplace.
The 2026.2 update adds AI-agent integration: developers can ask a coding assistant in the IDE to surface the trace of a failing endpoint, find the request that caused an exception, or plot a latency metric from the past hour. The assistant uses an MCP endpoint exposed by the plugin to query the same data the developer sees, an architecture JetBrains first previewed at its KotlinConf 2026 keynote in May.
Why It Matters
OpenTelemetry has become the de-facto standard for application instrumentation since the CNCF graduated the project in 2024. JetBrains' expansion to four additional IDEs means Java, Kotlin, Go, Python, and JavaScript developers can now inspect distributed traces without leaving their editor, removing a workflow gap that previously pushed developers to Honeycomb, Jaeger, or Grafana during incident response.
The shift also signals JetBrains' push to keep AI coding agents inside the IDE. JetBrains' coding assistant already competes with GitHub Copilot and Cursor for AI-pair-programming share, and the OpenTelemetry plugin gives that assistant an observability-aware workflow that neither Microsoft nor Cursor has matched at parity.
Industry Reaction
Observability vendors responded cautiously. Honeycomb published a same-day blog post welcoming "broader OTel adoption" while noting that the JetBrains plugin is "complementary to, not a replacement for, production telemetry backends." Grafana Labs CTO Tom Wilkie noted in a LinkedIn post that "any IDE investment in OTel is good for the ecosystem" and pointed to continued demand for Grafana's Tempo and Mimir products.
What to Watch Through Year-End
Three checkpoints follow. The first public benchmarks comparing the JetBrains plugin to Honeycomb and Grafana for local-trace query latency will determine whether IDE-native observability is viable for production debugging. The community response to MCP-based AI agent integration will show whether observability vendors should expose their own MCP servers. And the question of whether JetBrains bundles the plugin by default in 2027.1 will indicate how central observability has become to JetBrains' developer-experience roadmap.
Comments (0)
Log in or sign up to leave a comment.
No comments yet. Be the first to share your thoughts.