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
We're starting to run into more issues where people are profiling very large / complex applications. As we've added new features, it's possible for people to get into issues where a single config option can cause for the Pyroscope server to run into issues:
too many tags
Scrape interval too short
Retention threshold too high/low
"How much overhead does pyroscope cause"
if the push destination is unresponsive, will the profiling agent spin, consume resources, or crash?
etc
We should add more information to various pages to help people troubleshoot the issues that they run into more easily. Not sure if this should be one page or on each individual page, but just adding this here as a placeholder so we can address this more thoroughly as time goes on
The text was updated successfully, but these errors were encountered:
We're starting to run into more issues where people are profiling very large / complex applications. As we've added new features, it's possible for people to get into issues where a single config option can cause for the Pyroscope server to run into issues:
We should add more information to various pages to help people troubleshoot the issues that they run into more easily. Not sure if this should be one page or on each individual page, but just adding this here as a placeholder so we can address this more thoroughly as time goes on
The text was updated successfully, but these errors were encountered: