Synthetic Monitoring Plugin Initialization Error

Grafana Cloud
,
1

Hey Grafana team!

I got a problem when initializing the Synthetic monitoring plugin in a local instance (it’s on kubenetes). I found this post https://community.grafana.com/t/synthetic-monitoring-on-local-grafana-instance/59947/12 really helpful, so basically I followed all the steps there

The plugin version I’m using is 0.10.2, and grafana is 7.5.1. The two data sources (prometheus and Loki) were set up manually in Grafana console, and they’re in green when testing. And here’s my provision file for the sm plugin:

apiVersion: 1

    apps:
      - type: grafana-synthetic-monitoring-app
        name: grafana-synthetic-monitoring-app
        disabled: false
        jsonData:
          apiHost: https://synthetic-monitoring-api.grafana.net
          stackId: 412137
          logs:
            grafanaName: grafanacloud-apigatewaydev-logs
            hostedId: 261476
          metrics:
            grafanaName: grafanacloud-apigatewaydev-prom
            hostedId: 525012
        secureJsonData:
          publisherToken: eyJrIj.........

Here’s the page looks like now:

E3E02E66-22AB-4D6C-9504-6017F3FBDB9B
E3E02E66-22AB-4D6C-9504-6017F3FBDB9B2444×1674 287 KB

But after I clicked the “monitor your system” button, there’s no change to the page, and there’s a 404 record in the browser console:

Request URL: https://api-gateway-graf.eng.....com/a/grafana-synthetic-monitoring-app/?page=setup
Request Method: GET
Status Code: 404

Could you help me with it? Many thanks!

2

Hi @boyiyu ! I’m not sure if you are still working on this, but if so can you confirm that the API keys you are using are Grafana Cloud API keys? The Grafana HTTP API is a separate system and the Synthetic Monitoring requires Grafana Cloud API keys for authentication.

3

Thank you for replying! It turned out I should use a newer version of Grafana and plugin. But we’re not considering use Grafana synthetic monitoring since security guys don’t like it

1 Like
4

Gotcha, no worries! Glad to know what the issue was. Perhaps something like GitHub - prometheus/blackbox_exporter: Blackbox prober exporter might be a good alternative?