Dash0

Reading time: 0 minute(s) (0 words)

Dash0 provides an observability platform built on OpenTelemetry and Prometheus standards. By connecting Dash0 to Nobl9, you can transform your high-resolution telemetry into actionable SLOs.

Dash0’s API is fully compatible with Prometheus, allowing the Nobl9 agent to query metrics using standard PromQL while utilizing Dash0’s secure Auth Tokens for access control.

Dash0 parameters and supported features in Nobl9

General support:

Release channel: Beta

Connection method: Agent, Direct

Replay and SLI Analyzer: Historical data limit 30 days

Event logs: Supported

Query checker: Not supported

Query parameters retrieval: Supported

Timestamp cache persistence: Supported

---

Query parameters:

Query interval: 1 min

Query delay: 1 min

Jitter: 15 sec

Timeout: 30 sec

---

Agent details and minimum required versions for supported features:

Plugin name: n9prometheus

Query delay environment variable: PROM_QUERY_DELAY

Replay and SLI Analyzer: 0.109.0-beta

Query parameters retrieval: 0.109.0-beta

Timestamp cache persistence: 0.109.0-beta

Custom HTTP headers: 0.109.0-beta

Authentication

Dash0 requires an Auth Token to authenticate requests to its Prometheus API. These tokens are managed at the organization level and ensure secure, granular access to your telemetry data.

The auth token must be issued for your Dash0 organization and contain querying parameters.

To authenticate your Nobl9 Dash0 agent with the auth token, deploy the agent, passing the DASH0_AUTH_TOKEN environment variable.

Kubernetes

Kubernetes configuration

spec:
  template:
    spec:
      containers:
        - name: agent-container
          env:
            - name: DASH0_AUTH_TOKEN
              valueFrom:
                secretKeyRef:
                  key: dash0_auth_token
                  name: agent-dash0

Docker

Docker command line

docker run -d --restart on-failure \
  --name dash0-agent \
  -e N9_CLIENT_SECRET="N9_CLIENT_SECRET" \
  -e N9_METRICS_PORT=9090 \
  -e N9_CLIENT_ID="<N9_CLIENT_ID>" \
  -e DASH0_AUTH_TOKEN="<DASH0_AUTH_TOKEN>" \
  nobl9/agent:latest-beta

Adding Dash0 as a data source

You can add the Dash0 data source using the direct or agent connection method.

Direct connection method

Nobl9 Web

To set up this type of connection:

1. Navigate to Integrations > Sources.
2. Click .
3. Click your required Source tile.
4. Choose Direct.

5. Nobl9 integration with Dash0 is available only in the Beta release channel.

6. Enter the Auth token to connect to your data source (mandatory).

7. Enter your Dash0 server URL (mandatory).

8. Set Step to define the metric resolution (mandatory, default: 60 seconds).
   The Step value must be a positive integer. It controls how many data points Nobl9 retrieves in a single query.

   For optimal operation, consider the following recommendations for its value:
   • Aim for 15 seconds or more
   • Keep it less than or equal to your Dash0 query interval

9. Select a Project (mandatory).
   Projects provide the structure for organizing Nobl9 resources and managing access permissions.
   If a project is not specified, Nobl9 assigns the default project value automatically.
10. Enter a Display Name (optional).
    Spaces are allowed.
11. Enter a Name (mandatory).
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
12. Enter a Description (optional).
    Provide extra details, such as the purpose and responsible personnel.
    Up to 1050 characters.
13. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.

    • The default value in Dash0 integration for Query delay is 1 minute.

    Changing the query delay

    Changing the query delay can affect your SLI data.
    Learn more about query delay and its impact.
14. Configure how Nobl9 uses your data source’s historical data for Replay and SLI Analyzer.
    These features allow you to backfill SLOs or analyze SLIs for assisted SLO creation.
