search

elastic / data-extraction-service

Other
12 stars 0 forks source link

Service does not report any logs #35

Open artem-shelkovnikov opened 1 month ago

artem-shelkovnikov commented 1 month ago

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:

  1. Configure a Google Drive connector and set use_extraction_service to true
  2. Run Data Extraction Service in docker
  3. Run a sync and check logs for Data Extraction Service
  4. No logs are displayed at all

Expected behavior

Logs are displayed about requests received.

seanstory commented 1 month ago

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 docker exec command to tail those, or SSH into the container to tail them.

artem-shelkovnikov commented 1 month ago

Can we also pipe the logs into stdout so that I'm able to just docker logs <id>?

seanstory commented 1 month ago

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.

artem-shelkovnikov commented 1 month ago

I'd say it would help to see nginx logs for endpoints:

called /subextract: 200 OK called /subextract: 500 INTERNAL SERVER ERROR