Enterprise Prometheus Configurations

You can configure the Prometheus for enterprise deployment. All the required configuration parameters are stored in CONFIG_FOLDER_REDTAIL/rt_prometheus_vars.json

Each of the parameters is explained in more detail in the following table:

Prometheus Configuration Options

Parameter Description
certs_conf_path

The directory where the certificates required for communicating with other nodes is stored

 

Mandatory: Yes

Suggested Value: /usr/local/etc/rt_certs
data_path

The base directory for storing TIBCO OI Hawk RedTail services data. All the services store the data in the path categorized by service name.

 

Mandatory: Yes

Suggested Value: DATA_FOLDER
prometheus_node_url

Prometheus URL

 

Mandatory: Yes

Suggested Value: localhost
prometheus_port

Prometheus port

 

Mandatory: Yes

Suggested Value: 9090
zookeeper_node_url

ZooKeeper URL

 

Mandatory: Yes

Suggested Value: localhost
zookeeper.connectString

Host and port of ZooKeeper

 

Mandatory: Yes

Suggested Value: zookeeper:9600

zookeeper.config.path

ZooKeeper namespace where the configuration is stored

 

Mandatory:

Suggested Value: /unity/system/config
ZK_CLIENT_KEY_FILE

Path to the ZooKeeper client private key

 

Mandatory: Yes

Suggested Value: {certs_conf_path}/key
ZK_CLIENT_KEY_PASSWORD

Password of the ZooKeeper client key

 

Mandatory: Yes

Suggested Value: <password>
ZK_CLIENT_CACERT_FILE

Path to CA certificate file used for generating the key

 

Mandatory: Yes

Suggested Value: {certs_conf_path}/cacert
ZK_CLIENT_CERT_FILE

Path to the ZooKeeper client certificate

 

Mandatory: Yes

Suggested Value:{certs_conf_path}/certificate

Enterprise Prometheus Service Discovery Configurations

You can configure the Prometheus service discovery for the on-premises deployment. All the required configuration parameters are stored in CONFIG_FOLDER_REDTAIL/rt_prometheus_discoveryservice_vars.json

Each of the parameters is explained in more detail in the following table:

Prometheus Service Discovery Configuration Options

Parameter Description
certs_conf_path

The directory where the certificates required for communicating with other nodes is stored

 

Mandatory: Yes

Suggested Value:/usr/local/etc/rt_certs

data_path

The base directory for storing TIBCO OI Hawk RedTail services data. All the services store the data in the path categorized by service name.

 

Mandatory: Yes

Suggested Value: DATA_FOLDER
zookeeper_node_url

ZooKeeper URL

 

Mandatory: Yes

Suggested Value: localhost
zookeeper.connectString

Host and port of ZooKeeper

 

Mandatory: Yes

Suggested Value: zookeeper:9600

zookeeper.config.path

ZooKeeper namespace where the configuration is stored

 

Mandatory:

Suggested Value:/unity/system/config

ZK_CLIENT_KEY_FILE

Path to the ZooKeeper client private key

 

Mandatory: Yes

Suggested Value:{certs_conf_path}/key

ZK_CLIENT_KEY_PASSWORD

Password of the ZooKeeper client key

 

Mandatory: Yes

Suggested Value:<password>

ZK_CLIENT_CACERT_FILE

Path to CA certificate file used for generating the key

 

Mandatory: Yes

Suggested Value:{certs_conf_path}/cacert

ZK_CLIENT_CERT_FILE

Path to the ZooKeeper client certificate

 

Mandatory: Yes

Suggested Value:{certs_conf_path}/certificate

client_certificate

The certificate which is going to be used for TLS communication with the Hawk RedTail Console

 

Mandatory: Yes

Suggested Value: /usr/local/etc/rt_certs/prometheus-client-certificate

client_key

The key which is going to be used for TLS communication with the Hawk RedTail Console

 

Mandatory: Yes

Suggested Value: /usr/local/etc/rt_certs/prometheus-client-key
hawkconsole_ca

The CA certificate of the Hawk RedTail Console

 

Mandatory: Yes

Suggested Value: /usr/local/etc/rt_certs/cacert
target_output_file

Path to the file where the discovered Prometheus targets are stored

 

Mandatory: Yes

Suggested Value: /usr/local/tibco_redtail_data/prometheus_discoveryservice/hawktargets.json

log_level

Specifies the level of diagnostic information stored in the logs. The logging level are as follows:

• ERROR - Indicates that error level trace messages should be enabled.
• WARNING - Indicates that warning level trace messages should be enabled.
• INFO - Indicates that information level trace messages should be enabled.
• DEBUG - Indicates that debug level trace messages should be enabled.
• TRACE - Indicates that trace level messages should be enabled.

 

Mandatory: Yes

Suggested Value: INFO