The Settings page controls global WebReports behavior, including report processing, scheduling, Bridgit AI, database notifications, statistics, application maintenance, log cleanup, and security-related integrations.
Important: Some settings can affect application performance, security, report availability, and scheduled report processing. Review changes carefully before saving them.
Opening the Settings page
- Sign in to WebReports with an administrator account.
- Select Configuration from the navigation menu.
- Select Settings.
Changes apply immediately to the current application instance and within approximately 60 seconds on other instances.
Application settings for user presence, reports, scheduling, queues, statistics, CORS, Bridgit AI, maintenance, log cleanup, and iframe access.
User Presence
Track online users and last activity
Records whether signed-in users are online and when they were last active.
Enable this option when administrators need to view user-presence information in Management. Disabling it stops presence tracking and the related background updates.
Reports Options
Visualize Report Cache Sliding Expiration
Determines how many inactive minutes a cached Visualize report remains available.
The expiration period restarts whenever the cached report is accessed. A longer period may improve repeat-load performance but keeps report data in memory longer.
Default: 45 minutes
Reports Cleanup Timer
Determines how frequently WebReports checks report data storage for items eligible for cleanup.
Shorter intervals identify expired report data sooner but cause the cleanup process to run more frequently.
Default: Every 1 hour
Scripting
Controls whether report scripts can run in WebReports.
- Unrestricted allows report scripts to run.
- Deny prevents report scripts from running.
Important: Selecting Deny may prevent reports that rely on scripts from working as intended. Test existing reports before changing this option.
Session Timeout
Determines how many inactive minutes can pass before WebReports requires the user to authenticate again.
Shorter sessions reduce the time an unattended session remains accessible. Longer sessions reduce repeated sign-ins but extend the exposure period.
Default: 60 minutes
Enable In-Memory Report Cleanup
Enables the automatic removal of inactive reports from application memory.
Keep this option enabled to prevent inactive report instances from accumulating. The inactivity period is controlled by InMemoryReport Remove After Inactivity.
Default: Enabled
InMemoryReport Remove After Inactivity
Determines how many inactive days must pass before an in-memory report becomes eligible for removal.
This value is used only when Enable In-Memory Report Cleanup is enabled. Lower values release memory sooner, while higher values retain inactive report instances longer.
Default: 14 days
Report Default Retention
Determines how many days completed report output remains available before automatic removal.
Shorter retention reduces storage growth. Longer retention preserves more report history.
Default: 3 days
Important: Reducing this value may cause completed reports to be removed sooner than users expect.
Remove Scheduler History Days
Determines how many days WebReports retains successful, failed, and other scheduler execution records.
Shorter retention helps control database growth. Longer retention provides more information for auditing and troubleshooting.
Default: 60 days
Important: Reducing this value may remove older scheduler history sooner than expected.
Scheduler Host Control
Disable Scheduled Reports on Hosts
Lists application hosts that must not execute scheduled reports.
Enter multiple machine names separated by semicolons. This option is useful in multi-instance deployments where scheduler workloads should run only on selected hosts.
Leave the field empty to allow scheduled reports to run on every eligible host.
Important: Verify each host name before saving. Adding a host to this field prevents that host from processing scheduled reports.
Queue and Threads
These settings control how many report operations WebReports can run simultaneously and how many requests can wait for processing.
Increasing concurrency may improve throughput when sufficient resources are available, but it may also increase CPU usage, memory use, and database contention.
Scheduled Reports Parallel Threads
Determines the maximum number of scheduled reports that can run simultaneously. Additional reports wait until a thread becomes available.
Default: 1 thread
Suggested starting points:
- Small environments: 1–2 threads
- Medium environments: 2–4 threads
Test changes outside production hours.
Scheduled Reports Capacity
Determines how many scheduled report requests can wait for execution.
When the queue reaches capacity, additional scheduled requests may be delayed until space becomes available.
Default: 50 requests
Capacity controls waiting work; parallel threads control actively running work.
Server Administration Capacity
Determines the maximum queued workload available for background server-administration operations.
This setting prevents an unbounded background queue from affecting the application.
Default: 500 operations
Queue and Download Reports Parallel Threads
Determines how many Queue and Download report requests can run simultaneously. Additional requests wait for a thread to become available.
Default: 5 threads
Suggested starting points:
- Small environments: 2–5 threads
- Medium environments: 5–10 threads
Queue and Download Reports Capacity
Determines how many Queue and Download report requests can wait for execution.
Higher values allow WebReports to accept more requests during busy periods. Increasing capacity does not increase the number of reports that run simultaneously.
Default: 50 requests
Statistics
Enabled
Controls whether WebReports records process memory, CPU, and report-activity snapshots.
Disable this option only when operational statistics are not required.
Default: Enabled
Retention
Determines how many days collected WebReports statistics remain available.
Longer retention supports trend analysis but increases database storage.
Default: 7 days
Valid range: 1–30 days
Sampling Interval
Determines how frequently WebReports records process memory, CPU, and report-activity snapshots.
Shorter intervals provide more detail but increase database activity. The open Statistics page refreshes every 30 seconds independently of this setting.
Default: 30 seconds
Valid range: 5–3,600 seconds
CORS Options
Allowed Hosts
Lists external origins permitted to make cross-origin requests to WebReports.
Enter multiple origins separated by semicolons. Include only trusted origins that require access.
Leave this field empty when cross-origin access is not required.
Important: An overly broad list may expose WebReports data to unintended websites.
Bridgit AI
Analysis Model
Selects the AI model Bridgit uses for report analysis.
The available models are supplied by WebReports. Model selection can affect analysis quality, response time, and API usage.
API Key
Provides the protected API credential used to connect Bridgit AI.
The key is stored securely by WebReports. Leave the existing masked value unchanged unless you are replacing or removing the credential.
Important: Treat API keys as secrets and restrict access to this page.
Max Tokens
Limits the number of tokens Bridgit can generate for an analysis response.
Higher limits permit longer responses and may increase response time and API usage. The selected model may enforce a lower maximum.
Default: 65,536 tokens
Streaming
Controls whether a Bridgit response appears as it is generated.
Streaming can improve perceived responsiveness for longer answers. Disable it when an integration requires the complete response before displaying it.
Default: Disabled
System Prompt
Defines the system-level instructions applied to Bridgit analysis requests.
Keep the instructions concise, avoid including sensitive information, and test prompt changes before using them in production.
Default: You are a helpful assistant.
Database Maintenance
Enable Notification
Enables email alerts when the WebReports database reaches the configured size threshold.
Alerts are sent to the listed recipients when database maintenance detects that the threshold has been reached.
Default: Disabled
Notification Threshold
Determines the database size, in gigabytes, that triggers a maintenance notification.
Select a value that provides enough time to investigate database growth before storage becomes constrained.
Default: 8 GB
Notify Emails
Lists the email addresses that receive database-size alerts.
Separate multiple addresses with semicolons. A working WebReports email profile is required for email delivery.
Application Maintenance
Enable Start Notification
Enables a notification the next time the application starts normally.
Saving this setting does not restart WebReports. The notification is evaluated during the next normal application startup.
Default: Disabled
Notify Emails
Lists the email addresses that receive application-start notifications.
Separate multiple addresses with semicolons. A working WebReports email profile is required for email delivery.
Logging Cleanup Options
Enable
Enables automatic removal of WebReports log records after the configured retention period.
Keep this option enabled to control long-term log growth. Disable it only when another process manages log retention.
Default: Enabled
Remove Logs After Days
Determines how many days WebReports logs are retained before automatic removal.
Shorter retention reduces storage use. Longer retention preserves more history for troubleshooting and audits.
Default: 30 days
Important: Reducing this value may remove older logs sooner than expected.
IFRAME Options
Allowed Hosts
Lists the hosts permitted to embed WebReports in an iframe.
Enter multiple hosts separated by semicolons and include only trusted sites. Iframe embedding is disabled when this field is empty.
Important: Allowing an untrusted host may expose users to clickjacking or misleading embedded content.
Saving or restoring settings
After making changes, select Save.
To return the settings to their WebReports default values:
- Select Restore Defaults.
- Review the restored values.
- Select Save to apply them.
Restoring defaults can replace environment-specific configuration. Record any custom values you may need before using this option.
Comments
0 comments
Please sign in to leave a comment.