Given our support of backwards compatibility, does anyone have a preference for how traces are stored?
I ask because I have noticed some places where our internal trace hooks are named with collisions so that you get multiple events with the same identifier which are actually different events. I would like to change them, ideally for 1.5.2 and 1.6.1(0?) simply because it's hampering the ability to do performance testing and tuning.
But I'm not sure if A. we're okay making these changes from a compatibility perspective and B. we're okay making these changes as part of a minor release.
If they're ambiguous to you, then they're ambiguous to any user. If you don't have enough information to understand what the traces are timing, that is a bug. Fix it in 1.5.2.
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext