Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enable Pod UID metadata by default #9360

Closed
exekias opened this issue Dec 3, 2018 · 0 comments · Fixed by #9517
Closed

Enable Pod UID metadata by default #9360

exekias opened this issue Dec 3, 2018 · 0 comments · Fixed by #9517
Assignees
@exekias
Labels
containers Related to containers use case enhancement libbeat Team:Integrations Label for the Integrations team v6.6.0

Comments

@exekias
Copy link
Contributor

exekias commented Dec 3, 2018

We always want to have the Pod UID available as part of the Kubernetes metadata. See elastic/kibana#26359 for more details.

To do so, we are always enabling Pod UID reporting by default, with no option to disable it.

Users should be able to opt out by using the drop_fields processor if needed.
@exekias exekias added enhancement libbeat containers Related to containers use case v6.6.0 Team:Integrations Label for the Integrations team labels Dec 3, 2018
@exekias exekias mentioned this issue Dec 3, 2018
Closed
7 tasks
@exekias exekias self-assigned this Dec 3, 2018
@exekias exekias mentioned this issue Dec 12, 2018
Merged
ruflin pushed a commit that referenced this issue Dec 14, 2018
@exekias @ruflin
Always include Pod UID as part of Pod metadata (#9517)
571b882 
We realized Pod UID is a really useful info to have around so we are
always including it.

Users wanted to opt-out from this can use the `drop_fields` processor
like this:

```
processors:
  - drop_fields:
      fields: ["kubernetes.pod.uid"]
```

closes #9360
ruflin pushed a commit to ruflin/beats that referenced this issue Dec 14, 2018
@exekias @ruflin
Always include Pod UID as part of Pod metadata (elastic#9517)
7ddfd45 
We realized Pod UID is a really useful info to have around so we are
always including it.

Users wanted to opt-out from this can use the `drop_fields` processor
like this:

```
processors:
  - drop_fields:
      fields: ["kubernetes.pod.uid"]
```

closes elastic#9360

(cherry picked from commit 571b882)
This was referenced Dec 14, 2018
Merged
Closed
ruflin pushed a commit to ruflin/beats that referenced this issue Dec 14, 2018
@exekias @ruflin
Always include Pod UID as part of Pod metadata (elastic#9517)
55ad577 
We realized Pod UID is a really useful info to have around so we are
always including it.

Users wanted to opt-out from this can use the `drop_fields` processor
like this:

```
processors:
  - drop_fields:
      fields: ["kubernetes.pod.uid"]
```

closes elastic#9360

(cherry picked from commit 571b882)
ruflin added a commit that referenced this issue Dec 17, 2018
@ruflin
Always include Pod UID as part of Pod metadata (#9517) (#9552)
5d6bd16 
We realized Pod UID is a really useful info to have around so we are
always including it.

Users wanted to opt-out from this can use the `drop_fields` processor
like this:

```
processors:
  - drop_fields:
      fields: ["kubernetes.pod.uid"]
```

closes #9360

(cherry picked from commit 571b882)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@exekias exekias

Labels
containers Related to containers use case enhancement libbeat Team:Integrations Label for the Integrations team v6.6.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Always include Pod UID as part of Pod metadata exekias/beats
1 participant
@exekias