MirrorHub/synapse
0
0
Fork 1
mirror of https://mau.dev/maunium/synapse.git synced 2024-11-11 12:31:58 +01:00
Code Issues Projects Releases Wiki Activity
synapse/contrib/lnav
History
Eric Eastwood 887fa4b66b
Switch from matrix:// to matrix-federation:// scheme for internal Synapse routing of outbound federation traffic (#15806) 
`matrix://` is a registered specced scheme nowadays and doesn't make sense for
our internal to Synapse use case anymore. ([discussion]
(https://github.com/matrix-org/synapse/pull/15773#discussion_r1227598679))
2023-06-20 10:05:31 +01:00
..
README.md lnav config for synpase logs (#14953) 2023-02-01 12:36:04 +00:00
synapse-log-format.json Switch from matrix:// to matrix-federation:// scheme for internal Synapse routing of outbound federation traffic (#15806) 2023-06-20 10:05:31 +01:00

README.md

lnav config for Synapse logs

lnav is a log-viewing tool. It is particularly useful when you need to interleave multiple log files, or for exploring a large log file with regex filters. The downside is that it is not as ubiquitous as tools like less, grep, etc.

This directory contains an lnav log format definition for Synapse logs as emitted by Synapse with the default logging configuration. It supports lnav 0.10.1 because that's what's packaged by my distribution.

This should allow lnav:

  • to interpret timestamps, allowing log interleaving;
  • to interpret log severity levels, allowing colouring by log level(!!!);
  • to interpret request IDs, allowing you to skip through a specific request; and
  • to highlight room, event and user IDs in logs.

See also https://gist.github.com/benje/e2ab750b0a81d11920d83af637d289f7 for a similar example.

Example

asciicast

Tips

  • lnav -i /path/to/synapse/checkout/contrib/lnav/synapse-log-format.json
  • lnav my_synapse_log_file or lnav synapse_log_files.*, etc.
  • lnav --help for CLI help.

Within lnav itself:

  • ? for help within lnav itself.
  • q to quit.
  • / to search a-la less and vim, then n and N to continue searching down and up.
  • Use o and O to skip through logs based on the request ID (POST-1234, or else the value of the request_id_header header). This may get confused if the same request ID is repeated among multiple files or process restarts.
  • ???
  • Profit