Data Security provides real-time visibility into your SaaS App's performance and health. This feature is available for the following apps:

The status of core services like DLP, WildFire, Policy Engine, and URL Analysis are available separately at the top of the applications page. If these core services are down, you can configure admin alerts directly as shown in the example below or configure them in the Settings page.

As a Data Security administrator, you can monitor the following parameters related to your SaaS app's health:

Health Parameter	Description
Status	Healthy Warning (amber) Critical (red) The health status showing the above three statuses are applicable only for the five apps mentioned above. For other apps, it shows only whether it is Scanning, Scanning Off or Not Connected.
Status Description	The following are the possible health statuses (healthy or having issues) that your app might be encountering: Healthy: This application is healthy. Warning (Amber): Rate limit warning: Connector is hitting API limits. User activity fetch delayed: Some features may be limited. Remediation failed: Permission denied. Remediation failed: Internal error occurred. Critical (Red): Authorization Failure: No permission to access data. Please re-authenticate. Data Discovery failed: Unable to download data. Data Discovery failed: Unable to fetch required metadata. User Activity fetch failed: Connector may not perform optimally. Internal error: If this persists, please contact support. These status descriptions are applicable only for the five apps mentioned above. For other apps, there are no status descriptions.
No. of Assets Ingested	Number of new assets downloaded from the SaaS app.
No. of Assets Scanned	Number of assets scanned. It includes assets scanned by DLP service and WildFire service.
Processing Time (P95)	This refers to the time within which 95% of the assets are fully processed. The slowest 5% of assets are excluded to provide a realistic view of system performance. This isn’t a distribution, but a categorical bucket representation of processing time. The P95 processing time is represented using the following fixed buckets: 0–15 minutes 15 minutes–1 hour 1–4 hours 4–12 hours 12–24 hours 24 hours+ For example, in the last 1 hour, if 100 assets were processed end-to-end and the 95th fastest asset was processed in 50 minutes, then the P95 processing time bucket = 15 minutes – 1 hour.
Rate Limits Hit	Number of instances where the API requests were throttled due to rate limit constraints from the app.
No. of Incidents Generated	Number of alerts triggered based on your policy rules.
No. of Incidents Remediated	Number of incidents logged where an automated or manual remediation action was executed.
Users Info	Number of users to whom the asset has been exposed.
Notes	The trend indicators (positive and negative) for assets ingested, assets scanned, and processing time indicate a percentage change compared to the previous equivalent time period.

A sample screenshot for monitoring your app health is given below: