Configure FLM for Prometheus metrics

Prometheus metrics for the Four Js License Manager (FLM) are configured in the same configuration file as other FLM settings: $FLMDIR/etc/flmprofile. This page describes how to enable and configure Prometheus metrics collection.

When you enable Prometheus in FLM, the license server exposes a Prometheus-compatible metrics endpoint on the configured port (default 9191). Prometheus connects to this endpoint and scrapes metrics at regular intervals (for example, every 15 seconds).

The metrics endpoint is usually:

http://localhost:9191/metrics

Commented-out template in flmprofile:

[prometheus]
# Activate Prometheus metrics
# enabled=false

# HTTP server port for metrics collection
# port=9191

# HTTP server interface for metrics collection
# interface="0.0.0.0"

Active configuration example:

[prometheus]
enabled=true
port=9191
interface="0.0.0.0"
The interface setting controls which network interface FLM uses for the metrics endpoint.
  • Use 127.0.0.1 or localhost for local-only access.
  • Use 0.0.0.0 to allow remote Prometheus servers to connect.
  • You can also specify a hostname (for example, myflmhost.company.com) or any IP address that suits your environment.
  • The port is fully configurable; choose any available port if 9191 is already in use.

Restart the FLM service after making changes.

Update Prometheus configuration in prometheus.yml:

scrape_configs:
- job_name: 'flm'
scrape_interval: 15s
metrics_path: /metrics
static_configs:
- targets:
- 'localhost:9191'

Steps

  1. Edit $FLMDIR/etc/flmprofile and add or update the [prometheus] section as shown above.
  2. Set enabled to true to activate metrics collection.
  3. Adjust port and interface for your environment.
  4. Restart the FLM service to apply changes.
  5. Update prometheus.yml with the scrape job shown above.