App Discovery Setup
This document explains how to enable App Discovery, import demo discovery data, configure blacklist patterns, update the blacklist file, and understand the event data collected by the browser extension. App Discovery helps identify web-based applications used by users when an AppNavi application has not yet been created at the tenant level.
Prerequisites
- Access to the tenant where App Discovery will be configured.
- Permission to open Manage Tenant and update Discovery Settings.
- A supported browser extension installed for users whose application activity should be discovered.
- A clear decision on which URL patterns should be excluded from discovery analytics.
Enable App Discovery
To run App Discovery, enable App Discovery recording from Manage Tenant > Discovery Settings. After App Discovery recording is enabled, the available discovery settings and related options become visible.
-
Open Manage Tenant.
-
Go to Discovery Settings.
-
Enable App Discovery recording.
-
Review the discovery options that become available after the setting is enabled.
App Discovery recording option in Discovery Settings.
Discovery Settings options available after App Discovery is enabled.
The same discovery settings can also be opened from the Discovery tab by using the context menu in the top-right corner.
Discovery tab context menu with the Settings option.
Import Discovery Data
The Import Discovery Data option loads demo data for a newly created tenant. This helps users test and demonstrate App Discovery functionality with sample generated events before live data is available.
Demo data allows users to view the discovery overview dashboard, app overview, discovered apps, shadow apps, company apps, archive usage, assigned risks, and business capabilities associated with discovered applications. If the tenant already contains demo data, importing new demo data replaces the existing demo data.
Import Discovery Data option in Discovery Settings.
For more import information, see Import details.
Configure App Discovery Blacklist Patterns
Blacklist patterns prevent matching applications or URLs from being discovered in the future. Matching applications are excluded on the client side and removed from discovery analytics.
-
Open the Discovery tab.
-
Open the context menu and select Settings.
-
Enable Discovery Blacklist Pattern.
-
Use the App Discovery Blacklist Patterns table to add, edit, deactivate, or delete blacklist patterns.
App Discovery Blacklist Patterns table and pattern actions.
| Action | Description |
|---|---|
| Add Pattern | Open the context menu and select Add. A dialog opens where the user enters the title, pattern, and active status. |
| Edit Pattern | Edit the existing title, pattern, or active status when a change is required. |
| Deactivate Pattern | Deactivate the pattern when it should no longer be part of the blacklist mechanism. Once deactivated, discovery works normally for matching applications. |
| Delete Pattern | Remove a pattern from the table when it is no longer needed. |
Update Blacklist
The Update Blacklist option in the context menu updates the complete JSON blacklist file by using the patterns configured in the App Discovery Blacklist Patterns table.
Update Blacklist option in the App Discovery context menu.
How App Discovery Works
App Discovery provides insight into user engagement with each discovered web application. It tracks activity time based on page interaction, scrolling, and engagement. It does not record user input.
When a user opens a web application and App Discovery is enabled, the extension checks whether the application is blacklisted. If it is not blacklisted and there is no existing local storage data for that application, the extension generates App Discovery data such as activity time, user ID, and application URL. The App Discovery event is sent once within a 24-hour period.
Only the main website is considered for App Discovery. Interactions inside iframes are not counted for activity time.
Event Data Collected by the Extension
| Property | Description |
|---|---|
| browser | Browser where the application is discovered, such as Chrome or Edge. |
| browserLanguage | Browser language, such as en-US or de. |
| countryCode | Country from which the event is recorded, based on the time zone. |
| integrationMode | Integration mode. The default value is extension. |
| pageUrl | Application origin where the event is generated. For example, https://www.google.de, https://www.google.de/search, and https://www.google.de/search?query=23123123 are treated as the same app because only the base URL or origin is captured. |
| userId | Global user ID. If no global user ID exists, the extension creates one and sends it. |
| sessionId | User session based on browser tabs. |
| unixTimestamp | Time when the event is generated. |
| activityTime | Activity time of the user in a discovered app. |
Validation Checklist
- App Discovery recording is enabled in Discovery Settings.
- Discovery settings are accessible from the Discovery tab context menu.
- Demo data can be imported for a newly created tenant when testing is required.
- Blacklist patterns can be added, edited, deactivated, and deleted.
- Update Blacklist refreshes the JSON blacklist file from the configured table patterns.
- Discovery events contain only the expected event properties and do not include user input.
Updated 19 days ago