System Log- FineBI Help Document

Last update：July 25, 2025

Overview

Version

FineBI Server Version	Functional Change
6.0	/

Application Scenario

1. Some companies have strict control over the data center and a cumbersome application process for entrance, making log retrieval laborious.

2. When urgent issues that need to be located by logs occur, difficult log retrieval may impact the user experience.

3. When reporting product bugs to FanRuan, you need to provide essential environment details. However, it is time-consuming to collect these system environment details due to various reasons.

Function Description

Through the System Log function, the admin can:

1. Export log files filtered by Operation Time and Log Type.

2. View the storage locations of log files with one click.

3. Obtain and export report project environment information with one click.

System Log

Log in to the FineBI system as the admin, and choose System Management > Intelligent O&M. The System Log tab is added, as shown in the following figure.

Note:

In the cluster environment, a cluster selection box is displayed in the upper right of the page. The admin can directly select a cluster node to download the corresponding log.

Operation Time

The admin can select the operation time of the logs that need to be downloaded. Both Year-Month-Day and Dynamic Time are supported. If the specified date exceeds the range of the existing log files, only the existing files will be downloaded.

Year-Month-Day: You can select a specific date (year-month-day) directly, for example, 2020-01-01.
Dynamic Time: You can estimate a date (for example, the beginning of the last quarter) based on the current time.

Log Type

You can export multiple types of debug logs.

Note:

The types of logs available may vary depending on the operating system and deployment configuration of the server.

Log	Description
fanruan.log	It is the operation log of the FanRuan application.
fanruan.gc.log	It is the downtime log of FanRuan.
BIEvent.log	This log is for FineBI projects only. It records FineBI configuration operations.
access.log	It is the access log of FineOps NGINX, recording the request information of users' accesses to FineOps, such as access time, IP address, request method, access path, and HTTP status code.
catalina.log	It is the running log of the Tomcat server, recording mainly the running information of the Tomcat server upon startup and shutdown of the Tomcat server.
catalina.out	It contains the running logs output by Tomcat and the logs output from applications to the console. Whatever is written to the standard output and standard error of Tomcat will be recorded in the catalina.out file.
localhost_access_log.txt	It is the request access log of Tomcat, recording the request information such as the request time, request type, requested resource, and the returned status code.

Effect Display

Click One-Click to Download, and unzip the package. The following figure shows the content of the exported log.

Viewing the Storage Location

Click View Storage Location to view the storage location of the log of each type, as shown in the following figure.

Environment Info Export

Click One-Click to Export to export the environment information, as shown in the following figure.

Note:

In the cluster environment, a cluster selection box is displayed in the upper right of the page. The admin can select a specific node to download the required log.

The exported file is in the XML format. The following table shows the content.

Classification	Inspection Item
System Environment Information	JAR Package Version
	Operating system
	Number of CPU cores
	Memory information
	Disk information
	Max_map_count
	overcommit_memory
	overcommit_ratio
	jvm:version
	jvm:xmx
	jvm:disableExplicitGC
	jvm:useConcMarkSweepGC
	jvm:UseG1GC
	jvm:-Duser.country
	jvm:-Duser.language
	jvm:-Djava.awt.headless
	jvm:HeapDumpOnOutOfMemoryError
	jvm:PerBytecodeRecompilationCutoff
	jvm:PerMethodRecompilationCutoff
	jvm:MaxDirectMemory
	Font information
	Time zone information
	Language environment information
	hostname
	host file information
	gcc information
	Information about the number of opened files
	Swap partition information
BI project information	spider_high_performance_resource_time
	SystemOptimizationConfig.ClientMasterId
	ehcache.db.properties
	FineClusterConfig.params.cluster
	spider_base_update_thread_proportion
	log_level
	open_sql_time_control
	StateServerConfig.type
	SystemOptimizationConfig.biClusterMasterNodeHostName
	WebSocket
	FineDB
	open_cell_control
	StateServerConfig.clusterMode != false
	open_commit_row_count_control
	open_excel_import_cell_count_control
	spider_spark_log_level
	result_set_row_limit
	cache_seconds
	has_web_xml
	open_row_control
	auto_backup
	socket_connect
	BIVersion
	finedbVersion
	useTureVersion
	IntelliReleaseConfig.memoryAlarmOpen
	Domain name in BI
	IP address in BI
	HotBackConf.slave
	HotBackConf.master
	RedisConfig.host
	RedisClusterConfig.servers.host
	ResourceModuleConfig.repositoryName
	ResourceModuleConfig.sharedRepository
	ResourceModuleConfig.repositoryNameOnboot
	MarketConfig.cloudOperationMaintenanceId

Note: 1. Since the deployment method cannot be obtained by the MAC designer, unkown will be displayed.

The deployment method obtained by the Windows/Linux designer is tomcat.

2. The following shows the supported types of deployment containers. unknown will be returned for containers of all unavailable types.

GERONIMO("geronimo")
GLASSFISH("glassfish")
JBOSS("jboss")
JETTY("jetty")
JONAS("jonas")
OC4J("oc4j")
RESIN("resin")
TOMCAT("tomcat")
WEBLOGIC("weblogic")
WEBSPHERE("websphere")
WILDFLY("wildfly")
UNKNOWN("unknown")

Helpful
Not helpful
Only read

中文（简体）中文（繁體）日本語

English

System Log

Overview

Version

Application Scenario

Function Description

System Log

Operation Time

Log Type

Effect Display

Viewing the Storage Location

Environment Info Export

附件列表