# Metricbeat configuration file from package repository is always detected as changed and stops auto upgrade process
**URL:** https://discuss.elastic.co/t/metricbeat-configuration-file-from-package-repository-is-always-detected-as-changed-and-stops-auto-upgrade-process/265077
**Category:** Beats
**Tags:** metricbeat
**Created:** [February 22, 2021, 2:17pm UTC](https://discuss.elastic.co/t/metricbeat-configuration-file-from-package-repository-is-always-detected-as-changed-and-stops-auto-upgrade-process/265077 "2021-02-22T14:17:23Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jorge\_Correa](https://discuss.elastic.co/u/Jorge_Correa)
#### Post date: [February 22, 2021, 2:17pm UTC](https://discuss.elastic.co/t/metricbeat-configuration-file-from-package-repository-is-always-detected-as-changed-and-stops-auto-upgrade-process/265077/1 "2021-02-22T14:17:23Z")
I'm using metricbeat installed from APT repository in Ubuntu. I've all hosts configured to auto upgrade packages (for example, with rules in unattended-upgrades). However, on every upgrade of metricbeat, even though minor releases, APT stops asking to confirm if I want to use de new metricbeat.yml configuration file or the old one. As my metricbeat.yml is different to configure elasticsearch hosts, this process never ends like expected.
How can I suggest (where can I do that?) the package mantainer to change packages to use the well known 'conf.d' directories? So, my configurations can be done in a file that has no relation with the main files of package.
Thank you!
🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 22, 2021, 4:18pm UTC](https://discuss.elastic.co/t/metricbeat-configuration-file-from-package-repository-is-always-detected-as-changed-and-stops-auto-upgrade-process/265077/2 "2021-03-22T16:18:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.