using grafana api key

[t3h2mas]

I set up grafana w/ google login, so I'm trying to use an API key to connect wizzy to the dashboards.

I see that 'grafana:api_key' is an entry in validConfigs from config.js L:21.

EDIT: Using something like

{
  "config": {
    "grafana": {
      "url": "[URL]",
      "api_key": "[KEY]"
    }
  }
}

in the wizzy.json appeared to work. Maybe it should be a documented option.

[john-arvid]

Thank you for bringing attention to this. Created a api key in grafana with editor role and copied the api key

To get connected I only used: wizzy set grafana url http://grafanaip:3000 wizzy set grafana api_key averylongapikey

[Sytten]

This is indeed possible, I will add the documentation

[kepai91]

Complementary question: I have a similar setup of Grafana w/ Google OAuth, are you able to export dashboards using api_key config? I can list and import dashboards using this configuration but I am having a difficult time exporting dashboards. Maybe I'm missing something here.

>> wizzy export dashboards                                                                                                     
Output:
{"message":"Unauthorized"}
✘ Dashboard thanos-alerts export failed.
✘ 1 dashboards export failed.
>> node -v                                                                                                                
v12.9.0
>> npm -v                                                                                                                 
6.10.3
>> wizzy version                                                                                          
0.6.0
>> wizzy conf                                                                                         
Output:
{
  "grafana": {
    "envs": {
      "tst": {
        "url": "https://grafana.tst.net",
        "api_key": "blah"
      },
      "prod": {
        "api_key": "blah",
        "url": "https://grafana.prod.net"
      }
    }
  },
  "context": {
    "grafana": "tst"
  }
}

[Sytten]

Ha yes, the commands ending in s are currently broken (I will try to push a fix the repo this week). Basically the authentication is not passed correctly. You should be able to do it one by one. I am still waiting on npm permissions to push a new version though.

[kepai91]

Ah! Gotcha. Doing it one at a time worked. Thanks.

[dideler]

@Sytten could you point me to the documentation for token based auth? I can't find it.

I'm wondering what scopes the token needs to do various imports. In this case, the scope options are the roles viewer, editor, and admin.

[dideler]

Tried all the scopes and this is the result.

Token scope	Import dashboards	Import datasources	Import orgs
viewer	yes (but broken*)	no	no
editor	yes	no	no
admin	yes	yes	no

^{* Using token auth with viewer scope does not work for import dashboards. The text Importing N dashboards: will appear but it's a no-op with no additional feedback. Switching to basic auth (user/pass) does work to import dashboards with viewer scope.}

[Sytten]

@dideler Thanks for the report, we need to fix the documentation (https://github.com/grafana-wizzy/wizzy-site). If you want to do it, I would appreciate!

[jfreeland]

Ha yes, the commands ending in s are currently broken (I will try to push a fix the repo this week). Basically the authentication is not passed correctly. You should be able to do it one by one. I am still waiting on npm permissions to push a new version though.

Did this change get pushed? I'm seeing issues with response.statusCode undefined.

[Sytten]

Its pushed on master yes, not on npm

[ttownsend78]

I think I have the latest build, but getting the below error trying to list dashboards. My Grafana instance is using generic Oauth for SSO.

[root@ip-10-0-8-250 grafana]# wizzy conf
Output:
{
  "grafana": {
    "envs": {
      "staging": {
        "url": "https://dashboard-dev.url.com",
        "api_key": "long api key"
      }
    }
  },
  "context": {
    "grafana": "staging"
  }
}
[root@ip-10-0-8-250 grafana]# wizzy list dashboards
Output:
No Grafana API response
Error: unable to verify the first certificate
✘ Dashboards list display failed

[Sytten]

It seems like you have a problem with https certificates.

[jfreeland]

Its pushed on master yes, not on npm

Will there be a new mpm release soon? It looks like there hasn't been a release in quite some time?

[Sytten]

Yeah I am caught up in a lot of stuff currently, I want to make one next weekend.

[nunofernandes]

Did you had the time to look at this? I did an install from npm and have the same issue when trying to export to grafana.

[jfreeland]

Would love to see a new release soon.

[Sytten]

New release is out, let me know if you still have issues. I will publish an update to the documentation shortly.

[Tikam02]

@Sytten Problem in new release -
Grafana Version - v7.0.3 wizzy version - 0.6.0

$ wizzy list dashboards                                                                                     
Output:
Grafana API response status code = 401
No error body from Grafana API.
✘ Dashboards list display failed

[anthosz]

Hi,

Grafana Version - v7.0.5 wizzy version - 0.6.0

I confirm that it doesn't works:

$ npm install -g wizzy
$ wizzy set grafana url http://.....
$ wizzy set grafana api_key key (with admin rights)
$ wizzy import dashboards
Importing 1 dashboards:
✔ Dashboard status imported successfully.
✔ 1 dashboards imported successfully.

Only public dashboard is imported. Please note that github auth is used by default.

Best regards,