-
Notifications
You must be signed in to change notification settings - Fork 66
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
deprecation of host_name
in favour of k8s_node_name
for K8s
#226
Comments
If there were to be one single dashboard, there should be an attribute which is common across the environments. There is no such attribute since
|
@srikanthccv In case of hybrid environments with hostmetrics dashboard to monitor VMs, we would still see pod name of OtelAgent as the Is there any proper way to separate it other than adding filter in each widgets to skip one with |
Is this under the assumption that we will use a single dashboard for all environments?
I didn't understand this question. |
Not necessarily. It can have two dashboards. But in this case, K8s dashboard would be all good, but the other one would have otelAgent pod names.
related to above. question being, if not single dashboard, how to go about separating it? |
We recently deprecated
host_name
for Kubernetes in the favour ofk8s_node_name
.Now, users must have two separate dashboards to monitor K8ss nodes or non-K8s nodes.
cc @ankitnayan
The text was updated successfully, but these errors were encountered: