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

Verify whether Ballerina Errors are properly recorded in HTTP, gRPC and websocket Client Calls #27966

Closed
nadundesilva opened this issue Jan 19, 2021 · 2 comments
Labels
IceBox Older issues that are not being actively worked on but may be revisited in the future. Team/Observability Observability in general, Metrics, Tracing & Logging Type/Task

Comments

@nadundesilva
Copy link
Contributor

nadundesilva commented Jan 19, 2021

Description:
Adding error messages at Java level from all modules separately had been removed as we are recording the errors returned and paniced at ballerina level automatically using the Compiler Instrumentation.

However we need to verify whether error messages are properly added in the Ballerina Errors in HTTP, gRPC and Websocket client calls.

@nadundesilva
Copy link
Contributor Author

We need to check whether the above conditions that are removed from errors are properly captured at ballerina level.

@nadundesilva nadundesilva removed their assignment Jan 10, 2022
@anupama-pathirage anupama-pathirage added the IceBox Older issues that are not being actively worked on but may be revisited in the future. label Nov 21, 2024
@anupama-pathirage
Copy link
Contributor

We are closing this issue due to inactivity. If you need further assistance or have additional input, feel free to reopen it. Thank you for helping us maintain a relevant and focused issue list!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IceBox Older issues that are not being actively worked on but may be revisited in the future. Team/Observability Observability in general, Metrics, Tracing & Logging Type/Task
Projects
None yet
Development

No branches or pull requests

2 participants