Chapter 2. ceilometer
The following chapter contains information about the configuration options in the ceilometer
service.
2.1. ceilometer.conf Copy linkLink copied to clipboard!
This section contains options for the /etc/ceilometer/ceilometer.conf
file.
2.1.1. DEFAULT Copy linkLink copied to clipboard!
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. Inside the path {pid} will be replaced with the PID of the current process. |
| integer value | Batch size of samples to send to notification agent, Set to 0 to disable |
| string value | Configuration file for polling definition. |
| 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. |
| host address 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. Note that xenapi has been deprecated. |
`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, log-date-format). |
| 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). |
| integer value | The amount of time before the log files are rotated. This option is ignored unless log_rotation_type is setto "interval". |
| string value | Rotation interval type. The time of the last file change (or the time when the service was started) is used when scheduling the next rotation. |
| string value | Log rotation type. |
| string value | Format string to use for log messages with context. Used by oslo_log.formatters.ContextFormatter |
| string value | Additional data to append to log message when logging level for the message is DEBUG. Used by oslo_log.formatters.ContextFormatter |
| string value | Format string to use for log messages when context is undefined. Used by oslo_log.formatters.ContextFormatter |
| string value | Prefix each line of exception output with this format. Used by oslo_log.formatters.ContextFormatter |
| string value | Defines the format string for %(user_identity)s that is used in logging_context_format_string. Used by oslo_log.formatters.ContextFormatter |
| integer value | Maximum number of rotated log files. |
| integer value | Log file maximum size in MB. This option is ignored if "log_rotation_type" is not set to "size". |
| integer value | Maximum number of parallel requests for services to handle at the same time. |
| 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. |
| string value | Configuration file for pipeline definition. |
| multi valued | List of directories with YAML files used to created pollsters. |
| 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 | Size of RPC connection pool. |
| boolean value | Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping |
| integer value | Seconds to wait for a response from a call. |
| string value | Source for samples emitted on this instance. |
| string value | Syslog facility to receive log lines. This option is ignored if log_config_append is set. |
| boolean value | Identify project and user names from polled samples. By default, collecting these values is disabled due to the fact that it could overwhelm keystone servicewith lots of continuous requests depending upon the number of projects, users and samples polled from the environment. While using this feature, it is recommended that ceilometer be configured with a caching backend to reduce the number of calls made to keystone. |
| 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 | Log output to Windows Event Log. |
| 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. |
2.1.2. cache Copy linkLink copied to clipboard!
The following table outlines the options available under the [cache]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | Cache backend module. For eventlet-based or environments with hundreds of threaded servers, Memcache with pooling (oslo_cache.memcache_pool) is recommended. For environments with less than 100 threaded servers, Memcached (dogpile.cache.memcached) or Redis (dogpile.cache.redis) is recommended. Test environments with a single instance of the server can use the dogpile.cache.memory backend. |
| multi valued | Arguments supplied to the backend module. Specify this option once per argument to be passed to the dogpile.cache backend. Example format: "<argname>:<value>". |
| string value | Prefix for building the configuration dictionary for the cache region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name. |
| floating point value | Time in seconds before attempting to add a node back in the pool in the HashClient’s internal mechanisms. |
| boolean value | Extra debugging from the cache backend (cache keys, get/set/delete/etc calls). This is only really useful if you need to see the specific cache-backend get/set/delete calls with the keys/values. Typically this should be left set to false. |
| boolean value | Enable retry client mechanisms to handle failure. Those mechanisms can be used to wrap all kind of pymemcache clients. The wrapper allows you to define how many attempts to make and how long to wait between attemots. |
| boolean value | Global toggle for the socket keepalive of dogpile’s pymemcache backend |
| boolean value | Global toggle for caching. |
| integer value | Default TTL, in seconds, for any cached item in the dogpile.cache region. This applies to any cached method that doesn’t have an explicit cache expiration time defined for it. |
| integer value | Amount of times a client should be tried before it is marked dead and removed from the pool in the HashClient’s internal mechanisms. |
| floating point value | Time in seconds that should pass between retry attempts in the HashClient’s internal mechanisms. |
| integer value | Number of seconds memcached server is considered dead before it is tried again. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only). |
| integer value | Number of seconds that an operation will wait to get a memcache client connection. |
| boolean value | Global toggle if memcache will be flushed on reconnect. (oslo_cache.memcache_pool backend only). |
| integer value | Max total number of open connections to every memcached server. (oslo_cache.memcache_pool backend only). |
| integer value | Number of seconds a connection to memcached is held unused in the pool before it is closed. (oslo_cache.memcache_pool backend only). |
| list value |
Memcache servers in the format of "host:port". (dogpile.cache.memcached and oslo_cache.memcache_pool backends only). If a given host refer to an IPv6 or a given domain refer to IPv6 then you should prefix the given address with the address family ( |
| floating point value | Timeout in seconds for every call to a server. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only). |
| list value | Proxy classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior. |
| integer value | Number of times to attempt an action before failing. |
| floating point value | Number of seconds to sleep between each attempt. |
| integer value | The maximum number of keepalive probes TCP should send before dropping the connection. Should be a positive integer greater than zero. |
| integer value | The time (in seconds) the connection needs to remain idle before TCP starts sending keepalive probes. Should be a positive integer most greater than zero. |
| integer value | The time (in seconds) between individual keepalive probes. Should be a positive integer greater than zero. |
| string value | Set the available ciphers for sockets created with the TLS context. It should be a string in the OpenSSL cipher list format. If not specified, all OpenSSL enabled ciphers will be available. |
| string value | Path to a file of concatenated CA certificates in PEM format necessary to establish the caching servers' authenticity. If tls_enabled is False, this option is ignored. |
| string value | Path to a single file in PEM format containing the client’s certificate as well as any number of CA certificates needed to establish the certificate’s authenticity. This file is only required when client side authentication is necessary. If tls_enabled is False, this option is ignored. |
| boolean value | Global toggle for TLS usage when comunicating with the caching servers. |
| string value | Path to a single file containing the client’s private key in. Otherwhise the private key will be taken from the file specified in tls_certfile. If tls_enabled is False, this option is ignored. |
2.1.3. compute Copy linkLink copied to clipboard!
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.4. coordination Copy linkLink copied to clipboard!
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.5. event Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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. meter Copy linkLink copied to clipboard!
The following table outlines the options available under the [meter]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| multi valued | List directory to find files of defining meter notifications. |
2.1.9. monasca Copy linkLink copied to clipboard!
The following table outlines the options available under the [monasca]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | When turned on, archives metrics in file system when publish to Monasca fails or metric publish maxes out retry attempts. |
| string value | File of metrics that failed to publish to Monasca. These include metrics that failed to publish on first attempt and failed metrics that maxed out their retries. |
| integer value | Maximum number of samples in a batch. |
| integer value | Maximum number of retry attempts on a publishing failure to Monasca API. |
| boolean value | Indicates whether samples are published in a batch. |
| integer value | Frequency of checking if batch criteria is met. |
| integer value | Maximum time interval(seconds) after which samples are published in a batch. |
| integer value | Maximum number of retry attempts of connecting to Monasca API. |
| integer value | Frequency of attempting a retry connecting to Monasca API. |
| string value | Version of Monasca client to use while publishing. |
| string value | The name of cloud |
| string value | The name of cluster |
| string value | The name of control plane |
| boolean value | Enable paging through monasca api resultset. |
| string value | Monasca static and dynamic field mappings |
| boolean value | Indicates whether publisher retries publishing sample in case of failure. Only a few error cases are queued for a retry. |
2.1.10. notification Copy linkLink copied to clipboard!
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. |
| 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. |
| multi valued | Select which pipeline managers to enable to generate data |
| integer value | Number of workers for notification service, default value is 1. |
2.1.11. oslo_concurrency Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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 |
| 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 |
| 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. |
2.1.13. oslo_messaging_kafka Copy linkLink copied to clipboard!
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 |
---|---|---|
| string value | The compression codec for all data generated by the producer. If not set, compression will not be used. Note that the allowed values of this depend on the kafka version |
| 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 |
| boolean value | Enable asynchronous consumer commits |
| floating point value | Default timeout(s) for Kafka consumers |
| integer value | Max fetch bytes of Kafka consumer |
| integer value | The maximum number of records returned in a poll call |
| 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 |
| string value | Mechanism when security protocol is SASL |
| string value | Protocol used to communicate with brokers |
`ssl_cafile = ` | string value | CA certificate PEM file used to verify the server certificate |
`ssl_client_cert_file = ` | string value | Client certificate PEM file used for authentication. |
`ssl_client_key_file = ` | string value | Client key PEM file used for authentication. |
`ssl_client_key_password = ` | string value | Client key password file used for authentication. |
2.1.14. oslo_messaging_notifications Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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. |
| boolean value | (DEPRECATED) Enable/Disable the RabbitMQ mandatory flag for direct send. The direct send is used as reply, so the MessageUndeliverable exception is raised in case the client queue does not exist.MessageUndeliverable exception will be used to loop for a timeout to lets a chance to sender to recover.This flag is deprecated and it will not be possible to deactivate this functionality anymore |
| boolean value | Enable x-cancel-on-ha-failover flag so that rabbitmq server will cancel and notify consumerswhen queue is down |
| boolean value | Run the health check heartbeat thread through a native python thread by default. If this option is equal to False then the health check heartbeat will inherit the execution model from the parent process. For example if the parent process has monkey patched the stdlib by using eventlet/greenlet then the heartbeat will be run through a green thread. This option should be set to True only for the wsgi services. |
| 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 disables heartbeat). |
| 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. |
| 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"} " |
| integer value | Maximum interval of RabbitMQ connection retries. Default is 30 seconds. |
| string value | The RabbitMQ login method. |
| 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. |
| boolean value | Connect over 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). |
`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. |
2.1.16. oslo_reports Copy linkLink copied to clipboard!
The following table outlines the options available under the [oslo_reports]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| string value | The path to a file to watch for changes to trigger the reports, instead of signals. Setting this option disables the signal trigger for the reports. If application is running as a WSGI application it is recommended to use this instead of signals. |
| integer value | How many seconds to wait between polls when file_event_handler is set |
| string value | Path to a log directory where to create a file |
2.1.17. polling Copy linkLink copied to clipboard!
The following table outlines the options available under the [polling]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| integer value | Batch size of samples to send to notification agent, Set to 0 to disable |
| 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. |
| multi valued | List of directories with YAML files used to created pollsters. |
| boolean value | Identify project and user names from polled samples. By default, collecting these values is disabled due to the fact that it could overwhelm keystone servicewith lots of continuous requests depending upon the number of projects, users and samples polled from the environment. While using this feature, it is recommended that ceilometer be configured with a caching backend to reduce the number of calls made to keystone. |
2.1.18. publisher Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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 Copy linkLink copied to clipboard!
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. rgw_client Copy linkLink copied to clipboard!
The following table outlines the options available under the [rgw_client]
group in the /etc/ceilometer/ceilometer.conf
file.
Configuration option = Default value | Type | Description |
---|---|---|
| boolean value | Whether RGW uses implicit tenants or not. |
2.1.22. service_credentials Copy linkLink copied to clipboard!
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.23. service_types Copy linkLink copied to clipboard!
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.24. vmware Copy linkLink copied to clipboard!
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. |
| host address 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.25. xenapi Copy linkLink copied to clipboard!
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. |