You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The V1 monitoring flag is enabled by default (see here), even during fleet server bootstrap.
In particular, in ESS during fleet server bootstrap none of the agent monitoring settings are configured so it uses the default setting of enabled with a default output of "localhost:9200" (see the fleet server bootstrap config). This leads to confusing messages in the logs about the agent trying to connect to localhost:9200.
We should not enable monitoring during fleet server bootstrap.
See related discussion in #1731 (comment) where determining the root cause of the connection attempts to localhost:9200 took significant time.
The text was updated successfully, but these errors were encountered:
i agree with bootstrap but are you sure we should disable monitoring by default?
it would mean that any user running standalone would need to enable it in a config to get the best experience and see agent logs and metrics in the dashboards.
The V1 monitoring flag is enabled by default (see here), even during fleet server bootstrap.
In particular, in ESS during fleet server bootstrap none of the agent monitoring settings are configured so it uses the default setting of enabled with a default output of "localhost:9200" (see the fleet server bootstrap config). This leads to confusing messages in the logs about the agent trying to connect to
localhost:9200
.We should not enable monitoring during fleet server bootstrap.
See related discussion in #1731 (comment) where determining the root cause of the connection attempts to
localhost:9200
took significant time.The text was updated successfully, but these errors were encountered: