-
Notifications
You must be signed in to change notification settings - Fork 1
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
Service does not report any logs #35
Comments
Logs for the service are written to files, see: https://github.com/elastic/data-extraction-service?tab=readme-ov-file#logging So you can run a |
Can we also pipe the logs into stdout so that I'm able to just |
I suppose we could investigate it. We don't have many (any?) logs for the lua nginx logic that's actually "ours". And I'd feel a bit odd about further exposing the tika logs, since we don't want to support "tika", but our service. Maybe the answer really is to just have more logging in our lua code? I've re-labeled as an enhancement. |
I'd say it would help to see nginx logs for endpoints: called |
Bug Description
Running service from a docker image I see no logs when content is extracted at all. Can I do anything about it?
To Reproduce
Steps to reproduce the behavior:
use_extraction_service
totrue
Expected behavior
Logs are displayed about requests received.
The text was updated successfully, but these errors were encountered: