Jira · Jira Service Management · v1.0.0 · Planned
MetricLens
for Grafana
Put the panel that proves the incident on the incident ticket.
- Panel on the issue
- Pinned time window
- Post-mortem evidence
- Read-only
The gap it closes
Every incident review needs the graph that showed the problem. It lives in a dashboard whose default time range has long since moved on, so by the time the post-mortem is written the evidence has to be reconstructed from memory.
Linking the dashboard does not solve it: a link opens “now”, not the twenty minutes that mattered.
MetricLens attaches the panel to the ticket with the incident window pinned, so the evidence stays attached to the record of what happened.
How it works
Three steps, then it runs itself.
- 01
Connect with a read-only token
Supply your instance address and a viewer-level API token. The app only ever reads.
- 02
Attach a panel to the issue
Pick the dashboard and panel that show the problem, and set the time window that matters.
- 03
The evidence stays put
The panel renders on the issue with that window pinned, so it means the same thing in the post-mortem as it did during the incident.
How it behaves
The decisions that matter.
-
Read-only, always
A viewer-level token is all it asks for. The app cannot alter dashboards, alert rules or data sources.
-
The time window does not drift
Windows are stored as absolute timestamps, never “last hour”. Relative ranges are exactly why old incident links become meaningless.
-
Your instance decides who may render it
Rendering is authorised by your instance. The app cannot show a panel to someone your instance would refuse.
-
An unreachable panel is stated, not blank
If the panel is deleted or the instance is unreachable, the issue shows an explicit message rather than an empty box that looks like the incident had no impact.
Where it runs, and what it reaches
Every outbound connection, named.
The app runs on Atlassian’s own infrastructure. Where it must reach outside, these are the only hostnames it is permitted to contact — the same list Atlassian shows your admin before you install, and the same list a Marketplace reviewer checks against the manifest.
-
your-grafana-instanceThe instance you configure, contacted with your read-only token to render the selected panel. No other host is reachable.
Runs on
Atlassian Forge (runs on Atlassian’s own infrastructure)
Your credentials live in
Forge encrypted secret storage, inside your own installation
Surfaces it adds
Jira admin page, Issue panel
Pricing
Priced per user, billed by Atlassian.
Every paid plan starts with a free 30-day evaluation, arranged by Atlassian. Atlassian collects the payment, handles invoicing and tax, and is the merchant of record — so this app appears on the Atlassian bill you already pay, not a separate one from me. Sites of ten users or fewer pay one flat monthly rate.
Evaluation
Free
Up to 10 users
$10/month
11–100 users
$1.00/user/mo
101+ users
$0.70/user/mo
Indicative pricing for an app that is not listed yet. The rate on the Marketplace listing is the one that applies.
Documentation & data handling
Everything it touches, stated plainly.
Installing & getting started
- Install MetricLens from the Atlassian Marketplace into your Jira site and review the permissions listed here.
- Open Settings → Apps → MetricLens and work through the three steps above.
- Your evaluation runs for 30 days with everything switched on, so it can prove itself before you pay for it.
- Stuck? Email [email protected] — one business day response.
Permissions, and why each one
read:jira-work- Read the issue in order to render its attached panels.
write:jira-work- Store the panel reference and its pinned time window against the issue.
storage:app- Hold the instance address and the encrypted read-only token inside your own installation.
What is stored, and where
- The API token is stored in Forge encrypted secret storage inside your own installation and is never returned to the browser.
- Only the panel reference and its absolute time window are stored against the issue. Metric data itself is not copied into Jira.
- Outbound connections go only to the instance address you configure.
- Uninstalling removes the stored address and token.
Technical detail
- Version
- 1.0.0
- Platform
- Atlassian Forge
- Runtime
- Node.js 22 — Forge runtime
- Products
- Jira, Jira Service Management
- Modules
- Jira admin page, Issue panel
- External connections
- 1 declared host
- Billing
- Paid through the Atlassian Marketplace
- Support
- [email protected]
- Support SLA
- One business day
- Publisher
- Builds By Luke, Canada
Grafana® is a registered trademark of Raintank, Inc. dba Grafana Labs. MetricLens is an independent product, not affiliated with, endorsed by or sponsored by Grafana Labs.
Questions people ask.
Can it change my dashboards?
No. It asks for a viewer-level token and only ever reads.
Why pin an absolute time window?
Because a relative range like “last hour” means something different every time it is opened, which makes old incident evidence worthless.
What if the panel is deleted later?
The issue shows an explicit unavailable message, so nobody mistakes a missing panel for a flat graph.
MetricLens is on its way.
It is on the build list for the Atlassian Marketplace. If you want it sooner — or want it to do one specific thing — that is genuinely useful to hear.