[
https://issues.apache.org/jira/browse/HTRACE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056455#comment-15056455
]
stack commented on HTRACE-329:
------------------------------
bq. I sort of get what you're saying, but I feel like the kind of people who
are going to be looking at raw JSON are probably also people who won't mind
short labels.
The people who will be looking at these labels when it counts most are those
who are trying to integrate htrace. They will run into issues. They will have
these opaque labels and a UI that they are trying to figure out how to work.
Opaque JSON in logs makes their integration/debug job more difficult.
bq. We have all these GUIs and tools-- shouldn't we be using them to view
traces?
I'm looking at traces dumped in logs trying to figure why my stuff is broken.
That there are tools and GUIs is nice and all but how to make use of them is a
task (what in this JSON is the span ID? What is the parent ID? How do I
interpret this JSON dump?).
bq. Google's tracing system for Chrome also uses JSON with very short labels--
two letters in their case...
This is 100% better than what is going on here and they are pure JSON where
here we have the msgpack option that all will be using anyways for transport
(it encodes away label length....) where shortness counts. We need the labels
so can query and figure what is going on from looking in logs and UIs.
bq. The short JSON labels aren't even a problem in our Javascript, since we
have Backbone objects to wrap them and give more friendly labels....
This isn't implemented though, or is it? And bootstrap doesn't help when
looking at logs or figuring what part of JSON to paste into UI or to pass on
cmd line to a tool.
bq. I guess I haven't thought about it much, though...
Understood. You 'know' what is going on having implmented it. I am trying to
convey here what noobs will go through. We should do all we can to make their
life easier.
> JSON labels are opaque and so confound
> --------------------------------------
>
> Key: HTRACE-329
> URL: https://issues.apache.org/jira/browse/HTRACE-329
> Project: HTrace
> Issue Type: Improvement
> Reporter: stack
>
> Debugging, I get this in the log:
> {code}
> 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
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
