Skip to content

[8.x](backport #41077) [Heartbeat] Add managed status reporter at monitor factory level#41127

Closed
mergify[bot] wants to merge 1 commit into8.xfrom
mergify/bp/8.x/pr-41077
Closed

[8.x](backport #41077) [Heartbeat] Add managed status reporter at monitor factory level#41127
mergify[bot] wants to merge 1 commit into8.xfrom
mergify/bp/8.x/pr-41077

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Oct 4, 2024

Proposed commit message

Add status reporting for monitors when running under elastic-agent, this will allow the Fleet UI to reflect theres an issue with one or more heartbeat integrations.
image

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.

How to test this PR locally

  1. Build agentbeat locally with:
 DEV=true SNAPSHOT=true  PLATFORMS=linux/amd64 mage package
  1. Build elastic-agent locally with:
DEV=true SNAPSHOT=true PLATFORMS=linux/amd64 PACKAGES=docker mage package
  1. Enroll a non-complete elastic-agent into a private location policy with a browser monitor assigned.
  2. Check agent status is eventually reported as degraded and the integration marked as failed.
    This is an automatic backport of pull request [Heartbeat] Add managed status reporter at monitor factory level #41077 done by Mergify.

)

* [Heartbeat] Add status reporting for monitors when running under elastic-agent

(cherry picked from commit c70d2d8)
@mergify mergify bot requested a review from a team as a code owner October 4, 2024 16:10
@mergify mergify bot added the backport label Oct 4, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 4, 2024
@botelastic
Copy link

botelastic bot commented Oct 4, 2024

This pull request doesn't have a Team:<team> label.

@emilioalvap
Copy link
Contributor

Closing due to parent PR introducing linting issues, will follow with a manual backport after ##41128 is merged.

@emilioalvap emilioalvap closed this Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport needs_team Indicates that the issue/PR needs a Team:* label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant