elastic / beats

:tropical_fish: Beats - Lightweight shippers for Elasticsearch & Logstash
https://www.elastic.co/products/beats
Other
111 stars 4.93k forks source link

SYSTEM module reenabled after upgrade on RPM-based OS #34680

Closed Maksimkovalenk closed 3 months ago

Maksimkovalenk commented 1 year ago

It is possible to use --excludepath= to skip the system.yml file from being re-written. ?

When using an RPM-based operating system, if the installation/upgrade of Beat (in this case we observed the behavior on Metricbeat) is done via RPM and if the system module was previously disabled, the RPM installs the default config files over the current install, which includes the system.yml config that's enabled by default.

In case there is a large amount of Beat, it becomes a bit tedious to disable this system module everywhere.

As workaround, It is possible to use --excludepath= to skip the system.yml file from being re-written.

Is it possible to have a permanent fix for this behavior?

elasticmachine commented 1 year ago

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

botelastic[bot] commented 9 months ago

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!