8000 [Heartbeat] [Synthetics] Write summary document when termination signal is received by mcapell · Pull Request #44704 · elastic/beats · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Heartbeat] [Synthetics] Write summary document when termination signal is received #44704

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
Draft
wants to merge 22 commits into
base: main
Choose a base branch
from
Draft

[Heartbeat] [Synthetics] Write summary document when termination signal is received #44704

wants to merge 22 commits into from

Conversation

mcapell
Copy link
@mcapell mcapell commented Jun 9, 2025

Proposed commit message

Add a new monitor status skipped when the termination handler is received.

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.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@mcapell
[Heartbeat] [Synthetics] Write summary document when termination sign…
60722a2 
…al is received

Add a new monitor status `skipped` when the termination handler is
received.
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 9, 2025
@botelastic
Copy link
botelastic bot commented Jun 9, 2025

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

@github-actions GitHub Actions
Copy link
Contributor
github-actions bot commented Jun 9, 2025

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify mergify bot assigned mcapell Jun 9, 2025
@mergify Mergify
Copy link
Contributor
mergify bot commented Jun 9, 2025

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mcapell? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@mcapell mcapell

Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@mcapell
0