[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23243 [Metrics/Website]: Write a specification for Tor web server logs
#23243: Write a specification for Tor web server logs
-----------------------------+--------------------------------
Reporter: iwakeh | Owner: metrics-team
Type: enhancement | Status: needs_revision
Priority: High | Milestone:
Component: Metrics/Website | Version:
Severity: Normal | Resolution:
Keywords: metrics-2017 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------+--------------------------------
Changes (by karsten):
* status: needs_review => needs_revision
Comment:
Replying to [comment:63 Sebastian]:
> I read the specification, I didn't spot any errors.
Thanks for checking!
> I think maybe the sorting deserves a bit more prominence, maybe with a
sentence explaining that it's not possible to aggregate identical lines
without breaking log analysis tools?
Adding such a sentence sounds doable.
But I'm unsure how to make that sorting step more prominent.
Like, we cannot move that part elsewhere in the spec, because the sorting
really happens as one of the last steps of the sanitizing process.
And I'd rather avoid using markup like writing this paragraph in italics
or boldface. (In fact, I'm not even sure how to do that in the XML we're
using, though I'm not ruling out that it's possible.)
What we could do is be more verbose about this step and explain why it's
so important to sort lines.
Would you maybe want to give this a try and rewrite that paragraph and
also add the sentence explaining that aggregating lines would break tools?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23243#comment:64>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs