Troubleshooting TrueSight Operations Management Report Engine for performance reporting
This topic provides information on how to analyze and troubleshoot problems that you might experience when using BMC TrueSight Operations Management Report Engine for performance reporting:
No performance data is collected
If there are no errors, but data is not getting transferred make sure that BMC TrueSight Infrastructure Management Server is registered and attribute sets are defined with type as external report. To generate the list of all available PATROL parameters that collect data in the TrueSight Infrastructure Management Server, run the following SQL query on the TrueSight Infrastructure Management database or use the runsqli command:
||';'|| a.unitname ||';'|| m.displayname ||';'|| dispname from attribute_meta
a, mo_meta m where a.motypeid=m.motypeid and a.attrtype=4 and a.tablename like
'_PATROL__%';
Also, check that BMC TrueSight Infrastructure Management Server and report engine clocks are in sync.
Report Engine generates STATS/RATE data Comma Separated Value files
The Report Engine generates STATS/RATE data comma separated value (.csv) files, continuously. These files are generated in either of the following scenarios:
- Data transfer to Report engine database fails due to database issues
- Not enough space on disk
- Any other database related problem
To check if the comma separated files are being generated
To check if the comma separated files are generated, perform the following steps:
- Navigate to ReportingInstallLocation\ReportEngine\tools\jboss\server\all\transformations\datagapjob directory.
- Open the following directories and check if comma separated values are present:
- csvfilesstats
- csvfilesrate
To solve this issue:
- Resolve any database issues.
- Monitor for 24 hours. In case of data gaps, data from CSV files will be inserted into Report Engine database and will be automatically deleted in next 24 hours.
- If CSV files are generated due to other exception, take backup of the CSV files and store them on different safe location.
Database job status log file
The dbJobStatus.log file has information about the execution of database jobs configured for the Report Engine. You can use this log file to check if a job was executed or not.
The information for this log file is the print status of the database logs that comes from the ReportingDbActivityStatusJob command, which the Report Engine runs every hour.
If a user does not have access to the Report Engine database server, this log file is very useful for checking the status of a database job.
Queries to monitor the performance data recollection