Steps for enabling Auditing and Monitoring Jasper Server (only for administration)

Document created by Prashank Singh Champion on Aug 11, 2017
Version 1Show Document
  • View in full screen mode

JasperReports Server provides comprehensive diagnostics so that administrators can monitor the health and performance of the running server. In version 5.0, the server augments the audit logging with monitoring data that is easier to report against. Version 5.0 also introduces diagnostics that provide real-time information about the running server, such as memory usage. All of these tools can help you troubleshoot issues and analyze performance.

Auditing stores key events that are of interest to system administrators, such as login/logout time, user, report generated, report details, and object sizes. The audited events can be saved and moved to an archive automatically after a specified number of days.
Monitoring is based on audit events and provides a multi-dimensional Domain to create Ad Hoc views. This helps you generate reports that contain key metrics such as which reports use the most resources. This allow you to find places to optimize your data sources and your reports.

Diagnostics provide run-time data that gives the overall health of your server instance. For example, it includes load values such as the number of logged in user, the number of currently running reports, and the number of scheduled reports. The diagnostic data is exposed in a custom data source and can be easily viewed in a report or integrated with industry standard management consoles.


Steps for enabling auditing and monitoring data for jasper server are as below:

1) Path-: %JasperServer_Installed%\webapps\reportservice\WEB-INF



4) applicationContext-audit.xml

      Part 1:

<bean id="auditService"


                 <property name="isAuditPersistenceEnabled" value="true"/>

                 <property name="isMonitoringEnabled" value="${monitoring.enabled}"/>

                 <property name="sessionFactory" ref="sessionFactory"/>

                <property name="persistentClassFactory" ref="persistentMappings"/>

                <property name="clientClassFactory" ref="mappingResourceFactory"/>

                <property name="maxAuditEventAgeToArchive" value="30"/>

                <property name="maxAuditEventAge" value="0"/>




Part 2:

Bean id = “auditEventPurgerTrigger"


property name="jobDetail" ref="auditEventPurgerJob"

property name="cronExpression" value="0 0/10 * 1/1 * ? *" 

 *Above changed value describe trigger event will occurred for every 10 minute



Below are some generated reports after above settings-:








Prashank Singh

Pemari Technology 

1 person found this helpful