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

Fix grafana datasources #2888

Merged
merged 3 commits into from
Aug 4, 2018

Conversation

vasrem
Copy link
Contributor

@vasrem vasrem commented Aug 2, 2018

What this PR does / why we need it:

We need to assign the correct datasources in the grafana dashboard.

Special notes for your reviewer:

I have submitted two different commits. The first commit (2a3f03c) solves the problem of using default datasource which doesn't make sense in my opinion since in other parts of the file we use prometheus (like here). This leads to wrong data inputs and in addition to wrong visualization of the nginx metrics.

The second commit d1a38c2 fixes a bug which shows on the right corner of grafana the following message.

Annotation Query Failed
Datasource named Prometheus was not found

FYI: I'm using the following setup:
Grafana v5.2.1
Prometheus v2.3.1

@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Aug 2, 2018
@vasrem vasrem changed the title Fix grafana datasource Fix grafana datasources Aug 2, 2018
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 2, 2018
@vasrem vasrem force-pushed the fix_grafana_datasource branch 2 times, most recently from e2ebd92 to 41a7b94 Compare August 2, 2018 15:45
@vasrem vasrem force-pushed the fix_grafana_datasource branch from 41a7b94 to d1a38c2 Compare August 2, 2018 16:07
@vasrem
Copy link
Contributor Author

vasrem commented Aug 2, 2018

/check-cla

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Aug 2, 2018
@vasrem
Copy link
Contributor Author

vasrem commented Aug 2, 2018

/assign @caseydavenport

@aledbf
Copy link
Member

aledbf commented Aug 2, 2018

@vasrem please don't assign PRs manually

@aledbf
Copy link
Member

aledbf commented Aug 2, 2018

@vasrem please add a comment about the Grafana version (something like v5.2.0 or higher is required) in https://github.com/kubernetes/ingress-nginx/blob/master/deploy/grafana/dashboards/README.md

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 3, 2018
@vasrem vasrem force-pushed the fix_grafana_datasource branch 3 times, most recently from d345288 to 0b62a83 Compare August 3, 2018 08:00
@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. and removed cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 3, 2018
@vasrem vasrem force-pushed the fix_grafana_datasource branch from 0b62a83 to 2c883d0 Compare August 3, 2018 08:02
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Aug 3, 2018
@vasrem vasrem force-pushed the fix_grafana_datasource branch from 2c883d0 to c3d9aa8 Compare August 3, 2018 08:11
@vasrem
Copy link
Contributor Author

vasrem commented Aug 3, 2018

I think its ok now.

@codecov-io
Copy link

codecov-io commented Aug 3, 2018

Codecov Report

Merging #2888 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2888      +/-   ##
==========================================
- Coverage   47.56%   47.54%   -0.02%     
==========================================
  Files          76       76              
  Lines        5483     5483              
==========================================
- Hits         2608     2607       -1     
- Misses       2540     2542       +2     
+ Partials      335      334       -1
Impacted Files Coverage Δ
internal/watch/file_watcher.go 80.76% <0%> (-3.85%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 23ce9b5...c3d9aa8. Read the comment docs.

@aledbf
Copy link
Member

aledbf commented Aug 4, 2018

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 4, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, vasrem

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 4, 2018
@aledbf
Copy link
Member

aledbf commented Aug 4, 2018

@vasrem thanks!

@k8s-ci-robot k8s-ci-robot merged commit c475f9d into kubernetes:master Aug 4, 2018
@kerneljack
Copy link

kerneljack commented Aug 15, 2018

@aledbf @vasrem Thanks for noting that version 5.2.0 of Grafana is required. Can you please let me know which feature from that version is required for this dashboard? I'm currently on 5.1.3 and am thinking of upgrading.

@vasrem
Copy link
Contributor Author

vasrem commented Aug 26, 2018

@kerneljack Could you test if this feature works with 5.1.3? I did some tests for several previous versions and I saw that it works for >=5.2.0. I'm not sure which feature is required since I didn't delve into the code.

@kerneljack
Copy link

@vasrem unfortunately I've already upgraded to 5.2.x now, so I can no longer test it for you, apologies :-(

@kerneljack
Copy link

@vasrem btw, when you say test if this feature works with 5.1.3, what specific feature are you referring to?

@vasrem
Copy link
Contributor Author

vasrem commented Aug 29, 2018

@kerneljack I couldn't reply earlier. My mistake. Regarding the feature, I meant the dashboard yaml that I modified in that PR.

@kerneljack
Copy link

@vasrem no worries, it's ok, it works for us now anyway in 5.2.x so it's good, thanks for fixing it :-)

@kerneljack
Copy link

@vasrem btw, do you have a list of upcoming features or panels that you are planning on adding to that dashboard? For example, we prefer to see the error rates on a line graph "per-upstream" instead of the table that you have. We just happen to find that a lot more intuitive so I was wondering if you're going to add anything like that at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants