LMC Exporter Installation

Overview

LMC Exporter is distributed as a precompiled application and does not require source compilation by end users.

This article describes:

• Supported runtime environments
• Installation methods
• License configuration and validation
• Runtime configuration
• Post-installation validation
• Common troubleshooting steps

Prerequisites

Supported Runtime Platforms

Runtime Requirements

The target host must provide:

• Access to the required RTDS installation
• Access to the appropriate shared-memory environment
• Valid Shared Memory server keys
• A valid LMC Exporter license
• Network connectivity for Prometheus scraping when HTTP metrics mode is enabled

Installation

LMC Exporter can be installed using either the CJC’s RPM repository or a supplied deployment archive.

sudo yum install lmc-exporter

sudo dnf install lmc-exporter

lmc_exporter --version

tar -xzf lmc-exporter-<version>.tar.gz

particle_horizon
├── SOFTWARE
|   └── lmc_exporter-<version>-<platform>-x86_64
|   └── bin
|      └── lmc_exporter-<platform>
├── local_config
|   └── lmc_exporter
|      └── lmc_exporter.toml
├── local_data
|   └── lmc_exporter

tar -xzf lmc-exporter-<version>-<platform>-<arch>.tar.gz -C /opt

/opt/particle_horizon/bin/lmc_exporter --version

License Setup and Validation

Create a Configuration File

Copy the supplied sample configuration file:

cp lmcExporterConfig.toml.sample ./lmcExporterConfig.toml

Configure License

Update the configuration file with the path to your license key:

license_file = "/path/to/license.json"

License Validation Process

During startup, LMC Exporter validates:

1. License fingerprint
2. Digital signature
3. License expiration status

Validation occurs before any LMC shared-memory discovery or metrics collection begins.

License Expiration Grace Period

For running instances:

• Warning messages continue throughout the grace period.
• Once the grace period expires, the exporter exits during the next enforcement check.

Runtime Configuration

Example Configuration

context_id = 1
pool_name = "default"

app = "ads"
server_keys = [82]

metrics_interval_seconds = 30

metrics_http_enabled = true
metrics_bind_address = "0.0.0.0"
metrics_port = 9464
metrics_path = "/metrics"

license_file = "/licenses/lmc_exporter.json"

Common Configuration Settings

Validation

Start the Exporter

RPM installation:

lmc_exporter --config ./lmcExporterConfig.toml

Tarball installation:

/opt/lmc-exporter/bin/lmc_exporter --config ./lmcExporterConfig.toml

Verify Version Information

lmc_exporter --version

Verify Metrics Availability

curl "http://127.0.0.1:9464/metrics?server_key=82"

Example application routing:

curl "http://127.0.0.1:9464/metrics?app=ads&instance=<resolved-instance>"

Troubleshooting

License Validation Failure

Symptoms

The exporter exits during startup before any LMC discovery occurs.

Resolution

Verify:

• The configured license file exists
• The license has not been modified
• The license signature is valid
• The license has not exceeded the grace period

License Expired

Symptoms

Startup warning messages indicate license expiration.

Resolution

Replace the license before the 36-hour grace period expires.

HTTP Endpoint Returns 503

Symptoms

HTTP 503 Service Unavailable

Resolution

The target subtree may not yet be fully synchronized.

Verify:

• Server key configuration
• Application configuration
• LMC connectivity
• Target availability

No Metrics Returned

Symptoms

Metrics endpoint responds successfully but contains no application metrics.

Resolution

Verify:

• Correct application configuration
• Target selection
• Application-specific metric mappings are configured for the target application