MonitoringPDF version

Configuring OTel in HiveServer2

Learn how you can enable OTel in HiveServer2 and configure certain properties that will enable you to optimize the data collection.

  • Ensure that you are on Cloudera Data Warehouse 1.10.1 or higher version.
  • Ensure that the Hive Warehouse version is on 2025.0.19.0-XX or higher version.
  1. Log in to the Cloudera web interface and navigate to the Cloudera Data Warehouse service.
    The Overview page is displayed.
  2. From the Overview page, click the Virtual Warehouses tab, identify the Hive Virtual Warehouse that you want to configure, and then click to edit.
  3. In the Virtual Warehouse details page, click Configurations > Hiveserver2 and then select hive-site from the Configuration files drop-down.
  4. Search for hive.otel and modify the values as required:
    1. Required: hive.otel.metrics.frequency.seconds (Default: 0s)
      Specifies the frequency at which telemetry data is transmitted to the OTel collector. By default, the value is set to 0 seconds indicating that OpenTelemetry data collection is disabled. Enter a value greater than 0 to enable OpenTelemetry.
      If the value is 5s. This indicates that telemetry data is transmitted to the OTel collector every 5 seconds.
    2. Required: hive.otel.collector.endpoint
      Specifies the endpoint where all the OpenTelemetry Protocol (OTLP) traces and metrics are transmitted. The endpoint represents the address of an OTel collector. The endpoint must be a valid URL with https scheme.
      https://<otel-collector-host>:<port>
    3. Optional: hive.otel.exporter.timeout (Default: 10m)
      Specifies the maximum time allowed for the OTel agent to complete a transmit operation. The transmit operation times out if it exceeds the specified time.
    4. Optional: hive.otel.retry.initial.backoff (Default: 10s)
      Specifies the initial time delay before attempting to retry a failed transmit operation. The value serves as the starting point for the exponential backoff strategy.
    5. Optional: hive.otel.retry.max.backoff (Default: 1m)
      Specifies the maximum time that the OTel agent should wait between retries. This sets an upper limit on the backoff interval ensuring that retry export operations do not exceed the specified duration even with exponential backoff.
    6. Optional: hive.otel.retry.backoff.multiplier (Default: 5f)
      Specifies the factor by which the retry interval increases after every failed attempt. This determines how much the backoff interval increases after each failed attempt, following an exponential backoff strategy.
  5. Click Apply Changes and restart the Hive Virtual Warehouse.

We want your opinion

How can we improve this page?

What kind of feedback do you have?