Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cherry-pick #21071 to 7.9: Handling missing counters in application_pool metricset #21132

Merged
merged 2 commits into from
Sep 17, 2020
Merged

Cherry-pick #21071 to 7.9: Handling missing counters in application_pool metricset #21132

merged 2 commits into from
Sep 17, 2020

Conversation

narph
Copy link
Contributor

@narph narph commented Sep 17, 2020 •
edited
Loading

Cherry-pick of PR #21071 to 7.9 branch. Original message:

What does this PR do?

Mhe missing performance counters in the application_pool metricset would trigger an error and stop it.

Why is it important?

There should only be an error message if this is the case but should not stop the metricset.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

@narph
Handling missing counters in application_pool metricset (elastic#21071)
4c79a4b 
* mofidy doc

* fix

* changelog

(cherry picked from commit bdfff66)
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 17, 2020
@elasticmachine
Copy link
Collaborator

elasticmachine commented Sep 17, 2020 •
edited by jenkins-beats-ci bot
Loading

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #21132 updated]

  • Start Time: 2020-09-17T12:18:02.423+0000

  • Duration: 43 min 47 sec

Test stats 🧪

Test Results
Failed 0
Passed 760
Skipped 72
Total 832

@narph narph changed the title Cherry-pick #21071 to 7.x: Handling missing counters in application_pool metricset Cherry-pick #21071 to 7.9: Handling missing counters in application_pool metricset Sep 17, 2020
@narph narph self-assigned this Sep 17, 2020
@narph narph added [zube]: In Review backport Team:Integrations Label for the Integrations team labels Sep 17, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 17, 2020
@narph narph merged commit 36eb6f7 into elastic:7.9 Sep 17, 2020
@narph narph deleted the backport_21071_7.9 branch September 17, 2020 16:29
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
@narph
Cherry-pick elastic#21071 to 7.9: Handling missing counters in applic…
6cfd4eb 
…ation_pool metricset (elastic#21132)

* Handling missing counters in application_pool metricset  (elastic#21071)

* mofidy doc

* fix

* changelog

(cherry picked from commit d2dbc78)

* fix chnagelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ChrsMark ChrsMark ChrsMark approved these changes

Assignees

@narph narph

Labels
backport Team:Integrations Label for the Integrations team [zube]: In Review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@narph @elasticmachine @ChrsMark