Skip to main content
Version: current [26.x]

Service Telemetry for Kubernetes Deployments Enterprise

As of Dremio 26.0, enterprise customers deploying Dremio clusters on Kubernetes will automatically transmit telemetry data back to Dremio's corporate endpoint. This telemetry provides valuable insights into system performance and health, and is also used in the calculations for usage-based billing. Telemetry can be disabled through configuration; however, this is not considered a best practice because telemetry helps Dremio ensure stability and timely support.

Telemetry Data Collection​

Dremio's telemetry data collection is strictly limited to operational and performance metrics. These metrics provide visibility into various components and services, ensuring optimal performance and reliability. Importantly, no customer content (e.g., business data) or user-entered information is transmitted. If you would like to develop a deeper understanding of the metrics transmitted and their contents, you can set up your own internal monitoring of your Dremio cluster by following the steps in Monitoring Dremio Nodes.

The collected telemetry data is categorized as follows:

CategoryDescription
Application MetricsThese metrics provide insights into the usage and performance of objects within a Dremio deployment, including:
  • Number of queries, Reflections, sources, and views.
  • Success and failure rates of queries.
  • Success and failure rates of Reflection and source refresh operations.
Java MetricsThese metrics capture internal Java Virtual Machine (JVM) performance indicators from containers running the Dremio application, such as:
  • Number of active threads.
  • Memory allocation and usage.
  • Garbage collection activity and pauses.
Service MetricsThese metrics measure the health of core components supporting Dremio's execution and coordination services, including:
  • KVstore performance.
  • Zookeeper availability and network health.
Kubernetes MetricsThese metrics provide insight into container and pod behavior for all containers in a Dremio deployment, including:
  • CPU, memory, and storage requests.
  • Container restarts and readiness.
  • StatefulSet desired and current pod count.

Telemetry Transmission Requirements​

Telemetry transmission to Dremio follows the Dremio Subscription Agreement.

Network Requirements for Telemetry Transmission​

To ensure successful telemetry transmission, the following network configurations must be in place:

  • Your network must allow traffic egress to Dremio's endpoint observability.dremio.com.
  • Dremio's OpenTelemetry collectors use port 443 for secure data transmission via TLS.

Setting Up a Proxy​

If traffic egresses to the endpoint and the port is restricted, a proxy can be configured to enable telemetry transmission:

  1. Edit your .yaml configuration file to deploy Dremio to Kubernetes. For more information, refer to Configuring Your Values.

  2. Add your proxy configuration values to the .yaml file using the following syntax:

    telemetry:
      extraEnvs: []
        - name: HTTPS_PROXY
          value: https://proxy.example.com:443

Troubleshooting or Support​

For troubleshooting or support, please contact your account representative or Dremio Support.

  • Licensing - Learn more about Dremio's licensing and telemetry.
  • Billing - Learn more about Dremio's billing and usage data.