Opened 6 weeks ago

Last modified 5 days ago

#30830 new task

Modify snowflake broker logs to make them easier to process for measurements

Reported by: cohosh Owned by:
Priority: Medium Milestone:
Component: Circumvention/Snowflake Version:
Severity: Normal Keywords: logs, stats anti-censorship-roadmap-july
Cc: arlolra, cohosh, phw, dcf Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor28

Description

We recently produces graphs from the unsanitized broker logs here. However, the script to produce these graphs was complicated due to the structure of the log messages. We should evaluate log output from the broker and decide what to keep, what to change, and what to discard.

Child Tickets

Change History (3)

comment:1 Changed 6 weeks ago by cohosh

We should also consider how and why we want to distinguish between these logs and the corresponding data and the broker stats we export to metrics (#21315)

comment:2 in reply to:  1 Changed 4 weeks ago by cohosh

Replying to cohosh:

We should also consider how and why we want to distinguish between these logs and the corresponding data and the broker stats we export to metrics (#21315)

My thoughts on this are to use the metrics output in #21315 for measurements, and to use the default broker logs for debugging purposes. The only reason I can see for using the default broker log output for additional measurements are if there are long-term measurements we can do at the broker that are too sensitive for periodic export and display by the metrics team.

The stats exported in #21315 have all of the information needed for the graphs produced in #30693 (except for TLS/HTTP errors which fall into the debugging bucket).

comment:3 Changed 5 days ago by gaba

Keywords: anti-censorship-roadmap-july added
Note: See TracTickets for help on using tickets.