* Reduce the verbosity of the debug log for monitoring

Running Elastic Agent using debug mode would result in leaking
credentials for the monitoring of the local logs and metrics. This
PR remove the configuration to be exposed via the debug logging statements.

We can receive the same information by running the `inspect` subcommand
this require access to the local machine and the necessary privileges to
read the files.

* Changelog

* Add PR number, run make check

Co-authored-by: michel-laterman <michel.laterman@elastic.co>
(cherry picked from commit c3925fc)

* Reduce the verbosity of the debug log for monitoring

Running Elastic Agent using debug mode would result in leaking
credentials for the monitoring of the local logs and metrics. This
PR remove the configuration to be exposed via the debug logging statements.

We can receive the same information by running the `inspect` subcommand
this require access to the local machine and the necessary privileges to
read the files.

* Changelog

* Add PR number, run make check

Co-authored-by: michel-laterman <michel.laterman@elastic.co>
(cherry picked from commit c3925fc)

* Reduce the verbosity of the debug log for monitoring

Running Elastic Agent using debug mode would result in leaking
credentials for the monitoring of the local logs and metrics. This
PR remove the configuration to be exposed via the debug logging statements.

We can receive the same information by running the `inspect` subcommand
this require access to the local machine and the necessary privileges to
read the files.

* Changelog

* Add PR number, run make check

Co-authored-by: michel-laterman <michel.laterman@elastic.co>
(cherry picked from commit c3925fc)

Co-authored-by: Pier-Hugues Pellerin <phpellerin@gmail.com>

* Reduce the verbosity of the debug log for monitoring

Running Elastic Agent using debug mode would result in leaking
credentials for the monitoring of the local logs and metrics. This
PR remove the configuration to be exposed via the debug logging statements.

We can receive the same information by running the `inspect` subcommand
this require access to the local machine and the necessary privileges to
read the files.

* Changelog

* Add PR number, run make check

Co-authored-by: michel-laterman <michel.laterman@elastic.co>
(cherry picked from commit c3925fc)

Co-authored-by: Pier-Hugues Pellerin <phpellerin@gmail.com>

* upstream/master: (430 commits)
  CI: increase timeout (elastic#26764)
  Heartbeat: add datastream fields to synthetics (elastic#26774)
  Osquerybeat: Change the query timeout from 3 secs to 60 secs (elastic#26775)
  Remove experimental warning for inputs with variables. (elastic#26762)
  Add latest k8s versions in testing (elastic#26729)
  change type of max_bytes to ByteType (elastic#26699)
  [Elastic Agent] Fix broken enrollment command (elastic#26749)
  Update agent managed manifest to include enrolment token variable (elastic#26756)
  Filebeat: Ensure module pipelines compatibility with previous versions of Elasticsearch (elastic#26737)
  Forward port changelog for 7.13.3 (elastic#26731) to master (elastic#26754)
  Upgrade PyYAML dependency used for tests (elastic#26746)
  Add agent fleet enrolment k8s manifest (elastic#26566)
  CI: retry the step only (elastic#26736)
  Osquerybeat: Fix the configuration poll interval setting (elastic#26739)
  [Filebeat] Replace copy_from with templated value (elastic#26631)
  Reduce the verbosity of the debug log for monitoring (elastic#26583)
  Add instructions on testing metricbeat kubernetes module (elastic#26643)
  Revert "[CI] fight the flakiness with some retry option in the CI only for the Pull Requests (elastic#26617)" (elastic#26704)
  Packaging: linux/armv7 is not supported (elastic#26706)
  Cyberarkpas: Link to official docs on how to setup TLS (elastic#26614)
  ...