alexandzors / blog-files

0 stars 1 forks source link

[FILE ISSUE] - Varken dashboard panels using incorrect flux queries #2

Open alexandzors opened 1 year ago

alexandzors commented 1 year ago

Info

Please fill out this entire form before submitting a file/script issue! Otherwise they will be ignored/closed.

Report

File Name and Location e.g. config.yml in /path/to/file

grafana-dashboard.json in posts/MonitoringMediaVarken/

Show Stopper? Can this issue be easily bypassed or does it stop you?

Expected Behavior e.g. What is supposed to happen?

Panels are supposed to be displaying data correctly for 4k media / recent added totals.

Actual Behavior e.g. What is actually happening right now?

4K libraries and Recently added/total amount seems to be switched??

Notified via email by @btstromberg -- adding this to keep track so I do not forget to look into the dashboard updates. :) https://github.com/Boerderij/Varken/pull/249

btstromberg commented 1 year ago

Hi,

I noticed that the json I sent you before is empty/corrupt. I have attached the correct file. This is my custom dashboard but you can use the queries from it. I'd like to add my dashboard to the develop branch, but I am a complete noob when it comes to Github, I have never created a pull request before... Maybe you can point me in the right direction?

Den tors 27 juli 2023 kl 06:17 skrev Alexander Henderson < @.***>:

Info

Please fill out this entire form before submitting a file/script issue! Otherwise they will be ignored/closed. Report

File Name and Location e.g. config.yml in /path/to/file

grafana-dashboard.json https://github.com/alexandzors/blog-files/tree/main/posts/MonitoringMediaVarken in posts/MonitoringMediaVarken/

Show Stopper? Can this issue be easily bypassed or does it stop you?

  • Yes
  • No

Expected Behavior e.g. What is supposed to happen?

Panels are supposed to be displaying data correctly for 4k media / recent added totals.

Actual Behavior e.g. What is actually happening right now?

4K libraries and Recently added/total amount seems to be switched??

Notified via email by @btstromberg https://github.com/btstromberg -- adding this to keep track so I do not forget to look into the dashboard updates. :) Boerderij/Varken#249 https://github.com/Boerderij/Varken/pull/249

— Reply to this email directly, view it on GitHub https://github.com/alexandzors/blog-files/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOPRGLVTFFPPHQ2O6UVHPT3XSHTT7ANCNFSM6AAAAAA2ZPQ27M . You are receiving this because you were mentioned.Message ID: @.***>

alexandzors commented 1 year ago

Your attachment did not come through. If you want you can respond to the original email chain between us with the updated json.

As for adding your dashboard. Did you mean here or Varken's repository? Normally you fork the repository, clone it locally, create a new branch based on the one you want to update, commit your changes and push to your fork. Then open an upstream PR on the repository you forked with the base branch being the branch you want to submit a PR to and compare being your forked branch.

btstromberg commented 1 year ago

I think i figured it out, I managed to create a fork and a pull request

tors 27 juli 2023 kl. 16:02 skrev Alexander Henderson < @.***>:

Your attachment did not come through. If you want you can respond to the original email chain between us with the updated json.

As for adding your dashboard. Did you mean here or Varken's repository? Normally you fork the repository, clone it locally, create a new branch based on the one you want to update, commit your changes and push to your fork. Then open an upstream PR on the repository you forked with the base branch being the branch you want to submit a PR to and compare being your forked branch.

— Reply to this email directly, view it on GitHub https://github.com/alexandzors/blog-files/issues/2#issuecomment-1653688867, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOPRGLU37VCHQ7Y7CRMNNM3XSJYFNANCNFSM6AAAAAA2ZPQ27M . You are receiving this because you were mentioned.Message ID: @.***>