Fix IllegalArgumentException

✅ Solution

IllegalArgumentException in Zipkin often arises from incorrect UTF-8 encoding/decoding when interacting with storage systems like Elasticsearch or OpenSearch. Ensure your Zipkin storage configuration specifies UTF-8 encoding consistently and that data being sent to Zipkin is valid UTF-8; double-encoding is a common culprit. Review your storage configuration and upstream services to verify UTF-8 handling, potentially needing to adjust encoder/decoder settings to ensure data integrity.