5c1000ae37
Change-Id: I4fb8ebf4af52fdece4dc0ba534484bc70aef1e6e
31 lines
1.3 KiB
XML
31 lines
1.3 KiB
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<para xmlns="http://docbook.org/ns/docbook" version="5.0">
|
|
<!-- Warning: Do not edit this file. It is automatically
|
|
generated and your changes will be overwritten.
|
|
The tool to do so lives in openstack-doc-tools repository. -->
|
|
<table rules="all" xml:id="config_table_ceilometer_notification">
|
|
<caption>Description of notification configuration options</caption>
|
|
<col width="50%"/>
|
|
<col width="50%"/>
|
|
<thead>
|
|
<tr>
|
|
<th>Configuration option = Default value</th>
|
|
<th>Description</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<th colspan="2">[notification]</th>
|
|
</tr>
|
|
<tr>
|
|
<td><option>disable_non_metric_meters</option> = <replaceable>True</replaceable></td>
|
|
<td>(BoolOpt) WARNING: Ceilometer historically offered the ability to store events as meters. This usage is NOT advised as it can flood the metering database and cause performance degradation.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><option>pipeline_processing_queues</option> = <replaceable>10</replaceable></td>
|
|
<td>(IntOpt) Number of queues to parallelize workload across. This value should be larger than the number of active notification agents for optimal results.</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</para>
|