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

Kubernetes Cluster Name not getting logged #204

Closed
dewanymca opened this issue Apr 24, 2020 · 6 comments
Closed

Kubernetes Cluster Name not getting logged #204

dewanymca opened this issue Apr 24, 2020 · 6 comments
Assignees
Labels
status:resolved Bug is fixed but not released yet.

Comments

@dewanymca
Copy link

We are running active-active configuration for Kubernetes cluster for different environment. We are unable to see clustername getting logged as part of telemetry. This will help us in identitfying which cluster has processed the request and how load balancing is happening. Is there anything we are missing here? How to enable ClusterName.

@xiaomi7732 xiaomi7732 self-assigned this Apr 27, 2020
@xiaomi7732
Copy link
Member

@dewanymca Could you please clarify what is the cluster name you are looking for to record? Could you please describe how are you getting it? For example, what kind of kubectl cmd or what UI. A screenshot of where you get it manually will be really helpful for us to understand what is the data point you are trying to record. Thanks.

@xiaomi7732 xiaomi7732 added the status:active Actively work on label Apr 27, 2020
@dewanymca
Copy link
Author

When we run command kubectl config get-contexts we recieve clustername as output in one of the column, we are looking to get smae in Applicaiton insight

@xiaomi7732
Copy link
Member

@dewanymca For now, apparently, there's no way to get the cluster name from within the cluster.
References:

There's a draft for standardize the cluster name:

Is it possible:

  • for you to have 2 different instrumentation keys, one per cluster to separate the data?
  • for you to aggregate data from other IDs that is recorded, like a node id or so?

@raelga
Copy link

raelga commented May 29, 2020

+1

Some time when you need to manage cloud resources from within the cluster, you need the cluster id to look for the kubernetes.io/cluster-name/cluster-id tag.

@xiaomi7732
Copy link
Member

@raelga Thanks for the info. Is this tag on the pods? If so, it is already recorded in the labels property.

@dewanymca Last time, we synced offline, talking about adding labels on to the node for the cluster name, did it work for you?

@dewanymca
Copy link
Author

dewanymca commented May 29, 2020 via email

@xiaomi7732 xiaomi7732 added status:resolved Bug is fixed but not released yet. and removed status:active Actively work on labels May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:resolved Bug is fixed but not released yet.
Projects
None yet
Development

No branches or pull requests

3 participants