LogicMonitor Data Publisher for HTTPS Receiver
Last updated - 30 September, 2025
LogicMonitor Data Publisher is an integrated service in Collector that enables you to extract and send real-time DataSource metrics from a Collector to an HTTPS endpoint (a third-party destination) for further analytics. This feature enables the Collector to send metrics to other data sinks in parallel with sending metrics to the LogicMonitor portal. LogicMonitor Data Publisher sends metrics over any HTTPS-defined endpoint through an HTTPS receiver.
When an HTTPS receiver is integrated with the Collector, LogicMonitor Data Publisher automatically shares the metrics. The following steps outline the service workflow:
- Enable and configure the HTTPS receiver in the
agent.confsettings. - Restart the Collector to start the LogicMonitor Data Publisher service.
- The LogicMonitor Data Publisher collects and converts metrics data into a standard OTLP-formatted JSON string.
- The Data Publisher sends the formatted data to the receiver—HTTPS endpoint.
Requirements for Using LogicMonitor Data Publisher for HTTPS Receiver
To use LogicMonitor Data Publisher for an HTTPS receiver, you need the following:
- HTTPS server compatible with HTTPS v1.
- EA Collector 37.300 or later installed on your machine.
- The
metrics.protov1.0.0 to read and convert metrics into an OTLP-formatted JSON string. For more information, see metrics.proto from GitHub.
HTTPS Receiver Property Configurations
In the agent.conf settings, configure the following properties:
| Property | Description |
enable.collector.publisher | (Mandatory) Enables the LogicMonitor Data Publisher service. By default, the value is false. To enable the Data Publisher service, set the value to true. |
agent.publisher.name | (Mandatory) Specifies the HTTPS publisher name. To enable the HTTPS publisher, set the value to http or HTTP. |
publisher.http.url | (Mandatory) Specifies the HTTPS URL to send metrics. |
publisher.dequeue.count | Defines the number of DataSource instance raw or metrics data sent per HTTPS request. The default value is 5. |
agent.publisher.enable.auth | Specifies authentication mode to send data through HTTPS request. The default is noAuth (plain text). To enable authentication, set the value to true. Currently, Basic and Bearer token-based authentication are supported. |
publisher.http.bearer.token | Enter your bearer token for token-based authentication. |
publisher.http.auth.user | If you set agent.publisher.enable.auth=true, enter the username for basic authentication. |
publisher.http.auth.password | If you set agent.publisher.enable.auth=true, enter the password for basic authentication. |
publisher.http.proxy.enable | To send data to the HTTPS endpoint through a proxy server, set this property to true. |
publisher.http.proxy.host | Specifies the proxy host URL. |
publisher.http.proxy.port | Specifies the proxy port. |
publisher.http.proxy.user | If you set publisher.http.proxy.enable=true, enter the proxy username. |
publisher.http.proxy.pass | If you set publisher.http.proxy.enable=true, enter the proxy password. |
Authentication for HTTPS Receiver
By default, LogicMonitor Data Publisher sends data in the noAuth mode. You can authenticate using bearer token or follow the basic authentication method. To enable the Auth mode, do the following:
- In LogicMonitor, navigate to Settings > Collectors.
- Under the Collectors tab, select the Collector that you must configure.
- Select
More and then select Collector Configuration. - In the agent.conf settings, set value for the following properties:
- To enable authentication, set value for
agent.publisher.enable.auth. - To authenticate using the bearer token, set value for
publisher.http.bearer.token. - To authenticate using basic authentication, set value for
publisher.http.auth.userandpublisher.http.auth.password.
- To enable authentication, set value for
- Restart the Collector.
LogicMonitor Data Publisher switches to the Auth mode.
Dependencies on HTTPS Receiver Request Headers
The LogicMonitor Data Publisher sends data over an HTTPS endpoint with the following HTTPS client request headers:
| Key | Value | Header Type |
| Content-Type | application/json | Default |
| Content-Encoding | GZIP | Default |
| Accept-Encoding | gzip,deflate | Default |
| Authorization | Basic <username:password> OR Bearer <Encrypted-Token> | WITHAUTH, if authentication (agent.publisher.enable.auth) is enabled. |
LogicMonitor Data Publisher Collection and Conversion for HTTPS Receiver
LogicMonitor Data Publisher collects metrics and adds metadata, then converts the data into an OTLP-formatted JSON string.
HTTPS Receiver Data Model
LogicMonitor Data Publisher converts metrics data into an OTLP-formatted JSON string. OTLP is a standard protocol for transmitting telemetry data in observability and monitoring systems. The OTLP converter is a gRPC service in LogicMonitor Data Publisher that implements protobuf (based on metrics.protoversion 1.0.0) to convert Collector metrics data into an OTLP-formatted JSON string. Metrics data in OTLP consists of one or more time series, where each time series represents a set of related datapoints over time.
The following is an example of OTLP-formatted metrics data in JSON format for LogicMonitor_Collector_ThreadCPUUsage datasource of netscan-propsdetection instance.
{
"resourceMetrics": [
{
"resource": {
"attributes": [
{
"key": "hostName",
"value": {
"stringValue": "127.0.0.1"
}
},
{
"key": "hostId",
"value": {
"stringValue": "1017594"
}
},
{
"key": "devicePropKey",
"value": {
"stringValue": "devicePropValue"
}
}
]
},
"scopeMetrics": [
{
"scope": {
"name": "LogicMonitor_Collector_ThreadCPUUsage",
"attributes": [
{
"key": "collector",
"value": {
"stringValue": "jmx"
}
},
{
"key": "epoch",
"value": {
"stringValue": "1715263558360"
}
},
{
"key": "datasourceId",
"value": {
"stringValue": "128265135"
}
},
{
"key": "datasourceInstanceId",
"value": {
"stringValue": "367542931"
}
}
]
},
"metrics": [
{
"name": "CpuUsage",
"sum": {
"dataPoints": [
{
"startTimeUnixNano": "1715263558360000000",
"timeUnixNano": "1715263558360000000",
"asDouble": 0,
"attributes": [
{
"key": "dataSourceInstanceName",
"value": {
"stringValue": "LogicMonitor_Collector_ThreadCPUUsage-netscan-propsdetection"
}
},
{
"key": "datapointid",
"value": {
"stringValue": "197642"
}
},
{
"key": "wildValue",
"value": {
"stringValue": "netscan-propsdetection"
}
},
{
"key": "wildAlias",
"value": {
"stringValue": "netscan-propsdetection"
}
}
]
}
],
"aggregationTemporality": "AGGREGATION_TEMPORALITY_DELTA",
"isMonotonic": true
}
},
{
"name": "ProcessorCount",
"gauge": {
"dataPoints": [
{
"startTimeUnixNano": "1715263558360000000",
"timeUnixNano": "1715263558360000000",
"asDouble": 10,
"attributes": [
{
"key": "dataSourceInstanceName",
"value": {
"stringValue": "LogicMonitor_Collector_ThreadCPUUsage-netscan-propsdetection"
}
},
{
"key": "datapointid",
"value": {
"stringValue": "197643"
}
},
{
"key": "wildValue",
"value": {
"stringValue": "netscan-propsdetection"
}
},
{
"key": "wildAlias",
"value": {
"stringValue": "netscan-propsdetection"
}
}
]
}
]
}
},
{
"name": "RunnableThreadCnt",
"gauge": {
"dataPoints": [
{
"startTimeUnixNano": "1715263558360000000",
"timeUnixNano": "1715263558360000000",
"asDouble": 0,
"attributes": [
{
"key": "dataSourceInstanceName",
"value": {
"stringValue": "LogicMonitor_Collector_ThreadCPUUsage-netscan-propsdetection"
}
},
{
"key": "datapointid",
"value": {
"stringValue": "197644"
}
},
{
"key": "wildValue",
"value": {
"stringValue": "netscan-propsdetection"
}
},
{
"key": "wildAlias",
"value": {
"stringValue": "netscan-propsdetection"
}
}
]
}
]
}
},
{
"name": "ThreadCnt",
"gauge": {
"dataPoints": [
{
"startTimeUnixNano": "1715263558360000000",
"timeUnixNano": "1715263558360000000",
"asDouble": 0,
"attributes": [
{
"key": "dataSourceInstanceName",
"value": {
"stringValue": "LogicMonitor_Collector_ThreadCPUUsage-netscan-propsdetection"
}
},
{
"key": "datapointid",
"value": {
"stringValue": "197645"
}
},
{
"key": "wildValue",
"value": {
"stringValue": "netscan-propsdetection"
}
},
{
"key": "wildAlias",
"value": {
"stringValue": "netscan-propsdetection"
}
}
]
}
]
}
}
]
}
]
}
]
}The resourceMetrics consists of the following:
- ResourceMetrics—JSON array of one or more resources. It depends on the
publisher.dequeue.countproperty. - Resource—Metadata of the device from which the metrics is collected.
- ScopeMetrics
- Scope—Metadata of the DataSource for which metrics is collected.
- Metrics—Actual datapoints of the DataSource that are retrieved from the device.
Note: Raw data has two types of datapoints: normal and complex. LogicMonitor Data Publisher can only send normal datapoints in metrics data.
HTTPS Receiver Metadata Details
The OTLP-formatted JSON string contains data collected for a single poll along with the following metadata:
- Host name or Device name
- DataSource name
- Instance name
- Polling interval
- Epoch details
- DataPoint name
HTTPS Receiver
The LogicMonitor Data Publisher sends metrics in OTLP-formatted JSON string. The HTTPS receiver must be able to read and convert metrics data through metrics.proto. For more information, see metrics.proto from GitHub.
LogicMonitor Data Publisher for HTTPS Receiver Performance Monitoring
LogicMonitor Data Publisher DataSource monitors and provides real-time performance metrics and tracks the following datapoints:
| Datapoint | Description |
| CountOfDataEnqueued | Count of data enqueued to BigQueue. |
| CountOfDataDequeued | Count of data dequeued from BigQueue. |
| SizeOfBigQueue | Size of the queue in which data persists. |
| HTTPRequestCount | Number of requests to the HTTPS endpoint. |
| HttpRedirectsCount | Number of redirect requests. |
| SuccessfulHTTPRedirectsCount | Number of successful redirect requests. |
| FailedHTTPRedirectsCount | Number of failed redirect requests. |
| SuccessfulRequestsToHTTPEndpoint | Number of successful requests to the HTTPS endpoint. |
| CountofRequestsfailedDueToAuthError | Number of requests failed due to authentication errors. |
| CountofRequestsfailedDueToNetworkError | Number of requests failed due to network errors. |
| TimeTakenforDequeueAndConversion | Time taken for dequeuing data from queue and converting them to OTLP-formatted JSON string. |
| SizeOfDataPublishedinBytes | Size (in bytes) of data published to HTTPS endpoint. |
Note: If the connection with HTTPS endpoint fails, LogicMonitor Data Publisher can store data for 30 minutes.
