Domain preferences
Domain preferences are the settings that determine the default behavior of different aspects of the web application as well as the authentication methods used for domain logins. Your domain users will, in many cases, be able to personalize their user settings and override the domain's default settings you define here.
To review and modify any of these settings, go to Preferences in the navigation pane, then select the Account Preferences tab.
Global
These preferences affect aspects of user sessions in the Devo domain as well as how Devo manages event loading in a user's browser.
| Inactivity Period for session expiration (in minutes) | Specify the period of time during which a user can be inactive (that is, not interact with the system in any way) without any impact on their session. After the inactivity period expires, the user is locked out of the session and must log back in to continue working with Devo. This is valid only when Set an inactivity time is selected. |
|---|---|
| Set an inactivity time | Select if you want to set an inactivity timeout for domain session. Otherwise, user sessions will remain open until closed by the users. |
| Home page | Specify the home page to open when Admin users log in to this domain. |
| Language | Specify the language of the application. This means that by default, all of your Devo users will use the same language during their Devo sessions. This, however, can be overridden in a user's individual preferences. |
| Use browser language | Select this option to use the language configured in the user's web browser. When selected, this setting overrides the Language field. |
| Enable Real Time Event Flow by default when opening a search | Select to activate real time data flow by default when opening a data table or query. Otherwise, data tables will open with the time range end date set to the moment they were opened. |
| Default opening time range in Data Search | Specify the time range that determines which events to load in Data Search by default. The maximum is 24 hours. This will apply to all users and all data tables in the domain. |
Maximum number of events (in thousands of events) | Maximum number of events to load in a browser for all open queries. When this limit is reached, Devo will begin to remove less relevant events from the browser to make room for the newer or more relevant events. This works in parallel with the Maximum memory used such that Devo will begin to remove events once either of these values are reached. |
Maximum memory used (in Megabytes) | Maximum amount of browser memory to use including all open queries. When this limit is reached, Devo will begin to remove less relevant events from the browser to make room for the newest events. This works in parallel with the Maximum number of events such that Devo will begin to remove events once either of these values are reached. |
Sample period to determine if the maximum number of events has been reached (in milliseconds) and Maximum number of events that can be reached in sample period (in thousands of events) | Devo can automatically stop a query's real-time event flow when it detects that there is a risk of the browser being overloaded by an excessive amount of data. You can specify a threshold number of events and a time to threshold that define the potential risk for browser overload. For example, with a sample period of 10 seconds and a maximum number of events set to 15,000, real-time event flow will stop when more than 15,000 are loaded in any 10 second period. |
| Hide demo tables in Finder | Check this box to hide the demo.*.* tables when using the Finder. |
AVM
These parameters affect the Systems Monitoring application.
| Machines per view | Select the number of machines to be displayed per page in the application. |
|---|---|
| Autosave Filter | Select to retain the tag filter the user applies from session to session. |
Alerts
These preferences affect how alerts will be displayed by default in the Alerts Dashboard for domain users. These settings can be overridden by a user's alert preferences.
| Time Period of Alerts to show | Select the default period of time used in the Alerts Overview graph in the Alerts Dashboard. |
|---|---|
| Days of life of your alerts (30 minimum) | Indicate how many days you wish alerts to be available for domain users. The minimum is 30 days. |
| Autosave Filter | Check this box if you want to retain the filter a user applies to the Alerts History from one session to the next. |
| View open alerts | Check this box to see only open alerts in the Alerts History. |
| Show chart | Choose the chart type to display by default in the Alerts Overview. |
| Show Pie chart | Select to show the layered pie chart in the Alerts Overview. |
Annotations
Annotations are the comments you can append to triggered alerts to track actions taken in response to the alert condition. Use these settings to determine how the annotations are displayed to Devo users in this domain. These settings can be overridden by a user's annotation preferences.
| Display collapsed | Select to display alert annotations with the details collapsed by default. Otherwise the details will be displayed expanded and readable by default. |
|---|---|
| Show confirm on delete | Select if you want users to be prompted to confirm before deleting an annotation. |
| Show confirm on change task status | Select if you want users to be prompted to confirm before changing the status of a task. |
API/OData
These are the credentials used for OData V2 authentication when you set up a query as an OData feed.
| Basic Authentication User | Default user for OData V2 API basic authentication. |
|---|---|
| Basic Authentication Password | Default password for OData V2 API basic authentication. |
Authentication
You can log in to a Devo domain using your user and password, but stricter policies can be implemented in this area. Learn how to do it in the User authentication article.