Adapter (tibpromgateway) Command Line Reference

TIBCO FTL Prometheus adapter (tibpromgateway) acts as an adapter between the realm server and a Prometheus Pushgateway process.

Location

The tibpromgateway executable file is located in the bin directory of the product installation tree.

Help

Parameter Arguments Description
--help

-h

  Display a help message describing the command line parameters and options.

Communications

Parameter Arguments Description
--push-gateway

-g

IP:port Required.

The adapter application sends its data output to the Prometheus Pushgateway at this location.

Supply an IP address and port number, separated by a colon character (:).

--realmserver

-rs

URL Required.

URL of the realm server. The adapter application receives both its realm definition and monitoring data from the realm server.

The adapter application contacts the realm server at this location. Supply the location of the primary realm server or a satellite server (see "Connect Port" in TIBCO FTL Administration).

--secondary-realmserver

-s

URL Optional.

URL of the backup realm server.

If the regular realm server is unavailable, the adapter application contacts the backup realm server at this location to receive its realm definition. Supply the location of the backup realm server (see "Connect Port" in TIBCO FTL Administration).

Data

Parameter Arguments Description
--exclude-timestamp

-x

Optional.

When present, the adapter application removes the client's sampling interval time stamp from the data samples before sending it to the Prometheus Pushgateway.

When the clocks of the clients' host computers are not approximately synchronized, then Prometheus queries that refer to the time stamp field can yield unexpected results. Excluding the time stamp causes the Prometheus Pushgateway to supply a new time stamp value, representing the time that the adapter posted the data sample to the Pushgateway process. (This posting time is necessarily later than the time the client collected the monitoring sample.)

--source-name name Optional.

Supply a human-readable string that denotes the source of the monitoring data. The adapter process tags data with this string.

This name becomes the value in the Prometheus exported_job label. You can use this value in Prometheus queries to distinguish data from different sources, for example, primary and satellite realm servers.

When absent, the default value is the URL of the ream server, that is, the value of the -⁠-⁠realmserver command line parameter.

--max-age

-a

age Optional.

When the adapter stops receiving monitoring data about a client, the adapter waits for this time (in seconds) before instructing the Pushgateway to reclaim the memory that held data about that client.

When absent, the default value is 1800 seconds (30 minutes).

JAAS Security

Parameter Arguments Description
--password-file

-pf

path Optional. (Required for JAAS authentication.)

When present, the adapter application reads a user name and password from the file at path, and authenticates itself to the realm server using those credentials. For details, see "Password File" in TIBCO FTL Admistration.

TLS Security

Parameter Arguments Description
--trust-file path Optional. (Required for TLS communication with a secure realm server.)

When present, the adapter application reads a trust file from path, and uses that trust data in communications with the secure realm server. See "Running a Secure Realm Server" in TIBCO FTL Admistration.

--trust-everyone Optional.

The adapter application trusts any realm server without verifying trust in the server's certificate.

Warning: Do not use this parameter except for convenience in development and testing. It is not secure.

Tracing and Logging

Parameter Arguments Description
--trace

-t

level Optional.

When present, the adapter application outputs trace messages to stderr.

You may specify any of the standard log level strings (see “Tuning the Log Level” in TIBCO FTL Development).

When absent, the default trace level is info.

--logfile logfile_prefix Optional.

When present, the adapter application logs to a rolling set of log files instead of the console. The logfile_prefix argument may denote a path. All of the directories in the path must already exist.

For more information about rotating log files, see “Log Output Targets” in TIBCO FTL Development.

When absent, the adapter application sends log output to the console, ignoring the parameters --max-log-size and --max-logs.

--max-log-size size Optional.

Limits the maximum size, in bytes, of log files. The value must be greater than 100 kilobytes (102400). The default value is 2 megabytes (2*1024*1024).

--max-logs Optional.

Limits the maximum number of rolling log files. The default is 50.