OpenTelemetry Licensing

OpenTelemetry Licensing

The OpenTelemetry (OTel) Service license usage applies when traces are stored and indexed in AppLogs. The cost is tied to trace storage, rather than the number of OTel services or monitors created.

Suppose you have purchased 100GB of log storage. If you store traces from these OTel services, the storage will consume space from your 100GB log allocation. Related to traces are spans, that represents a unit of work or an operation in OTel.

Here are a few scenarios that show how OpenTelemetry services and trace storage affect licensing:

Sl.no
Scenario
Description
Licensing Impact
1
Multiple OpenTelemetry services
Several services send traces (for example, Auth, Payment, Order).

The traces you store in AppLogs are billed.

2
High traffic, many spans
More requests create more spans, which implies more trace data gets stored and billed in AppLogs.

For example, if your service handles 100 requests per minute, and each request generates five spans, that’s 500 spans per minute. Assuming each span is 2KB, the total trace volume is: 500 spans × 2KB/span = 1000KB/min (≈ 1MB/min)
The license usage will be 1MB per minute in AppLogs. Adding more services does not increase license costs.
3
No traces stored
No trace generated
No traces stored implies no cost. 
4
Mixed:
APM + OTel service
Service A uses APM Insight;
Service B uses OpenTelemetry.
Service A consumes an APM license, while Service B only contributes to license usage based on the spans it stores.
5
Many services, low volume
Consider 10 microservices that send a few spans each.
The licensing depends only on the total number of stored spans, not the number of services.
6
OTel metrics only
OpenTelemetry metrics sent without trace data.
The license depends on the total metrics stored.


    • Related Articles

    • How to verify the license key for a .NET application

      Problem Statement: The APM Insight .NET monitor is not created in the Site24x7 web client because of an empty or invalid license key. Prerequisite: The Site24x7 APM Insight .NET agent should be installed. Steps to verify the license key Navigate to ...
    • DC migration steps for APM Insight agents

      For Server based installations 1. Obtain the new device key. 2. Update the license.key value in the APM Insight configuration file (or the environment variable mentioned) with the new device key. The location varies for each agent, as listed below: ...
    • DC migration steps for APM Insight Java agent

      Obtain the new device key. Update the license.key value in the apminsight.conf file located at <apminsight-javaagent.zip Extracted Directory>/. Log in to the server and delete the existing instance information file apminsight.info located at ...
    • DC migration steps for APM Insight Python agent

      Obtain the new device key. Update the license.key value in the apminsight_info.json file located at the <application root directory>. Log in to the server and delete the existing instance information file located at the <application root ...
    • DC migration steps for APM Insight Ruby agent

      Obtain the new device key. Update the license.key value in the apminsight.conf file located at <APP_HOME>/. Log in to the server and delete the existing instance information file, apminsight.info, located at <APP_HOME>/. Restart the Ruby application. ...