Bug 2141683
| Summary: | [RHOSP 18.0] Remove sensubility from distribution | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Martin Magr <mmagr> |
| Component: | collectd-sensubility | Assignee: | Martin Magr <mmagr> |
| Status: | ON_DEV --- | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | mgeary <mgeary> |
| Priority: | medium | ||
| Version: | 18.0 (Zed) | CC: | jamparke, joflynn, jschluet, lmadsen, lnatapov, mrunge |
| Target Milestone: | ga | Keywords: | FutureFeature, Triaged |
| Target Release: | 18.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Removed functionality | |
| Doc Text: |
Sensubility has been removed from Red Hat OpenStack Platform. It was used as part of the OpsTools tooling system for interfacing with Sensu, which has been replaced by Service Telemetry Framework (STF).
Since RHOSP 13 sensubility has been used as an interface to allow service health checks to be transported to STF. We have removed the sensubility interface which is not necessary for health check telemetry transport, and is now replaced with a simpler interface via collectd-exec plugin, allowing data to flow through existing telemetry transport interfaces.
From an administrators perspective, the only change is to the labels exposed in the `collectd_container_health_status_bool`, with the `instance_type` label changing value from `healthy` to `base`. The metric value itself continues to be expressed as boolean with values 0 (unhealthy) or 1 (healthy).
|
Story Points: | --- |
| Clone Of: | 2136445 | Environment: | |
| Last Closed: | Type: | --- | |
| 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: | 2136445 | ||
| Bug Blocks: | |||
|
Description
Martin Magr
2022-11-10 13:24:16 UTC
|