Using the Diagnostic Data in Reports - 8.2.0 - Jaspersoft Community

Jump to content

We've recently updated our Privacy Statement, available here ×

This documentation is an older version of JasperReports Server Administration Guide. View the latest documentation.

Overview of JasperReports Server Administration
Overview of Organizations
- Single Default Organization
- Multiple Organizations
- Levels of Administrators
Overview of the Repository
- Folder Structure
- Resources
- Browsing and Searching
Overview of Users and Roles
- Administering Users and Roles
- Delegated Administration
Overview of Security
Administrator Login
- JasperReports Server Heartbeat
- Administrator Email
Administrator Pages
User and Role Management
- Managing Organizations
- Managing Users
- Managing Roles
- Managing Attributes
Repository Administration
- Resource Types
- JasperReport Structure
- Managing Folders and Resources
- Multiple Organizations in the Repository
- Repository Permissions
Data Sources
- Attributes in Data Source Definitions
- JDBC Data Sources
- Managing JDBC Drivers
- JNDI Data Sources
- AWS Data Sources
- Azure SQL Data Sources
  - Uploading an Azure Certificate File to the Repository
  - Creating an Azure SQL Server Data Source
- Snoflake Data Sources
- Hadoop-Hive Data Sources
- MongoDB Data Sources
- Virtual Data Sources
- TIBCO Data Virtualization
- XLS and XLSX Data Sources
- File Data Sources
- Bean Data Sources
Other Resources in the Repository
- Queries
- Datatypes
- Lists of Values
- Input Controls
- Query-based Input Controls
- Cascading Input Controls
  - Parameters in Input Control Queries
  - Creating a Cascading Input Control
- File Resources
Themes
- Introduction to Themes
- How Themes Work
- Administering Themes
- Creating Themes
- Working With CSS Files
Admin Console
- Schedules
- Alerts
- Diagnostics
Import and Export
- Import and Export Catalogs
- Dependencies During Import and Export
- The Import-Export Encryption Keys
- Import and Export Through the Web UI
- Import and Export Through the Command Line
- Alternate Import-Export Scripts
  - Running Import from Buildomatic
  - Running Export from Buildomatic
System Configuration
- Configuration Settings in the User Interface
- Configuration for Using Proxies
- Configuration for Session Persistence
- Enabling Compression in Tomcat
- Configuring Ad Hoc
- Enabling Data Snapshots
- Enabling Data Staging
- Configuring Cloud Services
- Configuring Domains
- Configuring JasperReports Library
- Disabling Open In Editor Option
- Configuring Input Control Behavior
- Configuring the Scheduler
- Configuring Report Thumbnails
- Configuring the Heartbeat
- Configuring the Online Help
OpenTelemetry
- Usecases
- Configuring OpenTelemetry and Jaegar Agent
Server Diagnostics
- Configuring System Logs
- Using Log Collectors
- Auditing and Monitoring Events
- Configuring Auditing and Monitoring
- Using the Audit Data
  - Audit Domain Items
  - Audit Reports and Ad Hoc Views
- Using the Monitoring Data
  - Monitoring Domain Items
  - Monitoring Reports and Ad Hoc Views
- Importing and Exporting Event Data
- Real-Time Diagnostics
- Exposing Diagnostics Through Jaspersoft’s JMX Agent
- Using the Diagnostic Data in Reports
- Excluding Diagnostic Attributes
- Disabling Real-Time Diagnostics
- Server Monitoring
Troubleshooting
- Number of Users Exceeded
- Running Out of Database Connections
- Data Chooser is Slow
- Fields Not Listed in Ad Hoc Editor
- Field Names Disappear in Ad Hoc Editor
- Ad Hoc Filter With All Values Causing Error
- Ad Hoc Dimensions Too Large
- Custom URLs Not Loading in Dashboards
- Print View Not Displaying in Dashboards
- Scheduler Sending Multiple Emails
- Scheduler Not Sending STARTTLS Emails
- Scheduler Running Deleted Jobs
- Scheduler Timezones in Excel Output
- Charts Not Appearing in Excel Export
- Working With Data Sources
  - Logging JDBC Operations
  - JDBC Drivers
  - Database Permissions
  - Unique JDBC Data Source Fields
  - JDBC Database URLs
  - SQL Functions with TIBCO JDBC Drivers
  - Enabling the TIBCO JDBC Drivers for Impala and Cassandra Data Sources
  - Enabling the JDBC Driver for ElasticSearch Data Sources
  - JNDI Services on Apache Tomcat
  - JNDI Services on JBoss
  - JNDI Services on WebLogic
  - Creating a Data Source on SQL Server Using Windows Authentication
  - Upgrading Bean Data Sources
- Special Characters in Database Schemas
- Hadoop-Hive Reports Not Running
- Cassandra Reports Not Running
- Maximum Parameter Size in Wildfly
- Extra Comma Appearing in Time Stamp
- Extra Comma Appearing in Time Stamp
Localization
- Configuring JasperReports Server for Multibyte Fonts
- UTF-8 Configuration
  - Java Options
  - Tomcat
  - PostgreSQL
  - MySQL
  - Oracle
- Changing Character Encoding
- Creating a Locale
- Configuring JasperReports Server to Offer a Locale
Glossary
About This Guide

Using the Diagnostic Data in Reports

In addition to remote JMX connections, 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.

Diagnostic Report in the Repository

The diagnostic topic and report are based on the diagnostic data source. This is a custom data source that encapsulates the JMX information and makes it available as a data source for reports. In addition, there is an Internal Diagnostic Data Source type that can be used to create a new data source. If you accidentally delete the diagnostic data source, select Create > Data Source, set the type to Internal Diagnostic Data Source, and set the name and location to re-create it.

The following figure shows the beginning of the diagnostic report. This report displays nearly every field available through JMX and the diagnostic subsystem. This report serves as a reference for the diagnostic data. The report is also very useful when configuring your server, because it shows many server configuration settings as well as system information such as memory use. You can use this information to fine tune the performance of your JasperReports Server instance.

Contents of the Diagnostic Report

Share

Go to documents

User Feedback

0 Comments

Recommended Comments

There are no comments to display.

×

×

Create New...