Nicolas Ruflin

++ on going for data streams and directly jump on the new naming scheme: https://www.elastic.co/blog/an-introduction-to-the-elastic-data-stream-naming-scheme (yes, I'm biased). I guess this would all fall under `metrics` as the type and...

++ on metrics. I like `hass.events` as it keeps room for other `hass.*` data. `hass-events` would be using `events` as the namespace which is unexpected. One thing I'm stumbling over...

@legrego LGTM 👍

There is the http module in metricbeat which is a contribution from @christiangalsterer . There you could use the reloading feature: https://www.elastic.co/guide/en/beats/metricbeat/6.0/metricbeat-module-http.html The module is available in 6.0.0-beta1.

There is also an entry `system.cpu.total.norm.pct` which contains the normalised percentage value and already did the calculation for you. It's an ongoing discussion which one should be shown by default....

👍 on this suggestion. An other option for the config would be to have it as following: ``` filebeat.autodiscover: providers: - type: docker templates: - default: true config: container.ids: -...

@andrewvc @axw and teams, it would be helpful if you could extend this list. @andresrc I expect this issue to grow over time but we should continously work on it...

@felixbarny I would consider the following "legal" from an ECS perspective: ``` { "labels": { "teams": ["team1","team2"] } } ``` The reason is that any field in Elasticsearch (Lucene) can...

In case there are no images around, I could also see us building it our self. As this could take a bit of time I could see the tests which...

@reyang It would be great to have these fields in ECS / single place. It was always the goal to get metrics into ECS especially some of these fundamentals. See...