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
Describe the feature:
Let users define other outputs than the one global output and reference them for subprocesses. At the moment only one global output can be configured. This forbids to e.g. send monitoring data to a dedicated monitoring cluster.
Describe a specific use case for the feature:
Elastic Agent runs a monitoring metricbeat and filebeat that are observing the agent itself and its subprocesses. These monitoring beats should ship data to a dedicated monitoring cluster, while the other processes, for example apm-server should ship to a production cluster.
The text was updated successfully, but these errors were encountered:
We have similar requirement to have a different Elasticsearch URL for some policies (in our case to use Private link when available). It would be nice if we can override Elasticsearch URL at policy level.
Describe the feature:
Let users define other outputs than the one global output and reference them for subprocesses. At the moment only one global output can be configured. This forbids to e.g. send monitoring data to a dedicated monitoring cluster.
Describe a specific use case for the feature:
Elastic Agent runs a monitoring metricbeat and filebeat that are observing the agent itself and its subprocesses. These monitoring beats should ship data to a dedicated monitoring cluster, while the other processes, for example apm-server should ship to a production cluster.
The text was updated successfully, but these errors were encountered: