Configuring Logging for the PDF Service

It is recommended that you configure your PDF Render Service to write its logs to LogScale.

As the LogScale PDF Render Service runs in a container, you need to configure your container to write out logs to stdout or a file. You can then ship the service logs into LogScale using LogScale Collector (or any compatible log shipper).

Log to stdout (Recommended for Containers)

By default, or by setting the log output to stdout, container orchestration platforms (Kubernetes, Docker, etc.) can capture logs natively:

bash
LOG_TO_STDOUT=true

Log to a File

If you need file-based logging, you can configure the log file path by mounting a volume and pointing the service to it:

bash
LOG_FILE=/path/to/logfile.log

You would then mount a persistent volume to that path in your container spec.

For containerized deployments, stdout logging is strongly preferred because it:

  • Integrates with Kubernetes logging (for example: kubectl logs)

  • Works with log shippers (LogScale Collector, Fluent Bit, Fluentd, and so on)

  • Avoids disk space management issues inside containers

Once the logs are emitted from the PDF Render Service container, you can configure your log shipper to ship the logs into LogScale. For details on how to do this with LogScale Collector read the documentation.