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
Issue:
We're encountering an unexpected behavior where despite the documentation indicating that limits are applied per-resource, we're observing that other resources are getting wiped of their logs and traces. Specifically, one of our resources is casting a batch of events every 3 seconds, and only this resource remains visible in the dashboard while others seem to be cleared.
Expected Behavior:
According to the documentation, limits should be enforced per-resource, ensuring that all resources have equal visibility on the dashboard regardless of their activity levels.
Steps to Reproduce:
Deploy multiple resources using the specified image.
One resource should cast a batch of events every 3 seconds.
Monitor the dashboard for log and trace visibility.
Additional Information:
This behavior is hindering our ability to accurately monitor and debug our resources. We believe this discrepancy between the expected behavior and the observed behavior constitutes a bug and should be addressed.
We appreciate any assistance or insight into resolving this issue. Thank you.
The text was updated successfully, but these errors were encountered:
Affected Image:
mcr.microsoft.com/dotnet/nightly/aspire-dashboard:8.0.0-preview.7
Issue:
We're encountering an unexpected behavior where despite the documentation indicating that limits are applied per-resource, we're observing that other resources are getting wiped of their logs and traces. Specifically, one of our resources is casting a batch of events every 3 seconds, and only this resource remains visible in the dashboard while others seem to be cleared.
Expected Behavior:
According to the documentation, limits should be enforced per-resource, ensuring that all resources have equal visibility on the dashboard regardless of their activity levels.
Steps to Reproduce:
Additional Information:
This behavior is hindering our ability to accurately monitor and debug our resources. We believe this discrepancy between the expected behavior and the observed behavior constitutes a bug and should be addressed.
We appreciate any assistance or insight into resolving this issue. Thank you.
The text was updated successfully, but these errors were encountered: