This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Envoy is becoming a popular reverse proxy in the cloud native space. Although it is supported by Instana for monitoring and tracing, we found one case where traces are marked as erroneous, but should not be: Client disconnects.
When a client closes the connection to envoy before getting the response, envoy will set the response status code to 0. Instana interprets this as an error. Nginx does something similar in case the client disconnects, but respond with the status code 499. The status code 499 is not considered erroneous by Instana.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Hi @Guest,
We have attempted to reproduce the issue on our end but haven’t been successful so far. It would be very helpful if you could provide us with a test case that reliably triggers the bug.
Here is how we tried reproducing the issues:
I've tried several times with https://github.com/instana/envoy-otel-tracing, Envoy 1.35.0 and "kill -9 ${pid_of_client_app-app.jar}" and restarting the client app with "docker-compose restart client-app". I've also tried
"while [ 1 ]; do sleep 15; docker-compose restart client-app; done"
Most promising:
while [ 1 ]; do for i in `pidof java`; do OUTPUT=$(sudo ls -l /proc/$i/fd); GOUT="$(grep client-app <<< $OUTPUT)"; if [ -n "$GOUT" ]; then echo "$i is a client-app - killing it"; sudo kill -9 $i; fi; done; sleep 2; docker-compose restart client-app; sleep 20; done
Thank you!