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.

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

Some extra fields under kubernetes.replicaset seem to be missing #11222

Closed
alakahakai opened this issue Mar 13, 2019 · 2 comments
Closed

Some extra fields under kubernetes.replicaset seem to be missing #11222

alakahakai opened this issue Mar 13, 2019 · 2 comments
Assignees
Labels
bug libbeat Team:Integrations Label for the Integrations team v7.2.0

Comments

@alakahakai
Copy link

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.

@odacremolbap
Copy link
Contributor

hi @alakahakai

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.

you mean this file: https://github.com/elastic/beats/blob/master/libbeat/processors/add_kubernetes_metadata/_meta/fields.yml

contains (or should contain) some fields that are missing at the kibana tests yaml?

I'll continue tracing the code, but sure some clarifications will be a time saver.
Thanks!

@alakahakai
Copy link
Author

We have added the missing fields in libbeat - pull #11134. This issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug libbeat Team:Integrations Label for the Integrations team v7.2.0
Projects
None yet
Development

No branches or pull requests

5 participants