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

[Improvement]: Capturing events within Ballerina spans #43467

Open
chathurace opened this issue Oct 7, 2024 · 0 comments
Open

[Improvement]: Capturing events within Ballerina spans #43467

chathurace opened this issue Oct 7, 2024 · 0 comments
Labels
Priority/High Team/Observability Observability in general, Metrics, Tracing & Logging Type/Improvement

Comments

@chathurace
Copy link
Contributor

Description

Currently, each Ballerina statement generates one or more events under its span. Such a statement to event mapping may not be optimal as all these event data are published to the trace analytics server and stored there. For example if (regions.length() == 3) line generates two events. We need to come up with more higher-level abstractions for events.

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

@ballerina-bot ballerina-bot added the Team/Observability Observability in general, Metrics, Tracing & Logging label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority/High Team/Observability Observability in general, Metrics, Tracing & Logging Type/Improvement
Projects
None yet
Development

No branches or pull requests

3 participants