microsoft / microsoft/aspire

"Error disposing log descriptor" log level

Open
#8,173 0 comments 1 reaction 0 assignees View on GitHub
area-orchestrator
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

One of my apps got a random `Error disposing log descriptor` error. (Similar to #5995, although this time with a different error).

Whilst it would be nice to fix the underlying timeout error (although as I have no repro steps or additional logs, I'm not sure this is a particularly actionable), I wonder if this class of errors issues really be logged at Error level - sure it's a failure from the perspective of an engineer working on DCP. However the error doesn't seem to have any user impact, nor is there anything I can do as an aspire user to fix or mitigate it, so there seems little value in sharing it with the user - and particularly not as a bright red error that makes users think they've done something wrong.

```
fail: Aspire.Hosting.Dcp.dcp.start-apiserver.api-server.container-logstreamer.LogDescriptorSet[0]
Error disposing log descriptor {"ResourceName": {"name":"prometheusMetricsAdapter-bsqbtjgs"}, "ResourceUID": "946ef89e-b34f-4e9a-8ee6-cd558b90a2f4", "error": "context deadline exceeded\ncontext deadline exceeded"}
```

### Expected Behavior

This error seems benign with no visible impact, so more like it should be at a warning level. Or possibly even Debug as I can't find any user impact from this error which would require me to know about this error.

### Steps To Reproduce

Unfortunately no repro steps.

### Exceptions (if any)

fail: Aspire.Hosting.Dcp.dcp.start-apiserver.api-server.container-logstreamer.LogDescriptorSet[0]
Error disposing log descriptor {"ResourceName": {"name":"prometheusMetricsAdapter-bsqbtjgs"}, "ResourceUID": "946ef89e-b34f-4e9a-8ee6-cd558b90a2f4", "error": "context deadline exceeded\ncontext deadline exceeded"}

### .NET Version info




### Anything else?

This has some relation to #5995, although the exact error is different.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.