Audit Diagnostic & Monitoring of Reports in Jasper Server Pro 6.3

•Auditing stores key events that are of interest to system administrators, such as login/logout time, user, the 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 allows 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.

Events Being Audited and Monitored :

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/events-being-audited-and-monitored

Configuring Auditing and Monitoring :

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/configuring-auditing-and-monitoring

Go to ./WEB-INF/js.config.properties

audit.sizeof.enabled=true
audit.records.enabled=true
feature.audit_monitoring.enabled=true
monitoring.records.enabled=true

Set this property to true to enable the auditing and monitoring subsystem. Given the default value of the other settings, only auditing is turned on when this setting is first set to true.

Using the Audit Data :
JasperReports Server makes the audit data available to administrators through Domains and several prepared views and reports. These are located in the /Public/Audit folder of the repository.

There are two Domains and two sets of reports created for accessing audit data:
•Audit Domain and Audit Reports – Use these to view the current audit data; they run against the active audit database.
•Audit Archive Domain and Archived Audit Reports – Use these to run reports on archived data; they run against the archive database.
The contents of both Domains and reports are identical—they differ only in the database tables that are accessed in each case.
To create an Ad Hoc View based on the audit Domains, select Create > Ad Hoc View, select the Domains tab in the Data Chooser, and expand the folders to select one of the audit Domains.
Audit Reports and Ad Hoc Views :

The following views and reports are provided:
•Audit Report – Generic example of a an audit report showing commonly audited events.
•Performance Crosstab Report – A crosstab that shows average performance of reports that were run.
•Performance Report – Generates a list of reports that were run and sorted by run-time to identify slow reports.
•Repository Resources Report – Shows repository resources and their associated events.
•Resource Execution Report – Generates a list of reports that were run.
•User Activity Report – Generates a list of reports run by a specific user.

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/using-audit-data

Using the Monitoring Data :

JasperReports Server makes the monitoring data available to administrators through a Domain and several prepared views and reports. These are located in the /Public/Monitoring folder of the repository.

Monitoring Views and Reports :

The monitoring reports and their views are blank by default, because the audit subsystem that monitoring depends upon is disabled by default and no audit data exists. To view these reports, first enable auditing as described in section Configuring Auditing and Monitoring, then wait for user activity to generate events.
A number of Ad Hoc views based on the monitoring Domain are provided in the Public/Monitoring/Monitoring Reports folder.

The reports are designed to cover common monitoring needs and can be used as-is. When monitoring is enabled and audit events are being recorded, the reports will contain up-to-the-minute records of events on your server. You can run the reports or schedule them as needed.

The Ad Hoc view used to create each report is included as well. You can open these in the Ad Hoc editor to explore the monitoring data in real-time. You can also modify these views in the Ad Hoc Editor to generate new reports to suit your monitoring requirements.

The following views and reports are provided:
•Report Monitoring Resources Report – Gives a list of all reports that were run and shows their average and high-low runtimes.
•Report Monitoring Details Report – A crosstab that shows report runtimes on one axis and many dimensions such as a time hierarchy, user and organization, and event type on the other axis

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/using-monitoring-data
Using the Diagnostic Data In Reports :

JasperReports Server makes the diagnostic data available to administrators for internal reports. The following resources are visible to the system admin (superuser by default) in the repository:

•/Public/Diagnostic/Diagnostic Data Source – A custom data source that returns all of the diagnostic fields.
•/Public/Diagnostic/Diagnostic Report – A report that displays nearly every single diagnostic field.
•/Public/Ad Hoc Components/Topics/Diagnostic Topic – A JRXML resource that can be used as a Topic to create an Ad Hoc view using diagnostic fields.

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/using-diagnostic-data-reports

Excluding Diagnostic Attributes :

The JasperReports Server diagnostic feature exposes a set of managed beans (MBeans), each with a number of JMX attributes. By default, all attributes of all MBeans are available. If you would like to limit what is exposed, you can exclude any of the attributes or entire beans through the following configuration file:
…/WEB-INF/applicationContext-diagnostic.xml
•To exclude an attribute, locate the MBean where it is defined and uncomment it from the excludedDiagnosticAttributes property. For example, if you want to hide sensitive information about your internal database, modify the diagnosticRepositoryDatabaseInfoCe MBean as follows:

<bean id=”diagnosticRepositoryDatabaseInfoCe” class=
“com.jaspersoft.jasperserver.api.logging.diagnostic.jmx.DiagnosticDynamicMBean”>
<property name=”diagnosticServices”>
<set>
<ref bean=”repositoryDatabaseInfo”/>
</set>
</property>
<property name=”excludedDiagnosticAttributes”>
<set>
<value>DatabaseProductName</value>
<value>DatabaseProductVersion</value>
<value>DriverName</value>
<value>SQLKeywords</value>
<value>URL</value>
<value>UserName</value>
<value>JDBCMajorVersion</value>
<value>JDBCMinorVersion</value>
<!–
<value>MaxRowSize</value>
<value>MaxStatementLength</value>
<value>MaxConnections</value>
<value>MaxCharLiteralLength</value>
<value>MaxColumnsInTable</value>
<value>MaxColumnsInSelect</value>
<value>MaxColumnsInGroupBy</value>
<value>MaxColumnNameLength</value>
–>
</set>
</property>
</bean>

•To exclude an entire bean, comment it out or remove it from the list of beans in the diagnosticExportingMBeansMap. For example, instead of excluding selected attributes, you could remove the entire repository database MBean as follows:

<util:map id=”diagnosticExportingMBeansMap” >
<entry key=”jasperserver:name=Users” value-ref=”${bean.diagnosticUsers}”/>
<entry key=”jasperserver:name=Reports” value-ref=”${bean.diagnosticReports}”/>
<entry key=”jasperserver:name=Scheduler” value-ref=”${bean.diagnosticScheduler}”/>
<entry key=”jasperserver:name=Settings” value-ref=”${bean.diagnosticSettings}”/>
<entry key=”jasperserver:name=Repository” value-ref=”${bean.diagnosticRepository}”/>
<entry key=”jasperserver:name=About” value-ref=”${bean.diagnosticJSAbout}”/>
<entry key=”jasperserver:name=HibernateStatics”
value-ref=”${bean.diagnosticHibernate}”/>
<entry key=”jasperserver:name=EhCache”
value-ref=”${bean.diagnosticEhCache}”/>
<entry key=”jasperserver:name=ExternalInfo”
value-ref=”${bean.diagnosticExternalInfo}”/>
<!–
<entry key=”jasperserver:name=RepositoryDatabase”
value-ref=”${bean.diagnosticRepositoryDatabaseInfo}”/>
–>
</util:map>

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/excluding-diagnostic-attributes

Disabling the Diagnostic Subsystem :

By default the JMX diagnostic subsystem is always enabled, but external access is password-protected and requires opening the diagnostic port in your firewall as described in Exposing Diagnostics Through Jaspersoft’s JMX Agent. If you wish to disable all external access, see Disabling Remote Connections to the JMX Agent.
Internally, the diagnostics subsystem is passive and has no performance impact until it is accessed in a report through the diagnostic data source. However, if you wish to disable the entire diagnostic subsystem, rename or remove the following files:

•applicationContext-diagnostic.xml
•applicationContext-diagnostic-pro.xml

http://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/disabling-diagnostic-subsystem.

Thanks & Regards

–A.Prasanth kumar.

Best Open Source Business Intelligence Software Helical Insight is Here

A Business Intelligence Framework

Free
Download