Chapter 2. ceilometer
The following chapter contains information about the configuration options in the ceilometer
service.
2.1. ceilometer.conf
This section contains options for the /etc/ceilometer/ceilometer.conf
file.
2.1.1. DEFAULT
The following table outlines the options available under the [DEFAULT]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Enable eventlet backdoor. Acceptable values are 0, <port>, and <start>:<end>, where 0 results in listening on a random tcp port number; <port> results in listening on the specified port number (and not enabling backdoor if that port is in use); and <start>:<end> results in listening on the smallest unused port number within the specified range of port numbers. The chosen port is displayed in the service’s log file. |
| string value | Enable eventlet backdoor, using the provided path as a unix socket that can receive connections. This option is mutually exclusive with backdoor_port in that only one should be provided. If both are provided then the existence of this option overrides the usage of that option. |
| boolean value | To reduce polling agent load, samples are sent to the notification agent in a batch. To gain higher throughput at the cost of load set this to False. |
| integer value | The pool size limit for connections expiration policy |
| integer value | The time-to-live in sec of idle connections in the pool |
| string value | The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option. |
| boolean value | If set to true, the logging level will be set to DEBUG instead of the default INFO level. |
| list value | List of package logging levels in logger=LEVEL pairs. This option is ignored if log_config_append is set. |
| string value | Configuration file for event pipeline definition. |
| integer value | Size of executor thread pool when executor is threading or eventlet. |
| boolean value | Enables or disables fatal status of deprecations. |
| integer value | Specify a timeout after which a gracefully shutdown server will exit. Zero value means endless wait. |
| unknown value | Name of this node, which must be valid in an AMQP key. Can be an opaque identifier. For ZeroMQ only, must be a valid host name, FQDN, or IP address. |
| integer value | Timeout seconds for HTTP requests. Set it to None to disable timeout. |
| string value | Inspector to use for inspecting the hypervisor layer. Known inspectors are libvirt, hyperv, vsphere and xenapi. |
`instance_format = [instance: %(uuid)s] ` | string value | The format for an instance that is passed with the log message. |
`instance_uuid_format = [instance: %(uuid)s] ` | string value | The format for an instance UUID that is passed with the log message. |
| string value | Libvirt domain type. |
`libvirt_uri = ` | string value | Override the default libvirt URI (which is dependent on libvirt_type). |
| string value | The name of a logging configuration file. This file is appended to any existing logging configuration files. For details about logging configuration files, see the Python logging module documentation. Note that when logging configuration files are used then all logging configuration is set in the configuration file and other logging configuration options are ignored (for example, logging_context_format_string). |
| string value | Defines the format string for %%(asctime)s in log records. Default: %(default)s . This option is ignored if log_config_append is set. |
| string value | (Optional) The base directory used for relative log_file paths. This option is ignored if log_config_append is set. |
| string value | (Optional) Name of log file to send logging output to. If no default is set, logging will go to stderr as defined by use_stderr. This option is ignored if log_config_append is set. |
| boolean value | Enables or disables logging values of all registered options when starting a service (at DEBUG level). |
| string value | Format string to use for log messages with context. |
| string value | Additional data to append to log message when logging level for the message is DEBUG. |
| string value | Format string to use for log messages when context is undefined. |
| string value | Prefix each line of exception output with this format. |
| string value | Defines the format string for %(user_identity)s that is used in logging_context_format_string. |
| integer value | Maximum number of parallel requests for services to handle at the same time. |
| string value | Configuration file for pipeline definition. |
| boolean value | Enables or disables publication of error events. |
| integer value | Maximum number of logged messages per rate_limit_interval. |
| string value | Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG or empty string. Logs with level greater or equal to rate_limit_except_level are not filtered. An empty string means that all levels are filtered. |
| integer value | Interval, number of seconds, of log rate limiting. |
| string value | Swift reseller prefix. Must be on par with reseller_prefix in proxy-server.conf. |
| list value | List of metadata keys reserved for metering use. And these keys are additional to the ones included in the namespace. |
| integer value | Limit on length of reserved metadata values. |
| list value | List of metadata prefixes reserved for metering use. |
| string value | Path to the rootwrap configuration file to use for running commands as root |
| integer value | Number of seconds to wait for an ack from a cast/call. After each retry attempt this timeout is multiplied by some specified multiplier. |
| integer value | Number to multiply base ack timeout by after each retry attempt. |
| string value | The messaging driver to use, defaults to rabbit. Other drivers include amqp and zmq. |
| integer value | Size of RPC connection pool. |
| integer value | Expiration timeout in seconds of a sent/received message after which it is not tracked anymore by a client/server. |
| integer value | The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired. |
| integer value | Seconds to wait for a response from a call. |
| integer value | Default number of message sending attempts in case of any problems occurred: positive value N means at most N retries, 0 means no retries, None or -1 (or any other negative values) mean to retry forever. This option is used only if acknowledgments are enabled. |
| integer value | Maximum number of (green) threads to work concurrently. |
| boolean value | Wait for message acknowledgements from receivers. This mechanism works only via proxy without PUB/SUB. |
| string value | ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The "host" option should point or resolve to this address. |
| integer value | Number of retries to find free port number before fail with ZMQBindError. |
| integer value | Number of ZeroMQ contexts, defaults to 1. |
| string value | Name of this node. Must be a valid hostname, FQDN, or IP address. Must match "host" option, if running Nova. |
| string value | Directory for holding IPC sockets. |
| string value | MatchMaker driver. |
| integer value | Maximal port number for random ports range. |
| port value | Minimal port number for random ports range. |
| string value | Default serialization mechanism for serializing/deserializing outgoing/incoming messages |
| integer value | Maximum number of ingress messages to locally buffer per topic. Default is unlimited. |
| string value | Source for samples emitted on this instance. |
| list value | List of publisher hosts SubConsumer can subscribe on. This option has higher priority then the default publishers list taken from the matchmaker. |
| string value | Syslog facility to receive log lines. This option is ignored if log_config_append is set. |
| string value | The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is: driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query Example: rabbit://rabbitmq:password@127.0.0.1:5672// For full details on the fields in the URL see the documentation of oslo_messaging.TransportURL at https://docs.openstack.org/oslo.messaging/latest/reference/transport.html |
| boolean value | Enable journald for logging. If running in a systemd environment you may wish to enable journal support. Doing so will use the journal native protocol which includes structured metadata in addition to log messages.This option is ignored if log_config_append is set. |
| boolean value | Use JSON formatting for logging. This option is ignored if log_config_append is set. |
| boolean value | Use syslog for logging. Existing syslog format is DEPRECATED and will be changed later to honor RFC5424. This option is ignored if log_config_append is set. |
| boolean value | This option makes direct connections dynamic or static. It makes sense only with use_router_proxy=False which means to use direct connections for direct message types (ignored otherwise). |
| boolean value | Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. |
| boolean value | Use ROUTER remote proxy. |
| boolean value | Log output to standard error. This option is ignored if log_config_append is set. |
| boolean value | Uses logging handler designed to watch file system. When log file is moved or removed this handler will open a new log file with specified path instantaneously. It makes sense only if log_file option is specified and Linux platform is used. This option is ignored if log_config_append is set. |
| integer value | How many additional connections to a host will be made for failover reasons. This option is actual only in dynamic connections mode. |
| boolean value | This option configures round-robin mode in zmq socket. True means not keeping a queue when server side disconnects. False means to keep queue and messages even if server is disconnected, when the server appears we send all accumulated messages to it. |
| integer value | Number of seconds to wait before all pending messages will be sent after closing a socket. The default value of -1 specifies an infinite linger period. The value of 0 specifies no linger period. Pending messages shall be discarded immediately when the socket is closed. Positive values specify an upper bound for the linger period. |
| integer value | Expiration timeout in seconds of a name service record about existing target ( < 0 means no timeout). |
| integer value | Update period in seconds of a name service record about existing target. |
| integer value | Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any other negative value) means to skip any overrides and leave it to OS default; 0 and 1 (or any other positive value) mean to disable and enable the option respectively. |
| integer value | The number of retransmissions to be carried out before declaring that remote end is not available. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default. |
| integer value | The duration between two keepalive transmissions in idle condition. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default. |
| integer value | The duration between two successive keepalive retransmissions, if acknowledgement to the previous keepalive transmission is not received. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default. |
2.1.2. compute
The following table outlines the options available under the [compute]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Ceilometer offers many methods to discover the instance running on a compute node: * naive: poll nova to get all instances * workload_partitioning: poll nova to get instances of the compute * libvirt_metadata: get instances from libvirt metadata but without instance metadata (recommended for Gnocchi backend |
| integer value | The expiry to totally refresh the instances resource cache, since the instance may be migrated to another host, we need to clean the legacy instances info in local cache by totally refreshing the local cache. The minimum should be the value of the config option of resource_update_interval. This option is only used for agent polling to Nova API, so it will work only when instance_discovery_method is set to naive. |
| integer value | New instances will be discovered periodically based on this option (in seconds). By default, the agent discovers instances according to pipeline polling interval. If option is greater than 0, the instance list to poll will be updated based on this option’s interval. Measurements relating to the instances will match intervals defined in pipeline. This option is only used for agent polling to Nova API, so it will work only when instance_discovery_method is set to naive. |
2.1.3. coordination
The following table outlines the options available under the [coordination]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The backend URL to use for distributed coordination. If left empty, per-deployment central agent and per-host compute agent won’t do workload partitioning and will only function correctly if a single instance of that service is running. |
| floating point value | Number of seconds between checks to see if group membership has changed |
2.1.4. dispatcher_gnocchi
The following table outlines the options available under the [dispatcher_gnocchi]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The archive policy to use when the dispatcher create a new metric. |
| string value | Gnocchi project used to filter out samples generated by Gnocchi service activity |
| floating point value | Number of seconds before request to gnocchi times out |
| string value | The Yaml file that defines mapping between samples and gnocchi resources/metrics |
2.1.5. event
The following table outlines the options available under the [event]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Configuration file for event definitions. |
| boolean value | Drop notifications if no event definition matches. (Otherwise, we convert them with just the default traits) |
| multi valued | Store the raw notification for select priority levels (info and/or error). By default, raw details are not captured. |
2.1.6. hardware
The following table outlines the options available under the [hardware]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Configuration file for defining hardware snmp meters. |
| string value | SNMPd v3 authentication algorithm of all the nodes running in the cloud |
| string value | SNMPd user name of all nodes running in the cloud. |
| string value | SNMPd v3 authentication password of all the nodes running in the cloud. |
| string value | SNMPd v3 encryption password of all the nodes running in the cloud. |
| string value | SNMPd v3 encryption algorithm of all the nodes running in the cloud |
| string value | Name of the control plane Tripleo network |
| string value | URL scheme to use for hardware nodes. |
2.1.7. ipmi
The following table outlines the options available under the [ipmi]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of retries upon Intel Node Manager initialization failure |
| integer value | Tolerance of IPMI/NM polling failures before disable this pollster. Negative indicates retrying forever. |
2.1.8. matchmaker_redis
The following table outlines the options available under the [matchmaker_redis]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Time in ms to wait before the transaction is killed. |
| string value | Host to locate redis. |
`password = ` | string value | Password for Redis server (optional). |
| port value | Use this port to connect to redis host. |
| string value | Redis replica set name. |
| list value | List of Redis Sentinel hosts (fault tolerance mode), e.g., [host:port, host1:port … ] |
| integer value | Timeout in ms on blocking socket operations. |
| integer value | Time in ms to wait between connection attempts. |
2.1.9. meter
The following table outlines the options available under the [meter]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Configuration file for defining meter notifications. This option is deprecated and use meter_definitions_dirs to configure meter notification file. Meter definitions configuration file will be sought according to the parameter. |
| multi valued | List directory to find files of defining meter notifications. |
2.1.10. notification
The following table outlines the options available under the [notification]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Acknowledge message when event persistence fails. |
| integer value | Number of notification messages to wait before publishing them. Batching is advised when transformations are applied in pipeline. |
| integer value | Number of seconds to wait before publishing samples when batch_size is not reached (None means indefinitely) |
| multi valued | Messaging URLs to listen for notifications. Example: rabbit://user:pass@host1:port1[,user:pass@hostN:portN]/virtual_host (DEFAULT/transport_url is used if empty). This is useful when you have dedicate messaging nodes for each service, for example, all nova notifications go to rabbit-nova:5672, while all cinder notifications go to rabbit-cinder:5672. |
| multi valued | Exchanges name to listen for notifications. |
| integer value | Number of queues to parallelize workload across. This value should be larger than the number of active notification agents for optimal results. WARNING: Once set, lowering this value may result in lost data. |
| multi valued | Select which pipeline managers to enable to generate data |
| integer value | Number of workers for notification service, default value is 1. |
| boolean value | Enable workload partitioning, allowing multiple notification agents to be run simultaneously. |
2.1.11. oslo_concurrency
The following table outlines the options available under the [oslo_concurrency]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Enables or disables inter-process locks. |
| string value | Directory to use for lock files. For security, the specified directory should only be writable by the user running the processes that need locking. Defaults to environment variable OSLO_LOCK_PATH. If external locks are used, a lock path must be set. |
2.1.12. oslo_messaging_amqp
The following table outlines the options available under the [oslo_messaging_amqp]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Indicates the addressing mode used by the driver. Permitted values: legacy - use legacy non-routable addressing routable - use routable addresses dynamic - use legacy addresses if the message bus does not support routing otherwise use routable addressing |
| boolean value | Accept clients using either SSL or plain TCP |
| string value | Appended to the address prefix when sending to a group of consumers. Used by the message bus to identify messages that should be delivered in a round-robin fashion across consumers. |
| string value | address prefix used when broadcasting to all servers |
| integer value | Increase the connection_retry_interval by this many seconds after each unsuccessful failover attempt. |
| integer value | Seconds to pause before attempting to re-connect. |
| integer value | Maximum limit for connection_retry_interval + connection_retry_backoff |
| string value | Name for the AMQP container. must be globally unique. Defaults to a generated UUID |
| string value | Exchange name used in notification addresses. Exchange name resolution precedence: Target.exchange if set else default_notification_exchange if set else control_exchange if set else notify |
| integer value | The deadline for a sent notification message delivery. Only used when caller does not provide a timeout expiry. |
| integer value | The maximum number of attempts to re-send a reply message which failed due to a recoverable error. |
| integer value | The deadline for an rpc reply message delivery. |
| string value | Exchange name used in RPC addresses. Exchange name resolution precedence: Target.exchange if set else default_rpc_exchange if set else control_exchange if set else rpc |
| integer value | The deadline for an rpc cast or call message delivery. Only used when caller does not provide a timeout expiry. |
| integer value | The duration to schedule a purge of idle sender links. Detach link after expiry. |
| string value | address prefix when sending to any server in group |
| integer value | Timeout for inactive connections (in seconds) |
| integer value | Time to pause between re-connecting an AMQP 1.0 link that failed due to a recoverable error. |
| string value | Appended to the address prefix when sending a fanout message. Used by the message bus to identify fanout messages. |
| string value | Address prefix for all generated Notification addresses |
| integer value | Window size for incoming Notification messages |
`password = ` | string value | Password for message broker authentication |
| multi valued | Send messages of this type pre-settled. Pre-settled messages will not receive acknowledgement from the peer. Note well: pre-settled messages may be silently discarded if the delivery fails. Permitted values: rpc-call - send RPC Calls pre-settled rpc-reply- send RPC Replies pre-settled rpc-cast - Send RPC Casts pre-settled notify - Send Notifications pre-settled |
| boolean value | Enable virtual host support for those message buses that do not natively support virtual hosting (such as qpidd). When set to true the virtual host name will be added to all message bus addresses, effectively creating a private subnet per virtual host. Set to False if the message bus supports virtual hosting using the hostname field in the AMQP 1.0 Open performative as the name of the virtual host. |
| integer value | Window size for incoming RPC Reply messages. |
| string value | Address prefix for all generated RPC addresses |
| integer value | Window size for incoming RPC Request messages |
`sasl_config_dir = ` | string value | Path to directory that contains the SASL configuration |
`sasl_config_name = ` | string value | Name of configuration file (without .conf suffix) |
`sasl_default_realm = ` | string value | SASL realm to use if no realm present in username |
`sasl_mechanisms = ` | string value | Space separated list of acceptable SASL mechanisms |
| string value | address prefix used when sending to a specific server |
| boolean value | Attempt to connect via SSL. If no other ssl-related parameters are given, it will use the system’s CA-bundle to verify the server’s certificate. |
`ssl_ca_file = ` | string value | CA certificate PEM file used to verify the server’s certificate |
`ssl_cert_file = ` | string value | Self-identifying certificate PEM file for client authentication |
`ssl_key_file = ` | string value | Private key PEM file used to sign ssl_cert_file certificate (optional) |
| string value | Password for decrypting ssl_key_file (if encrypted) |
| boolean value | By default SSL checks that the name in the server’s certificate matches the hostname in the transport_url. In some configurations it may be preferable to use the virtual hostname instead, for example if the server uses the Server Name Indication TLS extension (rfc6066) to provide a certificate per virtual host. Set ssl_verify_vhost to True if the server’s SSL certificate uses the virtual host name instead of the DNS name. |
| boolean value | Debug: dump AMQP frames to stdout |
| string value | Appended to the address prefix when sending to a particular RPC/Notification server. Used by the message bus to identify messages sent to a single destination. |
`username = ` | string value | User name for message broker authentication |
2.1.13. oslo_messaging_kafka
The following table outlines the options available under the [oslo_messaging_kafka]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | The pool size limit for connections expiration policy |
| integer value | The time-to-live in sec of idle connections in the pool |
| string value | Group id for Kafka consumer. Consumers in one group will coordinate message consumption |
| floating point value | Default timeout(s) for Kafka consumers |
| string value | Default Kafka broker Host |
| port value | Default Kafka broker Port |
| integer value | Max fetch bytes of Kafka consumer |
| integer value | Pool Size for Kafka Consumers |
| integer value | Size of batch for the producer async send |
| floating point value | Upper bound on the delay for KafkaProducer batching in seconds |
2.1.14. oslo_messaging_notifications
The following table outlines the options available under the [oslo_messaging_notifications]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| multi valued | The Drivers(s) to handle sending notifications. Possible values are messaging, messagingv2, routing, log, test, noop |
| integer value | The maximum number of attempts to re-send a notification message which failed to be delivered due to a recoverable error. 0 - No retry, -1 - indefinite |
| list value | AMQP topic used for OpenStack notifications. |
| string value | A URL representing the messaging driver to use for notifications. If not set, we fall back to the same configuration used for RPC. |
2.1.15. oslo_messaging_rabbit
The following table outlines the options available under the [oslo_messaging_rabbit]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Auto-delete queues in AMQP. |
| boolean value | Use durable queues in AMQP. |
| integer value | Maximum number of channels to allow |
| string value | Connection factory implementation |
| string value | Exchange name for sending notifications |
| integer value | Reconnecting retry count in case of connectivity problem during sending notification, -1 means infinite retry. |
| string value | Exchange name for sending RPC messages |
| integer value | Reconnecting retry count in case of connectivity problem during sending RPC message, -1 means infinite retry. If actual retry attempts in not 0 the rpc request could be processed more than one time |
| string value | Default serialization mechanism for serializing/deserializing outgoing/incoming messages |
| boolean value | Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake |
| integer value | The maximum byte size for an AMQP frame |
| integer value | How often to send heartbeats for consumer’s connections |
| integer value | How often times during the heartbeat_timeout_threshold we check the heartbeat. |
| integer value | Number of seconds after which the Rabbit broker is considered down if heartbeat’s keep-alive fails (0 disable the heartbeat). EXPERIMENTAL |
| floating point value | Set delay for reconnection to some host which has connection error |
| string value | EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not be used. This option may not be available in future versions. |
| string value | Determines how the next RabbitMQ node is chosen in case the one we are currently connected to becomes unavailable. Takes effect only if more than one RabbitMQ node is provided in config. |
| integer value | How long to wait a missing client before abandoning to send it its replies. This value should not be longer than rpc_response_timeout. |
| floating point value | How long to wait before reconnecting in response to an AMQP consumer cancel notification. |
| integer value | Max number of not acknowledged message which RabbitMQ can send to notification listener. |
| boolean value | Persist notification messages. |
| floating point value | Reconnecting retry delay in case of connectivity problem during sending notification message |
| integer value |
Maximum number of connections to create above |
| integer value | Maximum number of connections to keep queued. |
| integer value | Lifetime of a connection (since creation) in seconds or None for no recycling. Expired connections are closed on acquire. |
| integer value | Threshold at which inactive (since release) connections are considered stale in seconds or None for no staleness. Stale connections are closed on acquire. |
| integer value | Default number of seconds to wait for a connections to available |
| boolean value | Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring is no longer controlled by the x-ha-policy argument when declaring a queue. If you just want to make sure that all queues (except those with auto-generated names) are mirrored across all nodes, run: "rabbitmqctl set_policy HA ^(?!amq\.).* {"ha-mode": "all"} " |
| string value | The RabbitMQ broker address where a single node is used. |
| list value | RabbitMQ HA cluster host:port pairs. |
| integer value | Maximum interval of RabbitMQ connection retries. Default is 30 seconds. |
| string value | The RabbitMQ login method. |
| integer value | Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count). |
| string value | The RabbitMQ password. |
| port value | The RabbitMQ broker port where a single node is used. |
| integer value | Specifies the number of messages to prefetch. Setting to zero allows unlimited messages. |
| integer value | How long to backoff for between retries when connecting to RabbitMQ. |
| integer value | How frequently to retry connecting with RabbitMQ. |
| integer value | Positive integer representing duration in seconds for queue TTL (x-expires). Queues which are unused for the duration of the TTL are automatically deleted. The parameter affects only reply and fanout queues. |
| string value | The RabbitMQ userid. |
| string value | The RabbitMQ virtual host. |
| integer value | Max number of not acknowledged message which RabbitMQ can send to rpc listener. |
| integer value | Time to live for rpc queues without consumers in seconds. |
| string value | Exchange name for receiving RPC replies |
| integer value | Max number of not acknowledged message which RabbitMQ can send to rpc reply listener. |
| integer value | Reconnecting retry count in case of connectivity problem during sending reply. -1 means infinite retry during rpc_timeout |
| floating point value | Reconnecting retry delay in case of connectivity problem during sending reply. |
| floating point value | Reconnecting retry delay in case of connectivity problem during sending RPC message |
| floating point value | Set socket timeout in seconds for connection’s socket |
| boolean value | Enable SSL |
`ssl_ca_file = ` | string value | SSL certification authority file (valid only if SSL enabled). |
`ssl_cert_file = ` | string value | SSL cert file (valid only if SSL enabled). |
`ssl_key_file = ` | string value | SSL key file (valid only if SSL enabled). |
| dict value | Arguments passed to ssl.wrap_socket |
`ssl_version = ` | string value | SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some distributions. |
| floating point value | Set TCP_USER_TIMEOUT in seconds for connection’s socket |
2.1.16. oslo_messaging_zmq
The following table outlines the options available under the [oslo_messaging_zmq]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of seconds to wait for an ack from a cast/call. After each retry attempt this timeout is multiplied by some specified multiplier. |
| integer value | Number to multiply base ack timeout by after each retry attempt. |
| integer value | Expiration timeout in seconds of a sent/received message after which it is not tracked anymore by a client/server. |
| integer value | The default number of seconds that poll should wait. Poll raises timeout exception when timeout expired. |
| integer value | Default number of message sending attempts in case of any problems occurred: positive value N means at most N retries, 0 means no retries, None or -1 (or any other negative values) mean to retry forever. This option is used only if acknowledgments are enabled. |
| integer value | Maximum number of (green) threads to work concurrently. |
| boolean value | Wait for message acknowledgements from receivers. This mechanism works only via proxy without PUB/SUB. |
| string value | ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP. The "host" option should point or resolve to this address. |
| integer value | Number of retries to find free port number before fail with ZMQBindError. |
| integer value | Number of ZeroMQ contexts, defaults to 1. |
| string value | Name of this node. Must be a valid hostname, FQDN, or IP address. Must match "host" option, if running Nova. |
| string value | Directory for holding IPC sockets. |
| string value | MatchMaker driver. |
| integer value | Maximal port number for random ports range. |
| port value | Minimal port number for random ports range. |
| string value | Default serialization mechanism for serializing/deserializing outgoing/incoming messages |
| integer value | Maximum number of ingress messages to locally buffer per topic. Default is unlimited. |
| list value | List of publisher hosts SubConsumer can subscribe on. This option has higher priority then the default publishers list taken from the matchmaker. |
| boolean value | This option makes direct connections dynamic or static. It makes sense only with use_router_proxy=False which means to use direct connections for direct message types (ignored otherwise). |
| boolean value | Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. |
| boolean value | Use ROUTER remote proxy. |
| integer value | How many additional connections to a host will be made for failover reasons. This option is actual only in dynamic connections mode. |
| boolean value | This option configures round-robin mode in zmq socket. True means not keeping a queue when server side disconnects. False means to keep queue and messages even if server is disconnected, when the server appears we send all accumulated messages to it. |
| integer value | Number of seconds to wait before all pending messages will be sent after closing a socket. The default value of -1 specifies an infinite linger period. The value of 0 specifies no linger period. Pending messages shall be discarded immediately when the socket is closed. Positive values specify an upper bound for the linger period. |
| integer value | Expiration timeout in seconds of a name service record about existing target ( < 0 means no timeout). |
| integer value | Update period in seconds of a name service record about existing target. |
| integer value | Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any other negative value) means to skip any overrides and leave it to OS default; 0 and 1 (or any other positive value) mean to disable and enable the option respectively. |
| integer value | The number of retransmissions to be carried out before declaring that remote end is not available. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default. |
| integer value | The duration between two keepalive transmissions in idle condition. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default. |
| integer value | The duration between two successive keepalive retransmissions, if acknowledgement to the previous keepalive transmission is not received. The unit is platform dependent, for example, seconds in Linux, milliseconds in Windows etc. The default value of -1 (or any other negative value and 0) means to skip any overrides and leave it to OS default. |
2.1.17. polling
The following table outlines the options available under the [polling]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Configuration file for polling definition. |
| string value | Work-load partitioning group prefix. Use only if you want to run multiple polling agents with different config files. For each sub-group of the agent pool with the same partitioning_group_prefix a disjoint subset of pollsters should be loaded. |
2.1.18. publisher
The following table outlines the options available under the [publisher]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Secret value for signing messages. Set value empty if signing is not required to avoid computational overhead. |
2.1.19. publisher_notifier
The following table outlines the options available under the [publisher_notifier]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The topic that ceilometer uses for event notifications. |
| string value | The topic that ceilometer uses for metering notifications. |
| string value | The driver that ceilometer uses for metering notifications. |
2.1.20. rgw_admin_credentials
The following table outlines the options available under the [rgw_admin_credentials]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Access key for Radosgw Admin. |
| string value | Secret key for Radosgw Admin. |
2.1.21. service_credentials
The following table outlines the options available under the [service_credentials]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Authentication URL |
| string value | Config Section from which to load plugin specific options |
| string value | Authentication type to load |
| string value | Optional domain ID to use with v3 and v2 parameters. It will be used for both the user and project domain in v3 and ignored in v2 authentication. |
| string value | Optional domain name to use with v3 API and v2 parameters. It will be used for both the user and project domain in v3 and ignored in v2 authentication. |
| string value | Domain ID to scope to |
| string value | Domain name to scope to |
| string value | Type of endpoint in Identity service catalog to use for communication with OpenStack services. |
| string value | User’s password |
| string value | Domain ID containing project |
| string value | Domain name containing project |
| string value | Project ID to scope to |
| string value | Project name to scope to |
| string value | Region name to use for OpenStack service endpoints. |
| string value | Scope for system operations |
| string value | Trust ID |
| string value | User’s domain id |
| string value | User’s domain name |
| string value | User id |
| string value | Username |
2.1.22. service_types
The following table outlines the options available under the [service_types]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Cinder service type. |
| string value | Glance service type. |
| string value | Neutron service type. |
| string value | Neutron load balancer version. |
| string value | Nova service type. |
| string value | Radosgw service type. |
| string value | Swift service type. |
2.1.23. vmware
The following table outlines the options available under the [vmware]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Number of times a VMware vSphere API may be retried. |
| string value | CA bundle file to use in verifying the vCenter server certificate. |
| unknown value | IP address of the VMware vSphere host. |
`host_password = ` | string value | Password of VMware vSphere. |
| port value | Port of the VMware vSphere host. |
`host_username = ` | string value | Username of VMware vSphere. |
| boolean value | If true, the vCenter server certificate is not verified. If false, then the default CA truststore is used for verification. This option is ignored if "ca_file" is set. |
| floating point value | Sleep time in seconds for polling an ongoing async task. |
| string value | Optional vim service WSDL location e.g http://<server>/vimService.wsdl. Optional over-ride to default location for bug work-arounds. |
2.1.24. xenapi
The following table outlines the options available under the [xenapi]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Password for connection to XenServer/Xen Cloud Platform. |
| string value | URL for connection to XenServer/Xen Cloud Platform. |
| string value | Username for connection to XenServer/Xen Cloud Platform. |