You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it looks like by default, Parca scrapes from it's own pprof endpoints. Does this mean if I want continuous profiling of another application, that I would have to point towards the pprof endpoints on the separate application in the parca.yaml?
(Sorry if this is an obvious answer, as it was a bit non-obvious in the documentation.)
The text was updated successfully, but these errors were encountered:
There are two ways to do this: the first one is using a pull-based approach, as you already described; and the second one is to use the parca-agent to push profiles from an installed machine. So if you want to use a pull-based approach you need to add a scrape config for your application.
@yquansah do you have a suggestion of what we could do to make this clearer in our documentation? Maybe we should call this out more explicitly elsewhere?
There isn't any documentation of the config file and only one example. I assume that I could add a scrape configuration based on label. I don't know how though.
So it looks like by default, Parca scrapes from it's own pprof endpoints. Does this mean if I want continuous profiling of another application, that I would have to point towards the pprof endpoints on the separate application in the parca.yaml?
(Sorry if this is an obvious answer, as it was a bit non-obvious in the documentation.)
The text was updated successfully, but these errors were encountered: