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.

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

[8.14](backport #39807) [Docker] Stop returning errors when there are no metric values #39829

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jun 7, 2024

Proposed commit message

Stop returning errors when there are no metric values for the Docker memory metricset.

The docker metricset returns an error when there are no memory metric values available. This condition can happen when there are no running containers on Docker.

When no containers are running, the metricset returns an error at every collection, creating noise.

Notes for reviewers

  • Is there a use case when we should return an error instead?
  • Should I add a logger to log a debug message saying "no memory stats data available"?

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.

Related issues


This is an automatic backport of pull request #39807 done by [Mergify](https://mergify.com).

* Return nil instead or an error if no metrics

The docker metricset returns an error when there are no memory metric
values available.

This condition can happen when there are no running containers on
Docker.

When no containers are running, the metricset returns an error
at every collection, creating noise.

* Add a "docker.memory" logger to write a debug message on no-metrics

(cherry picked from commit 4c1d3f2)
@mergify mergify bot requested a review from a team as a code owner June 7, 2024 14:34
@mergify mergify bot added the backport label Jun 7, 2024
@mergify mergify bot requested review from AndersonQ and faec and removed request for a team June 7, 2024 14:34
@mergify mergify bot assigned zmoog Jun 7, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 7, 2024
@zmoog zmoog added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Jun 7, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 7, 2024
@zmoog zmoog enabled auto-merge (squash) June 7, 2024 15:22
Copy link
Contributor Author

mergify bot commented Jun 10, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

@zmoog zmoog merged commit de256b8 into 8.14 Jun 10, 2024
19 checks passed
@zmoog zmoog deleted the mergify/bp/8.14/pr-39807 branch June 10, 2024 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants