pingcap / pingcap/tiup

Grafana data source not found

Open
#665 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted type/bug
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

Deploy with the following yaml file:

global:
  user: "tidb"
  ssh_port: 22
  deploy_dir: "/tidb-deploy"
  data_dir: "/tidb-data"

pd_servers:
  - host: 127.0.0.1
    name: pd

tidb_servers:
  - host: 127.0.0.1

tikv_servers:
  - host: 127.0.0.1
    data_dir: "/mnt/test/tikv-data"

monitoring_servers:
  - host: 127.0.0.1

grafana_servers:
  - host: 127.0.0.1

Deploy with command: tiup cluster deploy toda-test-cluster v4.0.4 ./test-cluster.conf

Then visit http://127.0.0.1:3000/d/SVbh2xUWk/toda-test-cluster-tiflash-summary?orgId=1.

  1. What did you expect to see?

No error in grafana.

  1. What did you see instead?

I got an error: Datasource named toda-toda-test-cluster was not found. The datasource set in dashboard is toda-toda-test-cluster, but the real datasource name is toda-test-cluster

  1. What version of TiUP are you using (tiup --version)?
v1.0.8 tiup
Go Version: go1.13
Git Branch: master
GitHash: 4276089

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported tiup cluster deploy command with the supplied YAML, then open the Grafana dashboard URL and compare the configured datasource with the dashboard's requested name. Done means the dashboard loads without a datasource-not-found error and the datasource names agree.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, grafana
Domain
devops, observability-sre
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.