Skip to content
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

Limits are not per-resource despite documentation #4173

Open
AntonZhuchkovXOR opened this issue May 14, 2024 · 0 comments
Open

Limits are not per-resource despite documentation #4173

AntonZhuchkovXOR opened this issue May 14, 2024 · 0 comments

Comments

@AntonZhuchkovXOR
Copy link

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:

  1. Deploy multiple resources using the specified image.
  2. One resource should cast a batch of events every 3 seconds.
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant