[HTRACE-329] JSON labels are opaque and so confound

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 10/Dec/15 06:06
• Updated: 14/Dec/15 22:58

Description

Debugging, I get this in the log:

2015-12-09 21:56:21,293 ERROR [localhost:61345.activeMasterManager] core.Tracer: Can't close TraceScope for {"a":"b45638d30b8c6e1dbdc001c6e7f1dd8f","b":1449726980426,"d":"get","r":"hconnection-0x6a38397","p":["b45638d30b8c6e1dbd33cf6dc5ce5206"]} because it is not the current TraceScope in thread localhost:61345.activeMasterManager

I could go consult a dictionary if such a thing existed on the htrace website (currently it does not) or go read up on some source code... but this is JSON so a.) perf is not a consideration so why bother shortening the labels in the name of 'perf' benefits and b.) JSON is ".. easy for humans to read and write." (second sentence on the website) yet here were are frustrating the first half of this sentence.

Suggest more readable labels.

Issue Links

• duplicates: HTRACE-96 One letter JSON field names are not user friendly