1. Maximum period for historical data retrieval (optional).

   • Defines the furthest point in the past from which data can be retrieved.
   • To activate Replay and SLI Analyzer for your data source, set this value to a positive whole number.
   • The maximum period is capped by your data source's specific limitations. Find the maximum value for your data source.
2. Default period for historical data retrieval (optional).

   • Sets the automatic backfill window for new SLOs using this data source.
   • Enter 0 or a positive whole number (default: 0). You can change this value for individual SLOs during creation.
   • Setting a non-zero value results in automatic replay of newly created SLOs based on this data source, so they report past performance upon creation, rather than waiting for new data to accumulate.
15. Click Add Data Source.

YAML

Create a YAML definition to set up a direct connection with Dash0. You can use the following example:

YAML definition for the direct connection method

apiVersion: n9/v1alpha
kind: Direct
metadata:
  name: dash0
  displayName: Dash0 Direct
  project: default
  annotations:
    area: latency
    env: prod
    region: us
    team: sales
spec:
  description: Example Dash0 Direct
  releaseChannel: beta
  dash0:
    authToken: Secret
    url: https://dash0.url
    step: 60
  historicalDataRetrieval:
    maxDuration:
      value: 30
      unit: Day
    defaultDuration:
      value: 15
      unit: Day
  queryDelay:
    value: 1
    unit: Minute

Field	Type	Description
queryDelay.unit Mandatory	enum	Specifies the unit for the query delay. Possible values: Second | Minute. • Check query delay documentation for default unit of query delay for each source.
queryDelay.value Mandatory	numeric	Specifies the value for the query delay. • Must be a number less than 1440 minutes (24 hours). • Check query delay documentation for default unit of query delay for each source.
logCollectionEnabled Optional	boolean	Optional. Defaults to false. Set to true if you'd like your direct to collect event logs. Contact us to activate it.
releaseChannel Mandatory	enum	Specifies the release channel. Accepted values: beta | stable.
Source-specific fields
dash0.url Mandatory	string	Base URL to your Dash0 server. See authentication for more details.
dash0.authToken Mandatory	string	Your auth token. See authentication for more details.
dash0.step Mandatory	integer	Defines metrics resolution in seconds. Must be a positive integer, 60 seconds by default. Recommendations: Use a value of at least 15 seconds and less than or equal to your Prometheus query interval.
Replay-related fields
historicalDataRetrieval Optional	n/a	Optional structure related to configuration related to Replay. ❗ Use only with supported sources. • If omitted, Nobl9 uses the default values of value: 0 and unit: Day for maxDuration and defaultDuration.
maxDuration.value Optional	numeric	Specifies the maximum duration for historical data retrieval. Must be integer ≥ 0. See Replay documentation for values of max duration per data source.
maxDuration.unit Optional	enum	Specifies the unit for the maximum duration of historical data retrieval. Accepted values: Minute | Hour | Day.
defaultDuration.value Optional	numeric	Specifies the default duration for historical data retrieval. Must be integer ≥ 0 and ≤ maxDuration.
defaultDuration.unit Optional	enum	Specifies the unit for the default duration of historical data retrieval. Accepted values: Minute | Hour | Day.

Agent connection method

Nobl9 Web

Follow the instructions below to create your Dash0 agent connection:

1. Navigate to Integrations > Sources.
2. Click .
3. Click your required Source tile.
4. Choose Agent.

5. Nobl9 integration with Dash0 is available only in the Beta release channel.

6. Enter your Dash0 server URL (mandatory).

7. Set Step to define the metric resolution (mandatory, default: 60 seconds).
   The Step value must be a positive integer. It controls how many data points Nobl9 retrieves in a single query.

   For optimal operation, consider the following recommendations for its value:
   • Aim for 15 seconds or more
   • Keep it less than or equal to your Dash0 query interval

8. Select a Project (mandatory).
   Projects provide the structure for organizing Nobl9 resources and managing access permissions.
   If a project is not specified, Nobl9 assigns the default project value automatically.
9. Enter a Display Name (optional).
   Spaces are allowed.
