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

[K8s] cluster metadata not added on all metrics #30425

Closed
emmanuelmathot opened this issue Feb 16, 2022 · 7 comments · Fixed by #33032
Closed

[K8s] cluster metadata not added on all metrics #30425

emmanuelmathot opened this issue Feb 16, 2022 · 7 comments · Fixed by #33032
Assignees
Labels
Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team

Comments

@emmanuelmathot
Copy link

emmanuelmathot commented Feb 16, 2022

Describe the enhancement:

The cluster metadata such as orchestrator.cluster.name and orchestrator.cluster.ip are not added on all kubernetes metrics. From usage and code review, I can see they are added to

  • container
  • node
  • pod
  • state_daemonset
  • state_deployment
  • state_job
  • state_node
  • state_pod
  • state_replicaset
  • state_service
  • state_statefulset

but missing to the following metrics where they should be added

  • proxy
  • system
  • volume
  • apiserver
  • state_daemonset
  • state_persistentvolume
  • state_persistentvolumeclaim
  • state_storageclass
  • event

Describe a specific use case for the enhancement or feature:

Being able to account the PVC usage for a given cluster.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 16, 2022
@tetianakravchenko tetianakravchenko added the Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team label Feb 16, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 16, 2022
@tetianakravchenko
Copy link
Contributor

@emmanuelmathot could you give more details on your k8s setup? are you using managed kubernetes solutions?

@emmanuelmathot
Copy link
Author

Yes, we have deployed managed kubernetes as described in https://www.elastic.co/guide/en/fleet/master/running-on-kubernetes-managed-by-fleet.html using fleet policies.
We also added a kubeadm-config config map to add the cluster metadata

apiVersion: v1
kind: ConfigMap
metadata:
  name: kubeadm-config
  namespace: kube-system
data:
  ClusterConfiguration: |
    clusterName: {{ .Values.components.kubeadm_config.clusterName }}
    controlPlaneEndpoint: {{ .Values.components.kubeadm_config.controlPlaneEndpoint }}

We are using elastic cloud with Elasticsearch 7.15.1 and beats image same version

@lrfsh
Copy link

lrfsh commented Feb 17, 2022

Hello,

I am using Elasticsearch 8.0.0 and the beats image same version and I have the same issue.

@RumRogerz
Copy link

I am seeing similar results, but with kubernetes metadata.

@tetianakravchenko
Copy link
Contributor

tetianakravchenko commented Sep 8, 2022

metricsets:

metricsets:

event - was added #31341

state_storageclass - will be fixed by #33032

@emmanuelmathot
Copy link
Author

great! Thank you!

@ottramst
Copy link

Hi!

Is it correct that for EKS based clusters the orchestrator.cluster.name field is not possible to add?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants