5 ms·
This looks great! Thank you for putting it up on GitHub and sharing Have you tried it with log files? It would be great to have this kind of search when huntin
by nico 3y ago
This looks great! Thank you for putting it up on GitHub and sharing
Have you tried it with log files? It would be great to have this kind of search when hunting things down on multiple large log files in a server
- darrenldl 3y ago> This looks great! Thank you for putting it up on GitHub and sharing Thank you! > Have you tried it with log files? It would be great to have this kind of search when hunting things down on multiple large log files in a server That is an interesting suggestion, and I can see the myself wanting to use Docfd search engine even for line oriented input. Just to make sure I didn't misunderstand, log files in your context mean things that have one entry per line, and no point in searching across lines, correct?
- nico 3y agoI guess it depends on what I’m looking for But usually yes, most of the times the search case is: * I have an id/uuid or some text or a piece of some id/text * there are multiple log files, each for a different process/daemon/app which handle different parts of a workflow * I have to grep each log file individually and then piece things together to figure out how the workflow went for some usage/user Usually there is a lot of back-and-forth between the log files and the grep commands to find the info I need, especially if what I’m looking for is not an id/uuid
- darrenldl 3y agoI see. Docfd right now should be fine for the id/uuid part, but the "piece of text" can be problematic as right now there is no way to ask Docfd to constrain search to line level. I'll add a --line-oriented-exts command line argument that defaults to "log", so searching anything *.log will not be cross line boundaries. Are there other file extensions you're dealing with?
- nico 3y agoUsually only .log files, although sometimes the log files might not have an extension and just be in a logs/ folder and the file name might be something like a date+name of service that writes the log
- darrenldl 3y agoGotcha. In the latter case, would file globbing through bash/whatever suffice? Been trying to avoid opening more cans of worms than I need, but if I really do need to add file globbing then oh well : v EDIT: Scratch that, I'll just add file globbing since I'm that close to covering most use cases anyway.