Just discovered the new "infrastructure" menu item. Unfortunately, despite having many, many GB of data there doesn't seem to be anything to display here. I have plenty of dashboard data and am gathering from a slew of different *beat providers.
I've tried a variety of options in the "search for infrastructure data" field.
Infrastructure UI relies on Metricbeat data, many of the metrics we show are available starting with
Metricbeat 6.5 so I would recommend using it. For instance, we use information from add_host_metadata to group information by host.
so it's important to use Metricbeat 6.5? I was collecting data with Docker module on Metricbeat 6.4; Have I to update it? here-infrastructure-UI I saw a list of points to be enabled to collect data from Docker; is it really a list or can I just enable one of them?
you can change the index pattern used to read the metrics by changing the xpack.infra.sources.default.metricAlias setting in the kibana config file. Contrary to the name, it does not have to be an alias, any index pattern supported by Elasticsearch should work.
I'm seeing the same issue - infrastructure UI isn't populated ("There is no data to display.") even though I have metricbeat-* data sent from 6.5.x using the system module.
Something i noticed is that the POST requests to "graphql" return an error:
..."errors":[{"message":"[illegal_argument_exception] Fielddata is disabled on text fields by default. Set fielddata=true on [beat.hostname] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead."...
Oh! I changed on of my nodes to not use logstash and installed the index template (using metricbeat setup) and that index is immediately picked up by the infrastructure UI.
So, now I just have to figure out how I can get logstash to use the same mapping as the index template - any tips on how to do it?
The index template by default matches metricbeat-${VERSION}-*. I assume your logstash configuration writes to different index names? You could pick metricbeat's template from the _template/metricbeat-* API response and write it back to Elasticsearch under a different name with an index pattern that matches your logstash configuration. See the Elasticsearch docs on index templates for more usage examples of the _template API.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.