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
We can see some fields in libbeat/kibana/testdata/extensive/fields.yml:
- name: replicaset
type: group
description: >
kubernetes replica set metrics
fields:
- name: name
type: keyword
description: >
Kubernetes replica set name
- name: replicas
type: group
description: >
Kubernetes replica set paused status
fields:
- name: available
type: long
description: >
The number of replicas per ReplicaSet
- name: desired
type: long
description: >
The number of replicas per ReplicaSet
- name: ready
type: long
description: >
The number of ready replicas per ReplicaSet
- name: observed
type: long
description: >
The generation observed by the ReplicaSet controller
- name: labeled
type: long
description: >
The number of fully labeled replicas per ReplicaSet
But they are not defined in the libbeat fields.yml. Open this PR to track this problem.
Notice that kubernetes.replicaset.name is addressed by PR #11133.
The text was updated successfully, but these errors were encountered:
I'm trying to understand this, and currently tracing the code around add_kubernetes_metadata processor.
It is still not clear to me what is missing.
Are we retrieving some fields using the processor that do not show at the /kibana/testdata/extensive/fields.yml you reference above?
But they are not defined in the libbeat fields.yml. Open this PR to track this problem.
We can see some fields in libbeat/kibana/testdata/extensive/fields.yml:
But they are not defined in the libbeat fields.yml. Open this PR to track this problem.
Notice that kubernetes.replicaset.name is addressed by PR #11133.
The text was updated successfully, but these errors were encountered: