Closed hazra-mms closed 6 days ago
Do you mind sharing ...
Thanks that should help us find the problem 🙂
Thanks for your reply, please find the details.
Our pyroscope setup is working and we can get the details from the explore view also. It's just issues with the plugin that we face.
We are running Grafana version 10.4.3 which is configured using the helm chart.
In case you need any further information please let me know.
Hi @hazra-mms,
Thank you for the info, may I also ask you to share:
/Series
on your screenshot
?Thanks, we're still trying to figure out where the problem could be.
Hi @grafakus ,
Sorry for the delay, please find the information below.
https://
url for failing request contains: http://localhost/grafana/api/datasources/proxy/uid/pyroscope/querier.v1.QuerierService/Series
Not sure why localhost is used here.
Thanks @hazra-mms. Would you mind sharing part of your settings.ini file in [server]
section? The localhost
is taken from root_url
config which by default is:
root_url = %(protocol)s://%(domain)s:%(http_port)s/
By setting domain/protocol to:
[server]
http_port = 80
domain = grafana
or
[server]
http_port = 80
root_url = http://grafana/
I was able to load the plugin from https://grafana/...:
Also, do you have serve_from_sub_path
set in your settings?
We've closed this issue since it needs more information and hasn't had any activity recently. Feel free to re-open it after you you add more information.
Bug description
We have installed the plugin in our grafana infrastructure, we are having datasource for pyroscope already enabled but the plugin explore view doesn't find the datasource. Hence we can not use this.
Steps to reproduce
Install the plugin following https://grafana.com/grafana/plugins/grafana-pyroscope-app/?tab=installation ( we installed manually and through plugin section in the helm chart). Navigate to Profiles --> Explore Profiles
Actual behaviour
Error![image](https://github.com/user-attachments/assets/11c9c1e3-e91e-4c17-88f0-bd7180d4ae1d)
TypeError: Failed to fetch
Error in developer console in chrome![image](https://github.com/user-attachments/assets/9debe1c9-41f0-4c2f-8bea-a613c4780879)
Expected behaviour
I expect the UI would load the profile correctly as the pyrooscope data source is configured already.