Search

Administrator Guide

Administrator Guide

10.2.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2

Back Next

Dashboard and Reports System Properties

Dashboard and Reports System Properties

After you install the Dashboard and Reports component, you can use system properties to modify certain aspects of the Dashboard behavior.

The following table describes the Dashboard and reports system properties:

System Property	Description
dx.dashboard.url	Connection string to the dashboard server, in the following format: http://<hostname>:<port>/<dashboard name> If you use HTTPS to connect to the Operation Console, the URL must match the value of the property. Otherwise, the Dashboard does not appear. For example: https://myhost:18443/ dx -dashboard
dx.dashboard.max.timewindow	Maximum time frame in hours that Operation Console users can select to display unresolved error events in the Dashboard. Default is 96.
dx.dashboard.jdbc.username	User name for the operational data store database.
dx.dashboard.jdbc.password	Password for the operational data store in an encrypted string database. If you change the password you must encrypt the string with the password encryption utility and use the encrypted string.
dx.dashboard.jdbc.url	Location of operational data store. The location must be different from the B2B Data Exchange repository.
dx.dashboard.show.at.startup	Determines whether to show the Dashboard when users log on to the Operation Console. Default is True.
dx.dashboard.errorrate.threshold.low	Maximum error event percentage to display in the green area of the Error Rate Gauge panel. Any percentage higher than this value is displayed in the orange area. Default is 25.
dx.dashboard.errorrate.threshold.high	Maximum error event percentage to display in the orange area of the Error Rate Gauge panel. Any percentage higher than this value is displayed in the red area. Default is 75.
dx.dashboard.sla.detection.midnight.latency	Time after midnight in minutes from which to start the calculation level. For example, if you define an SLA rule with a calculation level of a single day, you can set the value to 60 minutes to start the calculation at 01:00 instead of midnight. Available for SLA rules in which violations are reported at the end of the time frame. Default is 120.
dx.first.day.of.week	Numeric representation of the first day of a calendar week. For example, the value 1 represents Sunday. Use this property to determine the first day of the week when you define an SLA rule with a calculation level of a week. For example, if you define Monday as the first day of the week, violations are reported for a week that starts on Monday and ends on Sunday. Default is 2.
dx.ods.latency.seconds	Number of seconds between the time the event finished processing and the time that the event load process starts. The operational data store event loader loads events for which the processing time difference in seconds is equal or greater than this value. For example, if you increase the latency to 60 seconds, the event loader only loads events that finished processing at least 60 seconds before the load process starts. Default is 0.
dx.ods.row.limit.thousands	Number of thousands of events to load in each batch when the total number of events is higher than this value. If the total number of events to load is less than the value in this property, the operational data store event loader runs one batch. If you set the row limit to 0, the event loader runs one batch regardless of the number of events. Default is 500. Must be numeric and greater than or equal to 0.

Dashboard and Reports Management

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.