10. Enter a Name (mandatory).
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
11. Enter a Description (optional).
    Provide extra details, such as the purpose and responsible personnel.
    Up to 1050 characters.
12. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.

    • The default value in Dash0 integration for Query delay is 1 minute.

    Changing the query delay

    Changing the query delay can affect your SLI data.
    Learn more about query delay and its impact.
13. Configure how Nobl9 uses your data source’s historical data for Replay and SLI Analyzer.
    These features allow you to backfill SLOs or analyze SLIs for assisted SLO creation.
1. Maximum period for historical data retrieval (optional).

   • Defines the furthest point in the past from which data can be retrieved.
   • To activate Replay and SLI Analyzer for your data source, set this value to a positive whole number.
   • The maximum period is capped by your data source's specific limitations. Find the maximum value for your data source.
2. Default period for historical data retrieval (optional).

   • Sets the automatic backfill window for new SLOs using this data source.
   • Enter 0 or a positive whole number (default: 0). You can change this value for individual SLOs during creation.
   • Setting a non-zero value results in automatic replay of newly created SLOs based on this data source, so they report past performance upon creation, rather than waiting for new data to accumulate.
14. Click Add Data Source.
Deploy your agent in a Kubernetes cluster or Docker container.

To configure custom HTTP headers for your Nobl9 agent, include them in your agent deployment.

YAML

Create a YAML definition to set up an agent connection with Dash0. You can use the following example:

YAML definition for the agent connection method

apiVersion: n9/v1alpha
kind: Agent
metadata:
  name: dash0
  displayName: Dash0 Agent
  project: default
  annotations:
    area: latency
    env: prod
    region: us
    team: sales
spec:
  description: Example Dash0 Agent
  releaseChannel: beta
  dash0:
    url: https://dash0.url
    step: 60
  historicalDataRetrieval:
    maxDuration:
      value: 30
      unit: Day
    defaultDuration:
      value: 15
      unit: Day
  queryDelay:
    value: 1
    unit: Minute

Field	Type	Description
queryDelay.unit Mandatory	enum	Specifies the unit for the query delay. Possible values: Second | Minute. • Check query delay documentation for default unit of query delay for each source.
queryDelay.value Mandatory	numeric	Specifies the value for the query delay. • Must be a number less than 1440 minutes (24 hours). • Check query delay documentation for default unit of query delay for each source.
logCollectionEnabled Optional	boolean	Optional. Defaults to false. Set to true if you'd like your direct to collect event logs. Contact us to activate it.
releaseChannel Mandatory	enum	Specifies the release channel. Accepted values: beta | stable.
Source-specific fields
dash0.url Mandatory	string	Base URL to your Dash0 server. See authentication section above for more details.
dash0.step Mandatory	integer	Defines metrics resolution in seconds. Must be a positive integer, 60 seconds by default. Recommendations: Use a value of at least 15 seconds and less than or equal to your Prometheus query interval.
Replay-related fields
historicalDataRetrieval Optional	n/a	Optional structure related to configuration related to Replay. ❗ Use only with supported sources. • If omitted, Nobl9 uses the default values of value: 0 and unit: Day for maxDuration and defaultDuration.
maxDuration.value Optional	numeric	Specifies the maximum duration for historical data retrieval. Must be integer ≥ 0. See Replay documentation for values of max duration per data source.
maxDuration.unit Optional	enum	Specifies the unit for the maximum duration of historical data retrieval. Accepted values: Minute | Hour | Day.
defaultDuration.value Optional	numeric	Specifies the default duration for historical data retrieval. Must be integer ≥ 0 and ≤ maxDuration.
defaultDuration.unit Optional	enum	Specifies the unit for the default duration of historical data retrieval. Accepted values: Minute | Hour | Day.

Useful links

Check out these related guides and references:

Create SLOs with Dash0Creating SLOsAgent metricsAgentCreating agents via TerraformTerraform