Bug 1784065 - Create a dedicated log file for the healtcheck runs
Summary: Create a dedicated log file for the healtcheck runs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Cédric Jeanneret
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On: 1784043 1784046
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-16 15:40 UTC by Cédric Jeanneret
Modified: 2020-03-05 12:01 UTC (History)
3 users (show)

Fixed In Version: openstack-tripleo-heat-templates-10.6.3-0.20200113185559.cf467ea.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-05 12:01:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1856575 0 None None None 2019-12-16 15:40:41 UTC
OpenStack gerrit 699226 0 None MERGED Create a dedicated log file for healthchecks for collectd 2020-03-02 14:49:53 UTC
OpenStack gerrit 701524 0 None ABANDONED Create a dedicated log file for healthchecks for collectd 2020-03-02 14:49:53 UTC
Red Hat Product Errata RHBA-2020:0643 0 None None None 2020-03-05 12:01:43 UTC

Description Cédric Jeanneret 2019-12-16 15:40:41 UTC
Following https://bugzilla.redhat.com/show_bug.cgi?id=1784043 and https://bugzilla.redhat.com/show_bug.cgi?id=1784046, it would be nice to collect the healthcheck logs in a dedicated logfile, so that we can expose it to any container wanting to read the healthcheck status (monitoring, metrics).

A simple rule such as this one should be sufficient:
if $programname == 'container-healthcheck' then /path/to/log/file.log
& stop

Location should probably be somewhere in /var/log/containers in order to keep things clean. Be careful to ensure the file location is covered by the logrotate_crond configuration!

Comment 1 Cédric Jeanneret 2020-01-08 10:07:17 UTC
Upstream for Stein (osp-15) in the pipe.

Comment 2 Cédric Jeanneret 2020-01-15 13:16:13 UTC
In order to verify this BZ, one must deploy an undercloud with the related paunch patch and verify that, if metrics are enabled, a new log located in /var/log/containers/sensu/healthchecks.log is present

Please note, this log exists only if metrics are enabled.

Comment 7 errata-xmlrpc 2020-03-05 12:01:18 UTC
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, 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/RHBA-2020:0643


Note You need to log in before you can comment on or make changes to this bug.