[osprofiler][rally][openstack] Using osprofiler/rally directly on production Openstack system

Andriy Kurilin andr.kurilin at gmail.com
Mon Mar 6 23:09:51 UTC 2023


Hi!

OSProfiler enables tracing only requests with a special header. The header
is not embedded in each request (even if you configure osprofiler in your
system), you need to use a special CLI argument to set it. So even if the
tracing of one particular request slows done the flow (which should not
happen), it should give zero impact on the performance of the whole system.

As for Rally (in particular, the task component), it creates resources with
a special naming format that allows to filter out only these resources
during the cleanup process. We are using Rally in production as a part of
the monitoring for ~5 years or so.

пн, 6 мар. 2023 г. в 23:34, hai wu <haiwu.us at gmail.com>:

> Is there any concern with using osprofiler/rally directly on the
> production Openstack system?
>
>

-- 
Best regards,
Andrey Kurilin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230307/2f0f9203/attachment.htm>


More information about the openstack-discuss mailing list