# Where is my infrastructure data?

**URL:** <https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039>\
**Category:** Metrics\
**Created:** [November 16, 2018, 11:36am UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039 "2018-11-16T11:36:58Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [November 30, 2018, 11:45am UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/21 "2018-11-30T11:45:24Z")

</div>

Hmm.. another puzzle..

```
FATAL ValidationError: child "xpack" fails because [child "infra" fails because [child "sources" fails because [child "default" fails because [child "fields" fails because ["hostname" is not allowed]]]]]

```

If my index follow 'metricbeat-' what would I set your xpack value(s) to?

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [November 30, 2018, 2:16pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/22 "2018-11-30T14:16:05Z")

</div>

oh, looks like I made a mistake in my config snippet - it should be `host` instead of `hostname`:

```auto
xpack.infra:
  sources:
    default:
      fields:
        host: 'beat.hostname.keyword'

```

sorry about that 😇

---

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [December 1, 2018, 3:36pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/23 "2018-12-01T15:36:53Z")

</div>

That's seems to be working. Thanks for your help!

---

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [December 2, 2018, 1:29pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/24 "2018-12-02T13:29:22Z")

</div>

Sorry - one more thing: what's the config to get the k8 monitoring working?

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [December 3, 2018, 12:34pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/25 "2018-12-03T12:34:17Z")

</div>

The k8s metrics rely on the `kubernetes` metricbeat module and the `add_kubernetes_metadata` processor being enabled: [https://www.elastic.co/guide/en/infrastructure/guide/current/install-infrastructure-monitoring.html#\_which\_modules\_and\_configuration\_options\_do\_i\_enable](https://www.elastic.co/guide/en/infrastructure/guide/current/install-infrastructure-monitoring.html#_which_modules_and_configuration_options_do_i_enable)

---

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [December 3, 2018, 1:03pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/26 "2018-12-03T13:03:18Z")

</div>

I updated my daemonset definition to include the "processors" entries from the link you provided. When I redeployed it these log entries started showing up:

```
"metricbeat":{"kubernetes":{"container":{"events":3,"failures":3},"node":{"events":3,"failures":3},"pod":{"events":3,"failures":3},"system":{"events":3,"failures":3},"volume":{"events":3,"failures":3}}

```

BTW: possible doc bug: in the "kubernetes" section for the same link - you still have the link for "filebeat _docker_ input". Not sure if this is intentional or not.

---

<div class="post-metadata">

**Author:** ![weltenwort](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weltenwort/32/53885_2.png) [@weltenwort](https://discuss.elastic.co/u/weltenwort)\
**Post date:** [December 3, 2018, 3:11pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/27 "2018-12-03T15:11:11Z")

</div>

@exekias any idea about these messages?

> possible doc bug: in the "kubernetes" section for the same link - you still have the link for "filebeat _docker_ input"

This is intentional since the even the logs for k8s containers are read using the docker input and correlated using the k8s metadata processor.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 31, 2018, 3:11pm UTC](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039/28 "2018-12-31T15:11:23Z")

</div>

Closed on December 31, 2018, 3:11pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

[Previous page](https://discuss.elastic.co/t/where-is-my-infrastructure-data/157039.md?page=1)