| Table of Contents | ||||
|---|---|---|---|---|
|
...
| Info |
|---|
Domain vs User In general, when a setting is present both in the user and domain preferences, the user always takes preference over the domain. |
...
| Anchor | ||||
|---|---|---|---|---|
|
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.
General | |
|---|---|
Default inactivity time 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 remain open until manually closed. |
Set as maximum inactivity time | Check this option to mark the given value as the maximum inactivity time for all the users in the domain. |
Initial page (only Admin users) | Specify the landing page when Admin users log in to this domain. |
Language | Default language |
- Specify the language of the application. This means that by default, all of your Devo users use the same language during their Devo sessions. This 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, the Language field is disabled.
| ||
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 open with a time range whose end date corresponds 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 applies to all users and all data tables in the domain. | |
Default case sensitivity in searches | Some query operations have a case sensitive and a case insensitive version, for example, Contains - case insensitive (weakhas) and Contains (has, ->). This setting defines the default (Case sensitive or Case insensitive) in the Operations over fields when you run a search. Operations that do not have a sensitive and insensitive version are visible regardless of the option selected. This setting also affects the behavior of global searches in your domain. If you select the Case sensitive option, the global search is case sensitive, and the operation used to filter the data is Contains tokens (toktains). If you select Case insensitive, the operation used is Contains tokens - case insensitive (weaktoktains). Learn more in Run a global search. | |
Data search settings | ||
Browser load thresholds | Event count threshold (in thousands) | |
- Maximum number of events to load in a browser for all open queries. When this limit is reached, Devo begins to remove less relevant events from the browser to make room for the newer or more relevant events. This works in parallel with the Browser memory threshold, so that Devo begins to remove events once either of these values are reached. |
Browser memory threshold (MB) |
- Maximum amount of browser memory to use including all open queries. When this limit is reached, Devo begins to remove less relevant events from the browser to make room for the newest events. This works in parallel with the Event count threshold, such that Devo begins to remove events once either of these values are reached. | |
Real-time event flow cutoff | Event count threshold (in thousands) |
|---|
and |
Time to threshold (milliseconds) |
- Devo can automatically stop a query's real-time event flow when it detects a potential risk for the browser to be overloaded with an excessive amount of data. You can specify a threshold for the number of events and a time that defines 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, the real-time event flow stops when more than 15,000 are loaded in any 10-second period. | |
Time control settings | Reference time |
|---|
- Select the default reference time for tables that contain both creation and event dates. The creation date refers to when data is generated at the source, whereas the event date is when Devo receives and ingests the data. Creation date mode is only applied to tables whose source technology supports it. |
Reception delay |
- Set the maximum expected delay between the creation date and the event date. If the delay period for your data never exceeds a specific length of time, being as accurate as possible helps the platform return results more quickly. This is only enabled when the creation date mode is selected. |
Hide demo tables in finder | Check this box to hide the |
|---|
| Anchor | ||||
|---|---|---|---|---|
|
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. |
| Anchor | ||||
|---|---|---|---|---|
|
Alerts
These preferences affect how alerts are 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 want 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. |
Graphics visualization | Choose the chart type to display by default in the Alerts Overview. |
| Anchor | ||||
|---|---|---|---|---|
|
...
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 are 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. |
Learn more about annotations in Add a comment to a triggered alert.
...
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. |
| Anchor | ||||
|---|---|---|---|---|
|
...