Description of problem: Can we have telemetry example in downstream as well. Please follow the following upstream doc, https://docs.openstack.org/aodh/latest/admin/telemetry-alarms.html Version-Release number of selected component (if applicable): RHOSP 10 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Reviewed the existing guide: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/logging_monitoring_and_troubleshooting_guide/#monitoring_using_the_telemetry_service Identified a few gaps that should be documented: * Describe alarm dimensioning * Describe composite alarms * Describe alarm types: --type event --type composite These should be added to the OSP11 guide, and backported to OSP10, where appropriate.
Identified use case in BZ#1467317. Created draft text for `--type event`. ---- This alarm raises an event when a particular instance is shutdown: aodh alarm create \ --type event \ --name instance_off \ --description 'event_instance_power_off' \ --event-type "compute.instance.power_off.*" \ --enable True \ --query "traits.instance_id=string::ac917539-fa21-42fb-bac6-c3a795f056e" \ --alarm-action 'log://' \ --ok-action 'log://' \ --insufficient-data-action 'log://' \ --resource-type instance ----
also elaborate on -alarm-action options, such as a webhook URL
Emailed questions to SME.
Also update examples to use the `ge` operator, where appropriate.
Update: don't cover composite alarms
See also https://access.redhat.com/solutions/2953931
See also https://access.redhat.com/solutions/2953041
Adding in updates from tech review
Hey Martin, Looks good overall. Included a couple of minor comments in gitlab. Feel free to merge once updated. -Deepti
Added updates from peer review.
Guide has been updated: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/logging_monitoring_and_troubleshooting_guide/#example_monitor_cpu_usage