[tor-dev] onionoo overload_general_timestamp (prop 328)

[nusenu]

>> Was there a particular motivation for this format change and granularity?
>> And what do you think about changing it to use the YYYY-MM-DD hh:mm:ss
>> format for consistency and having a direct human readable format here as well?
>>
>> related:
>> Karsten used to maintain onionoo protocol documentation/changelog and versions:
>> https://metrics.torproject.org/onionoo.html#versions
>> Is that and the 'version' field in onionoo no longer maintained?
>> (since it didn't change with the new fields)
> 
> Sure, we intend to maintain the version field, and since new fields have been added the protocol version should have been updated.
> 
> The reason I haven't updated it yet was that I wasn't very pleased that we had to add the overload_ratelimits [1] and overload_fd_exhausted [2] fields in the bandwidth document. We needed to expose these fields, but we also knew these didn't belong to this document. So the idea was to plan a bigger release with a little restructure of the onionoo internals and update the protocol version then.
> 
> Said this I will update both the timestamp and the protocol version for consistency.

Is there a gitlab issue where this is tracked?


btw:
"DNS timeout reached" can probably be removed from:
https://metrics.torproject.org/onionoo.html#details_relay_overload_general_timestamp

kind regards,
nusenu
-- 
https://nusenu.github.io