System package: revert back change to dynamic_dataset/namespace#6801
System package: revert back change to dynamic_dataset/namespace#6801gsantoro merged 3 commits intoelastic:mainfrom
Conversation
🌐 Coverage report
|
|
@gsantoro : Are we not adding re-route processor to the system package? |
|
hello @ishleenk17, |
| example: "stretch" | ||
| description: > | ||
| OS codename, if any. | ||
|
|
There was a problem hiding this comment.
I'm a bit conflicted by this change since even if I agree that it is not relevant to this PR, it was introduced by running elastic-package format locally.
Every time I run this command locally to test the integration I have to revert those formatting changes manually. This time, I committed this change by "mistake".
While this package has only this file change, some packages are not well formatted in multiple files.
Is it just me or do other people have similar issues?
Does this mean we are going to create Input package for this Integration that would collect traffic in one place from a common input type for System Package? |
|
Package system - 1.36.0 containing this change is available at https://epr.elastic.co/search?package=system |
What does this PR do?
Revert back changes from issue elastic/kibana#157897.
Removing the following configs from the system package manifest
We would like to revert these permissions in favour of creating a separate input package to reroute traffic from Syslog.
Also, syslog datastream is enabled by default when you create a new agent policy. By having these permissions here, we were accidentally giving any elastic-agent permissions to write
logs-*-*.The idea is that we would like to have datastream-based integrations to monitor a specific application, while we should have input packages instead to reroute "mixed" traffic (from different sources) from that application.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots