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
Currently, when Elastic products send their monitoring data to the production Elasticsearch cluster, this cluster enriches the data with a source_node field. The intent of this field is to identify the ES node that received the monitoring data so that this information may be used during debugging.
However, the monitoring UI has come to inadvertently rely on this source_node field as well (that is, this field is not just being used for its original intent, debugging).
This problem will get worse once we move away from our products sending Monitoring to the production Elasticsearch cluster and towards Metricbeat monitoring our products instead. In the latter/future model, there will be notion of an Elasticsearch production cluster node receiving monitoring data so there will be no source_node either.
Therefore, we should audit the Monitoring UI codebase and remove/replace references to source_node as much as safely possible (while keeping backwards compatibility in mind).
The text was updated successfully, but these errors were encountered:
Currently, when Elastic products send their monitoring data to the production Elasticsearch cluster, this cluster enriches the data with a
source_node
field. The intent of this field is to identify the ES node that received the monitoring data so that this information may be used during debugging.However, the monitoring UI has come to inadvertently rely on this
source_node
field as well (that is, this field is not just being used for its original intent, debugging).This problem will get worse once we move away from our products sending Monitoring to the production Elasticsearch cluster and towards Metricbeat monitoring our products instead. In the latter/future model, there will be notion of an Elasticsearch production cluster node receiving monitoring data so there will be no
source_node
either.Therefore, we should audit the Monitoring UI codebase and remove/replace references to
source_node
as much as safely possible (while keeping backwards compatibility in mind).The text was updated successfully, but these errors were encountered: