Overview

The Wildcard widget in Datadog extends the flexibility of the open-source Vega-Lite “Grammar of Graphics” language, and integrates it with the Datadog platform. The Wildcard widget allows you to create graphs that are not available within native Datadog widgets and query systems.

Use the Wildcard widget in Dashboards and Notebooks.

Best Practices

Datadog recommends using an existing dashboard widget to meet your use case. All native widgets have design and performance optimizations which are not available in the Wildcard widget. For known limitations, see the Additional information section.

However, if none of the Datadog widgets meets your visualization needs, a Wildcard widget is a fast way to get a new capability added to your Dashboards without waiting for a new feature or graph type to be added.

1. Don’t start from scratch. Vega-Lite maintains a public gallery with over 150 official examples. If you’re not sure what type of graph you want to use, fork an existing example to test the visualization. Use Vega-Lite over Vega for simplicity and ease of debugging.
2. Test the Wildcard widget. The flexibility of the Wildcard widget comes with the risk of creating slow, unappealing, or inconsistent visualizations. Test the Wildcard widget on a scratchpad or empty dashboard before adding Wildcard widgets to production.
3. Validate your query. Datadog widgets guarantee that the data visualizations are semantically aligned with the query, which ensures the configuration builds the expected graph. With the Wildcard widget, you’re adding a custom Vega-Lite specification that defines how the request maps to visual elements. This creates the potential that you’ll fetch a data field that isn’t used in your visualization. Use the Data Preview to help debug mismatches.

Setup

Configure a new Wildcard widget

1. Check native widgets. See if a Datadog widget can fulfill your requirements.
2. If no Datadog widget meets your requirements, in a new or pre-existing dashboard, click Add Widgets.
3. Click and drag the Wildcard Widget icon from the widget tray.
4. Copy a Vega-Lite Definition from the public gallery to find a starter Vega-Lite specification.
5. Open the Wildcard widget full screen editor and click Define Visual.
6. Paste the copied Vega-Lite definition.
7. Click Apply to apply your configuration changes, see a preview of the visualization, and iterate on your design. Note: You must click Apply to add your changes, however this does not save your configuration.
8. (Optional) Debug Vega-Lite specification mismatches with Data Preview. Make sure the query in your Vega-Lite specification maps to the Datadog query.
9. Click Save.

Import data from an existing widget

1. Copy from an existing Datadog widget using cmd+c.
2. Open the Wildcard widget full screen editor.
3. Paste with cmd+v.
4. Click Save.

Command palette

The command palette provides quick access to Wildcard widget tools. Activate with cmd + shift + p or click the info icon at the top of the page.

Data Preview

The Data Preview table shows the response, fields, and values from your data request that are available to use in your Vega-lite specification. To access, click the arrow at the bottom of the Wildcard widget editor to Show data preview. There are three types of tables in the preview:

• Request Rows: Displays your actual data.
• Request Columns: Displays column summary statistics and data types.
• Internal Tables: Displays transformed data stored by Vega-Lite.

Map Datadog data to Vega-Lite specifications

Datadog native widgets automatically map the query results to the visualization elements, but the Wildcard widget requires you to add a custom Vega-Lite specification that defines how the Datadog query maps to visual elements. This creates the potential for a mismatch. With Data Preview, you can verify that the Vega-Lite specification maps to the correct query response.

To see how Datadog values map to the Vega-Lite specification, start with the example metric query of system.cpu.user averaged by env:

Click on the Define Visual tab to view how this query maps to Vega-Lite. Open the Data Preview panel and notice the matching query1 and env fields listed in the Vega-Lite specification and the Data Preview column.

  {
    "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
    "data": {
      "name": "table1"
    },
    "encoding": {
      "x": {
        "field": "env",
        "type": "nominal"
      },
      "y": {
        "field": "query1",
        "type": "quantitative"
      }
    },
    "mark": {
      "type": "rect",
      "tooltip": {
        "content": "data"
      }
    }
  }

Select data configuration	Define Visual Specification

To demonstrate a mismatch between the Datadog data and the Vega-Lite specification, add an alias to the query. The visualization does not work because the Vega-lite specification still points to “query1”, but the Data Preview column shows that the new query is now the new alias “example”. To fix this visualization, you need to replace field:"query1" with field:"example".

Select data configuration	Define Visual Specification

Compatible data formats

The Wildcard Widget supports data requests from all data sources supported in native widgets:

Additional information

Choosing Between Vega and Vega-Lite

For simplicity and brevity, opt for Vega-Lite. The system supports Vega-Lite version 5.18.1. Reserve Vega for more complex or advanced visualization needs.

Terraform Integration

Use the datadog_dashboard_json resource when working with Wildcard widgets in Terraform dashboards.

Known Limitations

Avoid using Wildcard widgets for the following scenarios:

• Visualizations with high cardinality. If your visualizations have more than 5000 rows per request, consider pre-aggregating data on the backend before graphing.
• Network or hierarchical visualizations.
• Visuals requiring physics-based layouts.
• Advanced geographic mapping.
• 3D graphical representations.

Further reading

Additional helpful documentation, links, and articles:

Introduction to Vega-LiteVEGA TUTORIAL