openstack/ceilometer
Code Issues Proposed changes
ceilometer/doc/source/admin/telemetry-best-practices.rst
Mehdi Abaakouk 1dcbd607df Deprecating transformers and pipeline partitioning 
Theses features doesn't work well, rate-of-change metrics can still
wrongly be computed even with Pipeline partioning enabled. Also backend
like Gnocchi offers a better alternative to compute them.

This deprecates these two features, to be able to remove them in a couple
of releases.

Change-Id: I52362c69b7d500bfe6dba76f78403a9d376deb80
2018-04-20 10:45:45 +02:00

1.1 KiB
Raw Blame History

Telemetry best practices

The following are some suggested best practices to follow when deploying and configuring the Telemetry service.

Data collection

  1. The Telemetry service collects a continuously growing set of data. Not all the data will be relevant for an administrator to monitor.

    • Based on your needs, you can edit the polling.yaml and pipeline.yaml configuration files to include select meters to generate or process

    • By default, Telemetry service polls the service APIs every 10 minutes. You can change the polling interval on a per meter basis by editing the polling.yaml configuration file.

      Warning

      If the polling interval is too short, it will likely increase the stress on the service APIs.

  2. If polling many resources or at a high frequency, you can add additional central and compute agents as necessary. The agents are designed to scale horizontally. For more information refer to the high availability guide.