ITRS acquires IP-Label. Read the press release.

  1. Support
  2. Knowledge base
  3. OpenTelemetry
  4. Uptrends OpenTelemetry export configuration and setup

Uptrends OpenTelemetry export configuration and setup

Note: Uptrends OpenTelemetry export is available for Enterprise-level accounts.

Configure OpenTelemetry export

To configure OpenTelemetry export in Uptrends, do the following:

  1. Log in to Uptrends as an administrator.

  2. Go to the OpenTelemetry export menu. This opens a setup page for first-time setup.

  3. Create a connection.

  4. Create a rule set.

  5. Choose a monitor group to export Uptrends monitoring data.

Once your initial setup is completed, you can manage exports, connections, rule sets, and monitor groups from the OpenTelemetry export page. You may also create a new export by clicking +New export.

Uptrends OpenTelemetry export

Create a connection

You can create a connection in two ways:

  • First-time setup page: Opening the OpenTelemetry export menu for the first time opens the setup page to configure your initial connection.
  • From the Connections tab: Create a connection anytime on the OpenTelemetry export menu > Connections tab > +New connection.

To create a connection, do the following:

  1. Provide a connection name.
  2. Provide the OpenTelemetry endpoint URL.
  3. Select the protocol supported by your connector and allowed by your network configuration.
  4. Provide the timeout in milliseconds.
  5. Select the maximum message age.
  6. (Optional) Configure headers:
  • Enable Use basic authentication if required. You can use the Uptrends Vault to store credentials such as username and password.
  • If your connector requires token-based authentication, add a custom header.

Create a connection on the Uptrends OpenTelemetry export

Test connection

To verify that your connection works, do the following:

  1. Click Test connection.
  2. Provide a service namespace and service name. They apply only to this test request and do not affect your export configuration.
  3. Click Test connection. The result of the HTTPS request is displayed.

Test a connection on the Uptrends OpenTelemetry export

If the connection test succeeds, your observability platform should receive an OpenTelemetry trace from this test.

Note: Depending on your observability platform, locating the test trace may require applying filters (for example, by service namespace, service name, or time range). The exact steps depend on how your platform ingests and displays OpenTelemetry data.

Create a rule set

A rule set can be created in two ways:

  • First-time setup page: Opening the OpenTelemetry export menu for the first time opens the setup page to configure your initial rule set.
  • From the Rule sets tab: Create a rule set anytime on the OpenTelemetry export menu > Rule sets tab > +New rule set.

You may create multiple rule sets to scope data differently (for example by namespace, service name, or instance ID).

To create a rule set, do the following:

  1. Provide a rule set name.
  2. Provide a service namespace.
  3. Provide a service name.
  4. Provide a service instance ID. We recommend using the {{MonitorName}} token to automatically replace it with the monitor name.
  5. (Optional) Enable Export unconfirmed errors.
  6. (Optional) Define custom attributes in key-value pairs to add properties to the exported data.

Create a rule set on the Uptrends OpenTelemetry export

Choose monitors

To complete the setup, do the following:

  1. Select a monitor group to export metrics from.
  2. Click Enable export.

Choose monitors on the Uptrends OpenTelemetry export

This creates and enables an OpenTelemetry export for your monitor group. Once configured, you can see one enabled export on the OpenTelemetry export page.

From this page, you can manage, enable, or disable exports for each monitor group at any time to control which monitoring data is sent to your OpenTelemetry backend.

Manage exports

To manage exports and their associated connections and rule sets, go to the OpenTelemetry export page.

Enable export

Data is delivered to your OpenTelemetry endpoint only for monitor groups where export is enabled.

On the OpenTelemetry export page, confirm the following before you enable export using the toggle icon:

  • Your connection works.
  • You have at least one rule set.
  • You selected a monitor group with active monitors. We recommend starting with a small group for testing.

Only data gathered after export is enabled is sent to your backend. Historical monitoring data is not exported. After monitors produce new measurements, those should appear in your observability platform.

Allow up to five minutes for the first data to arrive. After that, data is typically delivered within seconds to one minute.

Edit export, connection, or rule set

  1. Click the edit icon next to the export, connection, or rule set you want to edit.
  2. Update the fields as needed.
  3. Click Save to confirm changes.
Note: Changes to a shared connection or rule set affect all exports that use it.

Delete export, connection, or rule set

Removing an export stops sending Uptrends monitoring data for that monitor group to your OpenTelemetry backend. It does not delete the connection or rule set referenced by that export. Those still remain on the Connections and Rule sets tabs for reuse.

To delete an export, connection, or rule set:

  1. Click the delete icon next to the export, connection, or rule set you want to remove.
  2. Click Save to confirm changes.
Note: You cannot delete a connection or rule set that is still used by an export. Adjust or delete the dependent export first.

Troubleshooting

To inspect activity and troubleshoot issues, go to the OpenTelemetry export page and click View log details. This lists error counts and descriptions so you can better understand what failed. Adjust connections, rule sets, or your observability backend as needed.

View log details on the Uptrends OpenTelemetry export

If you still need help, contact Uptrends Support.

By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.