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
Currently, each Ballerina statement is captured as an event in trace spans. While this could be helpful in locating code lines when errors occur, it significantly increases data sent per each trace data export. On the other hand, it is possible to locate relevant code lines using logs as well, which makes this information redundant if logs are available. Therefore, it is useful to make event capturing configurable.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Observability
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered:
Description
Currently, each Ballerina statement is captured as an event in trace spans. While this could be helpful in locating code lines when errors occur, it significantly increases data sent per each trace data export. On the other hand, it is possible to locate relevant code lines using logs as well, which makes this information redundant if logs are available. Therefore, it is useful to make event capturing configurable.
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Observability
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: