Bug 1523289
| Summary: | [RFE] Create a role that will list to the admin which hosts are not configured for metrics | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine-metrics | Reporter: | Lukas Svaty <lsvaty> |
| Component: | RFEs | Assignee: | Shirly Radco <sradco> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Guilherme Santos <gdeolive> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0.7.1 | CC: | bugs, dfediuck, emarcus, lleistne, rdlugyhe, sgoodman, sradco |
| Target Milestone: | ovirt-4.4.1 | Keywords: | FutureFeature |
| Target Release: | --- | Flags: | dfediuck:
ovirt-4.4?
rule-engine: planning_ack? sbonazzo: devel_ack+ rule-engine: testing_ack? |
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | rhv-4.4.0-29 | Doc Type: | Enhancement |
| Doc Text: |
With this update, you can check the list of hosts that are not configured for metrics, that is, those hosts on which the Collectd and Rsyslog/Fluentd services are not running.
First, run the playbook 'manage-ovirt-metrics-services.yml' by entering:
----
# /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh --playbook=manage-ovirt-metrics-services.yml
----
Then, check the file `/etc/ovirt-engine-metrics/hosts_not_configured_for_metrics`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-08-05 06:25:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Metrics | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1514927 | ||
| Bug Blocks: | |||
|
Description
Lukas Svaty
2017-12-07 16:28:30 UTC
New hosts should be configured during host deploy. To check regularly fluentd/collectd is running on all hosts and engine user can set cron job that will run the manage_services role and start the services if needed. Yaniv, is documentation on how to do that is enough? (In reply to Shirly Radco from comment #1) > New hosts should be configured during host deploy. > > To check regularly fluentd/collectd is running on all hosts and engine user > can set cron job that will run the manage_services role and start the > services if needed. > > > Yaniv, is documentation on how to do that is enough? Should be good enough. Please add a small playbook that goes over all oVirt hosts and checks if they are already configured or not (lets check configuration and that services are up). This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. Step for testing: 1. Run the playbook 'manage-ovirt-metrics-services.yml' by running: /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh --playbook=manage-ovirt-metrics-services.yml 2. Check file /etc/ovirt-engine-metrics/hosts_not_configured_for_metrics Verified on: ovirt-engine-4.4.1-0.1.el8ev.noarch ovirt-engine-metrics-1.4.1.1-1.el8ev.noarch Steps: 1. have metrics running and configured 2. logged in one of the hosts and deleted all collectd/ryslog data (as well stopping collectd service) # rm -rf /etc/collectd.d/* && rm -rf /etc/rsyslog.d/* && systemctl stop collectd 1. # /usr/share/ovirt-engine-metrics/configure_ovirt_machines_for_metrics.sh --playbook=manage-ovirt-metrics-services.yml 3. once above step concluded: # cat /etc/ovirt-engine-metrics/hosts_not_configured_for_metrics Results: File present, containing info about host the doesn't have metrics properly configured This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |