Feature request: Configurable external drill-down links in Coroot panels

Problem

We are using Coroot as an observability tool, but we still need other tools for custom workflows and deeper investigations, for example Grafana dashboards or Sentry issues/traces.

Right now, switching from Coroot to external tooling requires manual context transfer: users need to copy service names, trace IDs, time ranges, or other values and then manually open the corresponding external tool. This breaks the investigation flow and makes Coroot harder to use as the central entry point for incident analysis.

It would be very useful if Coroot could provide configurable external drill-down links directly inside relevant panels.

Proposal

Add support for configurable external links that can be shown in Coroot panels.

These links should allow users to jump from Coroot into external tools while passing contextual values such as:

selected time range service / application name instance / node name trace ID span ID namespace / cluster labels or other metadata available in the current Coroot context

Example targets could be:

• Grafana dashboards
• Sentry issues, traces, or performance views
• log search tools
• APM tools
• internal custom tooling
• Expected behavior
• Security Tooling

Coroot administrators should be able to configure between 1 and 4 external links for selected panels or views.

Each link should have:

• a display name, for example Open in Grafana or Open in Sentry
• a target URL template
• support for dynamic variables from the current Coroot context
• optional availability rules, for example only show the link when a trace_id exists

Example URL templates:

https://grafana.example.com/d/service-overview?from=${from}&to=${to}&var-service=${service_name} https://sentry.example.com/performance/trace/${trace_id}/?start=${from}&end=${to}

The links should appear directly in relevant panels, for example as buttons, dropdown actions, or panel menu items.

Use cases

1. Jump from Coroot to Grafana

A user investigates a service in Coroot and wants to open an existing custom Grafana dashboard for that service with the same time range.

Expected link: Open in Grafana with parameters such as: from=${from} to=${to} service=${service_name}

1. Jump from Coroot to Sentry

A user sees a problematic trace or error-related signal in Coroot and wants to open the corresponding trace or issue in Sentry.

Expected link: Open in Sentry with parameters such as:

trace_id=${trace_id} from=${from} to=${to} 3. Jump to internal tooling

A user wants to open an internal operations or deployment tool for the currently selected service, namespace, or cluster.

Expected link: Open internal tool with parameters such as:

service=${service_name} namespace=${namespace} cluster=${cluster}

Suggested configuration example externalLinks:

• name: Open in Grafana url: "https://grafana.example.com/d/service-overview?from=${from}&to=${to}&var-service=${service_name}" contexts:

  • service
  • application

• name: Open in Sentry url: "https://sentry.example.com/performance/trace/${trace_id}/?start=${from}&end=${to}" contexts:

  • trace showWhen:
  • trace_id

Requirements

Support 1 to 4 external links per relevant context or panel Support URL templates with dynamic variables Support selected Coroot time range as variables Support trace-related variables where available Links should be visible directly in relevant panels or panel menus Missing variables should either hide the link or render it disabled Configuration should be possible globally, for example via config file, Helm values, or UI settings Why this matters

This would make Coroot much more useful as the central observability entry point while still allowing teams to keep existing specialized tools.

Many teams have custom Grafana dashboards, Sentry workflows, log search tools, or internal platforms that cannot easily be replaced. Configurable drill-down links would reduce friction, preserve context, and make investigations significantly faster.

Related idea

Grafana supports data links and panel links that allow users to jump to external tools with contextual values. A similar lightweight mechanism in Coroot would be very valuable.