Dashboard import: migrate from other monitoring providers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli, observability
Research direction
Start by reviewing the CLI command entry points and the Sentry dashboard API schema. Define which third-party export formats and widget mappings are supported, how unsupported widgets are reported, and how dry-run output differs from API import. Done means a documented migration path with preview, graceful skipping, and optional dashboard creation.
Written by the indexing model from the issue text.
Description
Problem
Teams migrating from other observability/monitoring platforms to Sentry have no automated path for bringing their existing dashboards over. This creates manual re-creation work and acts as a friction point during migration.
Proposed Solution
Add a CLI command (e.g. sentry dashboard import) that accepts an exported dashboard definition from a third-party provider and converts it into a Sentry dashboard via the Sentry API.
Potential approach:
- Accept provider-specific export formats as input (file or stdin)
- Use LLM-assisted or heuristic mapping to translate widget types, queries, and layout to Sentry's dashboard schema
- Output a Sentry dashboard (optionally auto-importing via API token)
Scope
- Support common observability platform export formats
- Graceful handling of unsupported widget types (warn + skip)
- Dry-run / preview mode before committing to the API
Why CLI
The CLI has direct access to the Sentry API and is the natural home for automation and migration tooling that doesn't belong in the product UI.
Action taken on behalf of Miguel Betegón.
- Dominant language
- TypeScript
- Stars
- 121
- Forks
- 14
- Avg merge
- 22h 3m
- Merged PRs (30d)
- 94
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
bug jared
-
jared
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linagora/twake-calendar-frontend#1377 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#13385 · 1 comment ·
-
front-end UI/UX
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100