Red Hat Bugzilla – Bug 1524626
Fix precision and reliability of metrics collection for OpenShift
Last modified: 2018-03-01 08:22:12 EST
New commit detected on ManageIQ/manageiq-providers-kubernetes/gaprindashvili: https://github.com/ManageIQ/manageiq-providers-kubernetes/commit/5eae3559b57e37710bd4417bd0a490dd9e4098c8 commit 5eae3559b57e37710bd4417bd0a490dd9e4098c8 Author: Mooli Tayer <mtayer@redhat.com> AuthorDate: Sun Dec 10 15:20:10 2017 +0200 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Mon Dec 11 13:26:46 2017 -0500 Merge pull request #159 from yaacov/add-hawkualr-v1.5-collector Improve Hawkular metrics collection (cherry picked from commit d960961068c94d0a199f1bd9edc296ef37d25a3f) https://bugzilla.redhat.com/show_bug.cgi?id=1524626 https://bugzilla.redhat.com/show_bug.cgi?id=1524628 .../container_manager/metrics_capture.rb | 28 +- .../metrics_capture/hawkular_capture_context.rb | 299 ++++++++++++--- .../metrics_capture/hawkular_client_mixin.rb | 6 +- .../hawkular_legacy_capture_context.rb | 82 +++++ .../hawkular_capture_context_spec.rb | 42 ++- .../hawkular_legacy_capture_context_spec.rb | 95 +++++ .../container_manager/metrics_capture_spec.rb | 14 +- .../hawkular_capture_context_container_metrics.yml | 126 +------ ...hawkular_capture_context_container_timespan.yml | 128 +------ .../hawkular_capture_context_m_endpoint.yml | 88 +++++ .../hawkular_capture_context_node_metrics.yml | 310 +--------------- .../hawkular_capture_context_node_timespan.yml | 312 +--------------- .../hawkular_capture_context_pod_metrics.yml | 314 +--------------- .../hawkular_capture_context_pod_timespan.yml | 316 +--------------- .../hawkular_capture_context_refresh.yml | 147 ++++---- .../hawkular_capture_context_status.yml | 20 +- ...ar_legacy_capture_context_container_metrics.yml | 191 ++++++++++ ...r_legacy_capture_context_container_timespan.yml | 191 ++++++++++ ...awkular_legacy_capture_context_node_metrics.yml | 379 +++++++++++++++++++ ...wkular_legacy_capture_context_node_timespan.yml | 379 +++++++++++++++++++ ...hawkular_legacy_capture_context_pod_metrics.yml | 379 +++++++++++++++++++ ...awkular_legacy_capture_context_pod_timespan.yml | 379 +++++++++++++++++++ .../hawkular_legacy_capture_context_refresh.yml | 405 +++++++++++++++++++++ .../hawkular_legacy_capture_context_status.yml | 97 +++++ 24 files changed, 3162 insertions(+), 1565 deletions(-) create mode 100644 app/models/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context.rb create mode 100644 spec/models/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_spec.rb create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_capture_context_m_endpoint.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_container_metrics.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_container_timespan.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_node_metrics.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_node_timespan.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_pod_metrics.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_pod_timespan.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_refresh.yml create mode 100644 spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/hawkular_legacy_capture_context_status.yml
Please provide steps to reproduce.
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/RHSA-2018:0380