Heartbeat: move configuration of common input setting to the runner factory#20610
Heartbeat: move configuration of common input setting to the runner factory#20610urso merged 7 commits intoelastic:masterfrom
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) |
andrewvc
left a comment
There was a problem hiding this comment.
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
…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.asciidocorCHANGELOG-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
@metadataobject.Related issues