-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tenant-setting service is not reachable if not using ingress for routing #3507
Comments
I confirmed this by copy/pasting the gateway part from Loki and adjusting it to Pyroscope (see below). After deploying and adjusting the datasource to look at While working on it, I noticed that the path definitions in here and here do not seem to be correct. They apparently need to be prefixed with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We did add https://github.com/grafana/explore-profiles to our Grafana instance and also brought up
tenant-setting
andadhoc-profiles
by using the latest version of the pyroscope helm chart which did re-add them as mentioned in #3463 (comment).We're running pyroscope in microservice mode without the ingress resources as we're not exposing it externally, this means alloy and Grafana do connect to the services directly.
In the case of Grafana we do connect to the query-frontend on
http://grafana-pyroscope-query-frontend.pyroscope.svc.cluster.local:4040
.We're however ending up receiving a 404 on the settings page of "Explore Profiles" which also make some features unavailable.
Looking at other Grafana components, they mostly ship with a gateway which is responsible for those routing aspects. There is however no gateway component provided for Pyroscope. Is my assumption correct, that using the https://github.com/grafana/explore-profiles plugin currently does not work within the setup mentioned above?
Environment
The text was updated successfully, but these errors were encountered: