Open imballinst opened 8 months ago
Nevermind, I'm dumb 🤦 I didn't realize that there's this --log-level
option when running the Docker container.
docker run --log-level error typesense/docsearch-scraper:0.9.1
It will now only log the "> DocSearch:" stuff, resulting in less verbosity. Could we have this added in the Docs as well? I think this part can be improved:
If needed, you can send the output to both stdout and a file at the same time by adding | tee scraper-output.txt to the end of the command. This is helpful because the output can be very verbose.
We can add something like:
You can reduce the verbosity of the output by passing the
--log-level
option (fromdocker run
) to "error", for example,docker run --log-level error typesense/docsearch-scraper:0.9.1
.
EDIT: 🤦 (2nd time) I think I was confusing the log level between dockerd and docker run 😬 so this post is possibly invalid
Description
Hello! I would like to have a feature where the scraper outputs less verbose thing. According to https://typesense.org/docs/guide/docsearch.html#run-the-scraper:
While using the same approach I can also make it output to a text, using, say,
> output.txt
, it will also silence the error (if any). Would it be possible that we can have aLOG_LEVEL
or something as environment variable when running the Docker scraper?Steps to reproduce
Expected Behavior
We have something like
LOG_LEVEL
that allows us to filter logs, so that in CI we can get only, say, error logs and not the "debug" logs.Actual Behavior
We can't (?) configure log levels, which causes the logs to be rather overwhelming
Metadata
Typesense Version: (not related to Typesense version) OS: (not related to OS version)