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 Elasticsearch logs are put into a different index than filebeat-* they don't show up in "Stack Monitoring" view in Kibana.
A configuration option like "xpack.monitoring.sources.default.logAlias" could be added so Kibana would know where to look for the logs.
Similar options already exists for the Logs view in Kibana, with options like:
xpack.infra.sources.default.logAlias:
xpack.infra.sources.default.metricAlias:
The text was updated successfully, but these errors were encountered:
Currently, when Elasticsearch logs are put into a different index than filebeat-* they don't show up in "Stack Monitoring" view in Kibana.
A configuration option like "xpack.monitoring.sources.default.logAlias" could be added so Kibana would know where to look for the logs.
Similar options already exists for the Logs view in Kibana, with options like:
xpack.infra.sources.default.logAlias:
xpack.infra.sources.default.metricAlias:
The text was updated successfully, but these errors were encountered: