Bug 2027516 - OSP17 | collectd-sensubility doesn't report status of containers. Seems like parsing script on overcloud side needs to be updated.
Summary: OSP17 | collectd-sensubility doesn't report status of containers. Seems like ...
Keywords:
Status: CLOSED DUPLICATE of bug 2037413
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: collectd-sensubility
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 17.0
Assignee: Martin Magr
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-29 21:20 UTC by Leonid Natapov
Modified: 2022-01-07 10:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-07 10:27:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-11105 0 None Waiting on Customer Zabbix監視で使用しているpodmanコマンドがある期間timeoutとなった。 2022-04-27 03:14:59 UTC
Red Hat Issue Tracker STF-904 0 None None None 2021-11-29 21:23:00 UTC

Description Leonid Natapov 2021-11-29 21:20:54 UTC 
OSP17 | collectd-sensubility doesn't report a status of containers. Seems like parsing script on overcloud side needs to be updated.  

sensubility.log files doesn't include nova-api,neutron-api,heat-api services.
I also see swrvices named "Red" or "rhosp17" in the sensubility log file.
It looks like parsing is not correct and needs to be adapted for OSP17.

Example1:
"container\\\": \\\"558c0a3549cc30cadc493e8c8bbe39548f4b56e9d21d49c3b78d100e26b3ff37\\\", \\\"service\\\": \\\"Red\\\", \\\"status\\\": \\\"healthy\\\", \\\"healthy

Example2:
"container\\\": \\\"36f89dda840e7be20c9d01cbead607e59bebde8b91a1039ebe4db6f125410c16\\\", \\\"service\\\": \\\"rhosp17\\\", \\\"status\\\": \\\"healthy\\\",
Comment 5 Martin Magr 2022-01-07 10:27:10 UTC 
Aparently collectd-sensubility was not available during your OSP17 testing (see linked BZ). Let's close this now and in case you will hit sensubility issue, we can revive it.

*** This bug has been marked as a duplicate of bug 2037413 ***
Note You need to log in before you can comment on or make changes to this bug.