FortiSIEM
FortiSIEM provides Security Information and Event Management (SIEM) and User and Entity Behavior Analytics (UEBA)
Andy_G
Staff
Staff
Article Id 191180

Description

 
This article describes how to troubleshoot report generation problems after an SVG image upload. 
 


Scope

If a new SVG logo is uploaded to be displayed on exported report PDFs, and the report fails to generate or displays a "Generation Error" message, the SVG file is likely to contain a link to an external image file. 
SVG files which refer to an external image file are supported. However, the image file must be available to the report engine or the rendering of the SVG file will fail, and cause the generation of the report to fail.
 


Solution

To determine if the SVG file is the source of the problem encountered, open the SVG file in a text editor and look for any references to external image files. The lines in the SVG file which refer to external images may look something like the following:
 
xlink:href="myImage.png"
sodipodi:absref="C:\Program Files\images\myImage.png"
 
To fix the problem, change the reference in the SVG file so that it points to an image location somewhere on the server's physical file system, and copy the image file to that location.
 
First copy the external image to the FortiSIEM server in the following directory: \opt\phoenix\config
Then change the reference in the SVG file. Using the example above, after having copied the logo to the correct location, change the lines so they read:
 
xlink:href="file:///opt/phoenix/config/myImage.png"
sodipodi:absref="/opt/phoenix/config/myImage.png"
 
Change "myImage.png" in the example, to the actual file name of the image being referred to by the SVG file.
 
Finally, re-import the altered SVG file using the Admin > General Settings > UI screen.

 

Contributors