Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to query specific 'compressd file' via web console? #598

Open
dkhwangbo opened this issue Nov 19, 2024 · 1 comment
Open

How to query specific 'compressd file' via web console? #598

dkhwangbo opened this issue Nov 19, 2024 · 1 comment

Comments

@dkhwangbo
Copy link

Like 'index pattern' in ES&Kibana, How to query with specific file?
Is it the only way to query the entire compressed file?

@dkhwangbo dkhwangbo changed the title How to query specific compress file via web console? How to query specific 'compressd file' via web console? Nov 20, 2024
@kirkrodrigues
Copy link
Member

Hi @dkhwangbo,

Sorry for the slow response!

The web console currently doesn't support filtering for specific compressed files but if you're using clp-text, you can filter by file path from the command line:

sbin/search.sh --file-path <file-path> <query>

For example:

sbin/search.sh --file-path /var/log/syslog 'CRON'

We plan to add support to do the same in the web interface. Let us know if this is a must-have feature for you and we can try to prioritize it.

If you want something more similar to how Elasticsearch's indices work, then you could try clp-text's tagging feature. During ingestion, you can assign one or more tags to each set of logs you ingest:

sbin/compress.sh --tags <tag1>,<tag...>,<tagN> <log-paths>

And then you can search by tag:

sbin/search.sh --tags <tag1> <query>

Note that both of these features are currently only supported by clp-text, but let us know if you're using clp-json and we can prioritize adding the same for clp-json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants