|
The time your business hours end. Format: hh:mm
|
|
|
Only show business hours during weekdays.
|
|
|
Show business hours
|
|
|
Display business hours on rrd graphs.
|
|
|
Color to use for business hours
|
|
|
The color to be shown for business hours
|
|
|
After this number of days, the business hours will not be added to the graph. <br/>Recommended: 62 days
|
|
|
Refresh Poller Table Per Cycle
|
|
|
This setting is for a single poller systems only to rebuild the poller output table on each polling cycle to prevent the memory table from swapping on very large systems with large databases that could use swap.
|
|
|
Periodic All Device Re-Index
|
|
|
At what frequency do you wish to Re-Index all Devices. This Re-Index will occur at midnight at the frequency that you select.
|
|
|
Weekly on Sunday
|
|
|
The number of concurrent Poller Command processes. The will be at most one concurrent command per host within the Poller Command pool.
|
|
|
The "Distinguished Name" syntax, applicable for both OpenLDAP and Windows AD configurations, offers flexibility in defining user identity. For OpenLDAP, the format follows this structure: <i>"uid=<username>,ou=people,dc=domain,dc=local"</i>. Windows AD provides an alternative syntax: <i>"<username>@win2kdomain.local"</i>, commonly known as "userPrincipalName (UPN)". In this context, "<username>" represents the specific username provided during the login prompt. This is particularly pertinent when operating in "No Searching" mode, or "Require Group Membership" enabled.
|
|
|
This refers to the specific attribute within the LDAP directory that holds the usernames of group members. It is crucial to ensure that the attribute value aligns with the configuration specified in the "Distinguished Name" or that the actual attribute value is searchable using the settings outlined in the "Distinguished Name".
|
|
|
Use a separate subfolder for each hosts RRD files. The naming of the RRDfiles will be one of the following:<br><ul><li><path_cacti>/rra/host_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_id/data_query_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_hash/device_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_hash/device_id/data_query_id/local_data_id.rrd.</li></ul><br>You can make this change after install by running the CLI script <b>structure_rra_paths.php</b> after you make the change. NOTE: If you change Max Directories value to decrease the number of directories, or if you change the Directory Pattern, empty directories will not be pruned after you rerun the <b>structure_rra_paths.php</b> script.
|
|
|
Which Directory Pattern do you wish to use for Structured RRD Paths. 'Device ID' is the default. The setting 'Device ID/Data Query ID' should be used when you have Devices with thousands of Graphs. After Changing the Directory Pattern, you must run the Structured Path CLI script again to modify the RRDfile paths to the new Pattern.
|
|
|
Device Hash/Device ID/Data Query ID
|
|
|
Max Device Hash Directories
|
|
|
The maximum number of Device Directories to be created based upon hashed Device ID's.
|
|
