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
A configuration option added to the pyroscope.java component in Alloy that allows disabling of pyroscope entries in application logs
Use case
We're collecting profiles via the pyroscope.java component on Alloy profiles pods from the k8s-monitoring helm chart. On some java app pods that are running through this component, there are many log lines stating Profiling started flooding the application logs and not providing any value
The text was updated successfully, but these errors were encountered:
This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
Request
A configuration option added to the pyroscope.java component in Alloy that allows disabling of pyroscope entries in application logs
Use case
We're collecting profiles via the pyroscope.java component on Alloy profiles pods from the k8s-monitoring helm chart. On some java app pods that are running through this component, there are many log lines stating
Profiling started
flooding the application logs and not providing any valueThe text was updated successfully, but these errors were encountered: