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
It helps when a warning log or exception is thrown when unintentionally operating on finished spans.
In asynchronous workflows, a span that is finished may be propagated down unintentionally. In other cases, Kamon.runWithSpan(span) { ...} may be used with default finish=true param, and asynchronous flow could be started from inside. Any operations on such finished span are silently lost. Discovering that spans are missing this is hard enough, and happens at the wrong times when it is desperately needed. Debugging how the missing information in the span came about is another painful exercise.
A simple warning message that "you are trying to update a finished span" is sufficient to help debug such situations. Right now, nothing is emitted in logs.
The text was updated successfully, but these errors were encountered:
It helps when a warning log or exception is thrown when unintentionally operating on finished spans.
In asynchronous workflows, a span that is finished may be propagated down unintentionally. In other cases,
Kamon.runWithSpan(span) { ...}
may be used with defaultfinish=true
param, and asynchronous flow could be started from inside. Any operations on such finished span are silently lost. Discovering that spans are missing this is hard enough, and happens at the wrong times when it is desperately needed. Debugging how the missing information in the span came about is another painful exercise.A simple warning message that "you are trying to update a finished span" is sufficient to help debug such situations. Right now, nothing is emitted in logs.
The text was updated successfully, but these errors were encountered: