grafana/synthetic-monitoring-app

multihttp dont show up private probes graphs

shypkov opened this issue · 7 comments

shypkov commented

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Grafana version (if running on prem):
  • SM plugin version:
  • OS Grafana is installed on:
  • User OS & Browser:
  • Others:
rdubrock commented

Hiya @shypkov , because MultiHTTP is still in public preview, it's still behind a feature flag in the agent. When you run your private probe, you need to pass a flag on startup that will turn multihttp on: --features=k6.

shypkov commented

Hiya @shypkov , because MultiHTTP is still in public preview, it's still behind a feature flag in the agent. When you run your private probe, you need to pass a flag on startup that will turn multihttp on: --features=k6.

image
dont see good progress after i placed the proper line in agent config. what am i doing wrong?

rdubrock commented

What does it say when you expand the failure? Do you have any logs to share?

rdubrock commented

I'd also try adding the adhoc feature flag. The latest version of the agent I believe has remove the requirement for this flag. It's what allows it to run checks adhoc. So it would be FEATURES="k6,adhoc"

shypkov commented

I'd also try adding the adhoc feature flag. The latest version of the agent I believe has remove the requirement for this flag. It's what allows it to run checks adhoc. So it would be FEATURES="k6,adhoc"

image

peterschretlen commented

For questions and troubleshooting like this, I would recommend posting in the community forum under the synthetic-monitoring tag, rather than using a github issue: https://community.grafana.com/tag/synthetic-monitoring

When you post there, please share private probe logs as @rdubrock mentioned. That will help with troubleshooting.

This is more likely a configuration issue than a bug. If we can establish in a forum thread that there is a bug - along with reproduction steps - then we can open a github issue with the bug label. In the meantime I will close this issue.