feat: Add dashboard template gallery

[pulpdrew]

Summary

This PR adds a gallery of importable dashboard templates to the dashboards page. The existing Dashboard import functionality is modified to support importing dashboard templates which are included in the app source code bundle.

Screenshots or video

Screen.Recording.2026-03-30.at.8.52.12.AM.mov

How to test locally or on Vercel

This can be tested as shown above in the preview environment.

References

• Linear Issue: Closes HDX-3661 Closes HDX-3814
• Related PRs:

[changeset-bot]

🦋 Changeset detected

Latest commit: a2ec799

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@hyperdx/common-utils	Patch
@hyperdx/app	Patch
@hyperdx/api	Patch
@hyperdx/otel-collector	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hyperdx-oss	Ready	Preview, Comment	Apr 1, 2026 5:28pm

[github-actions]

E2E Test Results

✅ All tests passed • 126 passed • 3 skipped • 1081s

Status	Count
✅ Passed	126
❌ Failed	0
⚠️ Flaky	2
⏭️ Skipped	3

Tests ran across 4 shards in parallel.

View full report →

[github-actions]

PR Review

✅ No critical issues found.

A few minor notes worth considering:

• ⚠️ router.query.template can be string | string[] in Next.js — the as string | undefined cast (with eslint-disable) will silently pass an array to getDashboardTemplate, which then fails the lookup gracefully. Low risk, but could be made explicit with Array.isArray(v) ? v[0] : v.
• ⚠️ description is optional in DashboardTemplateSchema but the unit test enforces it via expect(json.description).toBeTruthy(). These are inconsistent — either make description required in the schema or document the intentional split (schema allows omission for user-imported templates, tests enforce it for shipped ones).
• ℹ️ getDashboardTemplate re-parses the JSON on every call rather than reusing the already-parsed DASHBOARD_TEMPLATES array — minor inefficiency, not a bug.

[pulpdrew]

Changes to this file are intended to fix flaky E2E tests caused by duplicate filter inputs (when the same label/value is present under multiple filter columns)

[pulpdrew]

Fixes bug: Form submission error when submitting a metric query without first setting a value expression via a non-metric source

[wrn14897]

Have we verified that these dashboard templates work as expected? One concern I have is the semantic conventions, since they tend to change over time.

Another thing is that we probably want to list the supported collector version range and I wonder if we want to introduce a 'Collector' tag for things like OTel or Vector, etc

[pulpdrew]

Have we verified that these dashboard templates work as expected?

@alex-fedotyev created them, and I have verified that they display the metrics produced by simple java/go/python/node/dotnet applications running locally with OTEL.

One concern I have is the semantic conventions, since they tend to change over time.

That's a good point. I can add the required semantic spec version in each description.

Since these are imported as saved dashboards (and are not hardcoded presets), if/when the semantic conventions change, users will likely have to update the impacted dashboard tiles themselves.

Another thing is that we probably want to list the supported collector version range

These metrics are collected by OTel language SDKs - would they depend on the collector version?

I wonder if we want to introduce a 'Collector' tag for things like OTel or Vector, etc

That's a good idea, I could tag these as "OTEL Runtime Metrics" instead of just "Runtime Metrics"

[wrn14897]

I believe otel sdks follow semantic versioning (maybe that’s the version we should follow). Let's get this out and we can adjust templates time to time.