Bug 1763711
| Summary: | [CLOUDOPS] STF Metric Request - Component Metrics in STF Dashboards | ||
|---|---|---|---|
| Product: | Service Telemetry Framework | Reporter: | Joshua Bulger <jbulger> |
| Component: | distribution | Assignee: | Paul Leimer <pleimer> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 1.1 | CC: | augol, jjoyce, joflynn, leif.madsen, lmadsen, mburns, mmagr, moddi, mrunge, pkilambi, pleimer, rmccabe, shrjoshi, spower |
| Target Milestone: | GA | Keywords: | Triaged |
| Target Release: | 1.2 (STF) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | service-telemetry-operator-container-1.2.0-9 | Doc Type: | Release Note |
| Doc Text: |
When you use Service Telemetry Framework (STF) 1.2 with Red Hat OpenStack Platform (RHOSP) 16.1.3 or later, you can now monitor RHOSP services, such as Dashboard (horizon), Ceph Storage, Compute (nova), and ceilometer.
An example implementation of this is shown in the STF dashboards provided at https://github.com/infrawatch/dashboards/blob/master/deploy/rhos-cloud-dashboard.yaml within the Service Resource Usage panel.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-23 19:18:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1844144 | ||
| Bug Blocks: | |||
|
Description
Joshua Bulger
2019-10-21 12:08:38 UTC
We're going to have to develop a way of getting infrastructure metrics associated with a particular process, perhaps through some sort of custom filters or regex in the collectd configuration to search for the components in OpenStack that we want to call out specifically. These requirements should be satisfied by https://bugzilla.redhat.com/show_bug.cgi?id=1844144 @pleimer can we use this BZ to target the dashboarding work in STF once the libpod-stats-collectd is landed for RHOSP 16.1.3? If so, please update the description just so it's a bit more clear that this is for the dashboard work, and then can you link the libpod-stats-collectd BZs to this BZ. Please mark it as "Depends On" for any BZs that are required on the OSP side to get the telemetry/data for the dashboard. @leif.madsen yes I suppose we can do that @pleimer pretty sure the dashboarding work is done (that's what you demo'd during happy hour?). Is there an upstream link or something we can get added to this BZ? We'll also need to create a release note for the STF 1.2 release. I know there is some missing functionality coming in 16.1.4, but I don't know what that is. Can you shoot me a link for that? I'd like to understand what we won't get in STF 1.2 right away with 16.1.3. I think we should make sure the dashboard work that satisfies this BZ should be compatible with whatever is available in 16.1.3, so we might want to make a copy of the current thing if it needs to be adjusted. We can call the current dashboard 16.1.4 compatible if necessary. Now that Martin's build for sensubility merged, all dashboard dependencies are satisfied in z3. I attached the upstream link for the dashboard that satisfies this requirement Moving to POST as the RHOSP supporting changes are available in the 16.1.3 puddle currently. We'll move this to MODIFIED once we have a service-telemetry-operator-container build for STF 1.2. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Service Telemetry Framework 1.2 - Operator Container), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:0649 |