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

Seems the dashboards to monitor tempo are broken #3992

Closed
chenlujjj opened this issue Aug 22, 2024 · 7 comments
Closed

Seems the dashboards to monitor tempo are broken #3992

chenlujjj opened this issue Aug 22, 2024 · 7 comments
Labels
stale Used for stale issues / PRs

Comments

@chenlujjj
Copy link

Describe the bug

Hi team, I deployed tempo-distributed in k8s cluster and tried to monitor it with the dashboards here.
But I found that the dashboards are broken, for example:

  • there is no cluster label in tempo_build_info metric, which causes the dashboard variable cluster no value at all
  • there is no tempo_receiver_accepted_spans metric from the distributor, but it is used in the distributor monitor panel

Expected behavior

The dashboards should be normal and show metrics well

Environment:

  • Infrastructure: Kubernetes
  • Deployment tool: helm

Additional Context

@chenlujjj
Copy link
Author

Found a PR: #3917 may be related to the tempo_receiver_accepted_spans metric, I'll try to upgrade my tempo deploy

@javiermolinar
Copy link
Contributor

Hi, the tempo_receiver_accepted_spans will be available in the 2.6.0 release and then it will need to be updated in the helm chart. For the tempo_build_info metric, we use the same dashboards so it makes sense for us, maybe @zalegrala knows more.

@chenlujjj
Copy link
Author

Thanks @javiermolinar

Does the tempo_build_info metric in your stack have cluster label?
Below is what I get from one of the temp distributor instances:
image

@javiermolinar
Copy link
Contributor

Here is where is populated:

func init() {

The cluster label is probably added in the K8s relabel configuration. That way all our metrics include the cluster info

@chenlujjj
Copy link
Author

Got it!

@zalegrala
Copy link
Contributor

That's right. Add a cluster and namespace label in the scrape configs. This should mean the queries in the dashboard work as intended.

Copy link
Contributor

This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.

@github-actions github-actions bot added the stale Used for stale issues / PRs label Oct 22, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Used for stale issues / PRs
Projects
None yet
Development

No branches or pull requests

3 participants