Skip to main content

​
Logicmonitor Exporter

Status Available in: contrib Maintainers: @bogdandrutu, @khyatigandhi6, @avadhut123pisal Source: opentelemetry-collector-contrib

​
Supported Telemetry

Logs Traces

​
Overview

This exporter supports sending traces & logs to Logicmonitor.

​
Configuration Options

The following configuration options are supported: endpoint (required): The target base URL to send data to (e.g.: https://<company_name>.logicmonitor.com/rest). For logs, “/log/ingest” path will be appended by default.
api_token : API Token of Logicmonitor

​
Prerequisite

Below environment variable must be provided
KeyValue
LOGICMONITOR_ACCOUNTCompany name
NOTE: For ingesting data into the Logicmonitor, either its API Token or Bearer Token is required.

​
Example

Ingestion through API Token
Pass access_id and access_key through config.yaml as shown in example OR
Set the environment variables LOGICMONITOR_ACCESS_ID and LOGICMONITOR_ACCESS_KEY 
  exporters:
    logicmonitor:
      endpoint: "https://<company_name>.logicmonitor.com/rest"
      api_token:
        access_id: "<access_id of logicmonitor>"
        access_key: "<access_key of logicmonitor>"
Ingestion through Bearer token
Pass bearer token as Authorization headers through config.yaml as shown in example OR Set the environment variable LOGICMONITOR_BEARER_TOKEN 
  exporters:
    logicmonitor:
      endpoint: "https://<company_name>.logicmonitor.com/rest"
      headers:
        Authorization: Bearer <bearer token of logicmonitor>

​
Resource Mapping for Logs

As per the LogicMonitor’s Log Ingestion documentation, if more than one resource property exists, only the first property will be mapped. In case of OTLP logs, there can be multiple resource attributes and its order also cannot be guaranteed. Recently we have made the resource mapping for logs more flexible. With that, any of the resource attributes present in the log matches can be considered for resource mapping. But, this is not the default behaviour. In order to make the resource mapping flexible, you can configure the resource_mapping_op in the LogicMonitor’s exporter. 
  exporters:
    logicmonitor:
      endpoint: https://company.logicmonitor.com/rest
      headers:
        Authorization: Bearer <token>
      logs:
        resource_mapping_op: "OR"
The value for resource_mapping_op can be AND or OR. The values are case-insensitive.

​
Configuration

​
Example Configuration

# The following entry demonstrates 
# - endpoint: The URL on which logs will be forwarded based on the configured pipeline
# - apitoken: Configuring the API Token as an authorization mechanism.
logicmonitor/apitoken:
  endpoint: https://company.logicmonitor.com/rest
  api_token:
    access_id: "accessid"
    access_key: "accesskey"
# The following entry demonstrates 
# - endpoint: The URL on which logs will be forwarded based on the configured pipeline
# - headers: Passing bearer token in headers for authorization.
logicmonitor/bearertoken:
  endpoint: https://company.logicmonitor.com/rest
  headers:
    Authorization: Bearer <token>
# The following entry demonstrates how to set resource mapping operation (AND / OR). 
# The values are case-insensitive
logicmonitor/resource-mapping-op:
  logs:
    resource_mapping_op: "OR"
  endpoint: https://company.logicmonitor.com/rest
  headers:
    Authorization: Bearer <token>
Last generated: 2026-04-13