logparser
logparser copied to clipboard
coroot
A library and a CLI tool for clustering unstructured logs.
Currently, the functionality involves viewing only ERROR and WARN patterns at the log level. This is a big problem for services with high fault tolerance where there are errors being...
Hello, We are trying to use this logparser to get patterns from our local files. From our apache access log, I have this log - which when passed to NewPattern...
We've a case where coroot-node-agent (logparser) accidentally merges multiple json logs into one but we expect to receive them one-by-one. Output: ``` {"context":"App:TypeOrmTransactionContext","level":"debug","timestamp":"2024-02-21T12:35:48.232Z","ms":"+1ms","span_id":"2aa1bcfe9bc837f2","trace_id":"1167fdf089bce248aa87fddee93eedff","msg":"..."} {"context":"App:TypeOrmTransactionContext","level":"debug","timestamp":"2024-02-21T12:35:48.239Z","ms":"+7ms","span_id":"2aa1bcfe9bc837f2","trace_id":"1167fdf089bce248aa87fddee93eedff","msg":"..."} {"context":"App:TypeOrmTransactionContext","level":"debug","timestamp":"2024-02-21T12:35:48.239Z","ms":"+0ms","span_id":"2aa1bcfe9bc837f2","trace_id":"1167fdf089bce248aa87fddee93eedff","msg":"..."} ``` We fixed this issue...
Introduces a tail mode (`-f` flag) to the log processing tool, enabling real-time analysis of incoming log data. PS: the current implementation doesn't handle output exceeding screen height for simplicity
