Browsing available templates
To browse the built-in template library, navigate to Dashboards and click Browse dashboard templates. This opens the template gallery, where templates are organized by category. Click Import on the template you want to use.Importing a template
In Step 2: Map Data, review the Dashboard Name and Tags, then confirm the data source in the To column for each tile and filter. Sources may already be selected. In the example below, the Node.js Runtime Metrics template maps its charts and service filter to the Metrics source. Click Finish Import to create the dashboard.Pre-built templates
Browser RUM
The Browser RUM (real user monitoring) template provides Core Web Vitals, page-load percentiles, traffic breakdowns, and error tracking. It uses browser sessions instrumented with the HyperDX Browser SDK or OpenTelemetry RUM instrumentation that emitsrum.sessionId.
OTel runtime metrics
The built-in OTel Runtime Metrics templates are designed for applications instrumented with OpenTelemetry runtime metrics.
Notes:
- Each template is configured with a custom filter for services whose
telemetry.sdk.languageresource attribute matches the dashboard’s runtime. - Metric names can vary between OpenTelemetry SDK versions. If your SDK emits different metric names, edit the visualizations to match your data.
Self-managed schemas
For self-managed deployments with custom metric table schemas, adjust the template’s service filter to query the appropriate service-name and resource-attribute columns. For high-volume workloads, consider materializing frequently queried attributes, such asResourceAttributes['telemetry.sdk.language'], to reduce filter load times.