-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Heartbeat: move configuration of common input setting to the runner factory #20610
Conversation
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Pinging @elastic/uptime (Team:Uptime) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from the failing lint
a360f8d
to
ae11779
Compare
…actory This changes moves the configuration of common input settings like processors, fields, tags to the runner factory (similar to filebeat). The settings index, pipeline, and dataset have been added as generic settings to all monitors.
ae11779
to
748739b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…actory (elastic#20610) (cherry picked from commit 61eaf3b)
What does this PR do?
This changes moves the configuration of common input settings like
processors, fields, tags to the runner factory (similar to filebeat).
The settings index, pipeline, and dataset have been added as generic
settings to all monitors.
Why is it important?
Add missing settings index and pipeline to heartbeat monitors.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Add custom index/pipeline setting and send event to console output. If index/pipeline are configured, they can be read from the
@metadata
object.Related issues