clp
clp copied to clipboard
y-scope
Compressed Log Processor (CLP) is a free log management tool capable of compressing text logs and searching the compressed logs without decompression.
### Bug Searching for `" info "` in the webui searches for the literal string `" info "`, including the quotes, meaning that the query doesn't find matches for `...
### Request I'm looking at CLP and would like to know if you have tried writing an SQL query engine or a query engine for any other declarative language that...
### Request I would like to know if it is possible to store CLP compressed data in S3 and query it through Athena using SQL? ### Possible implementation NA
### Bug I am trying to compress the json input file which contains the larger json (may be larger than 1MB )per line and the total file size is around...
### Bug When handling compression job with multiple input paths, the compression scheduler silently log and skip any input that doesn't resolve to any real on disk path. The compression...
### Bug I have compressed json logs using clp-s which look like the following: {"level": "INFO", "message": "Fetched Profile of user 1"} {"level": "INFO", "message": "Fetched Profile of user 2"}...
### Bug When searching using the package's `sbin/search.sh` script, sometimes, not all results are printed (but they exist in the results cache). The scheduler/worker logs don't show any errors. It's...
### Bug On a log file consisting of the following example data `{"a": [{"b": "c"}]}` Search will work correctly for queries like `a.b: c` and `a.b: *`, but will fail...
### Bug Currently CLG replaces ? with * in the search query because we don't handle ? wildcard and fallback to decompression and match. However, this doesn't consider the case...