PDF Printing

The printer pod is configured by environment variables. Normally, no manual configuration is required. With administrator discretion, the following environment variables are available.

1. Using a text editor of your choice, edit the config file based on the SevOne Data Insight version as shown in the table in section find config file to set the following environment variable and then, save it.
   Important: If the config file does not exist, please create one and add the following to it.

   For SDI 6.8.x and below, enable debug logging

   
   printer:
     env:
       PRINTER_DEBUG: "true"
   

   For SDI 7.0.x and above, enable debug logging

   
     printer = {
       env = {
         "PRINTER_DEBUG": "true"
       }
     }

2. Apply the change made to the config file.

   $ sevone-cli playbook up --tags apps

When enabled, additional information is logged.

• Browser console messages.
• HTTP requests and responses like the Network tab in dev tools.
• Report structure info, such as sections and widgets being printed.
• Event communication between the printer and User Interface.

It is not advised to increase this setting. Though, it might make sense to decrease it in specific situations if the Page Crashed Error occurring on certain reports.

Increase report concurrency by scaling the printer pod, instead.

The printer pod can be scaled up to the same number of agent nodes in your cluster. Each pod replica can process an additional 5 concurrent requests.

1. Using a text editor of your choice, edit the config file based on the SevOne Data Insight version as shown in the table in section find config file to set the following environment variable and then, save it.
   Important: If the config file does not exist, please create one and add the following to it.

   For SDI 6.8.x and below, set desired number of printer replicas

   
   printer:
     replicas: 3
   

   For SDI 7.0.x and above, set desired number of printer replicas

   
   printer = {
     replicas = 3
   }
   

2. Apply the change made to the config file.

   $ sevone-cli playbook up --tags apps

Default resolution is high enough to produce smooth graphics for display and printing on high resolution devices.

If PDF file size becomes a problem, this setting can be used to decrease file size by reducing the resolution.

The printer allows up to 15 minutes to print a report before timing out. If a report contains many widgets that take a significant amount of time to render, it should be split up into smaller reports.

If there is a problem during print, it is possible the report will timeout early at 30 seconds because it was unable to start the User Interface in the browser. This appears in the log as:

Timeout waiting for reportload

The Chromium browser can sometimes report a Page Crashed Error in the printer logs. This indicates an out of memory condition that caused the browser to fail to render.

Verify the Kubernetes host has available memory for the pod. Check for any printer configuration in the config file that might increase resource utilization. For example, environment variable PRINT_REPORT_CONCURRENCY can impact memory utilization.

SevOne Data Insight maintains a cache of the printed PDF files for scheduled reports. Depending on your usage of report scheduling, it is recommended to occasionally clean up the cache to free up disk space.

Execute the following command to delete files older than one week (604800 seconds).

$ sevone-cli exec graphql -- "npm run asset-sweeper -- \
--prefix=scheduledReports --age=604800"