How to Create Application Monitors

Overview

Arovy offers three types of application monitors to help you stay on top of what your connected Salesforce applications are doing. This article walks through how to configure each monitor type: Object & Field Access, Uptime, and New User.

Applies to: Arovy Detected Apps | Feature: Application Monitors (Event Monitoring)
 

Prerequisites

• Event Monitoring enabled
• At least one application approved and monitored in Arovy
• Email addresses ready for notification recipients

Estimated Time

~5 minutes per application

Background: The Three Monitor Types

Step-by-Step Instructions

Step 1: Open the Monitor Configuration for an Application

1. Scroll down to Detected Apps.
2. Locate the application you want to monitor and click Monitor App (or open an existing monitored application).
3. Navigate to the Monitors tab. The available monitor types are listed here.
   
   

Step 2: Configure Object & Field Access Monitor

This monitor is pre-configured out of the box — Arovy automatically establishes a baseline of the objects and fields the application currently accesses. You only need to set notification recipients.

1. Click into the Object & Field Access monitor.
2. Select the team members who should receive email alerts when the application accesses new objects or fields outside its baseline.

3. Click Save.

   Example: If Marketo is connected to your Salesforce org and a team member maps a new custom object, this monitor will send an alert detailing exactly which new objects and fields were accessed.

Step 3: Configure Uptime Monitor

The Uptime monitor detects when API traffic between an application and Salesforce drops off within an expected window — catching silent integration failures that wouldn't otherwise trigger an alert.

1. Click into the Uptime monitor.

2. Set the Monitoring Window — how frequently you expect API calls to occur for this application. Common options include:

   • Every hour (for business-critical, always-on integrations)
   • Weekdays only (for integrations that run during business hours)
   • Custom interval based on the application's expected cadence

   

3. Select notification recipients for uptime alerts.

4. Click Save.

   Example: If an integration user's account is frozen and the OAuth tokens are revoked, the application may still be running on its host (e.g., AWS) but will stop sending API traffic to Salesforce. The Uptime monitor will catch this data flow failure and alert your team.

Step 4: Configure New User Monitor

The New User monitor sends an alert whenever a new user OAuth-authenticates with an application — helping you enforce policies that require dedicated integration users for connected apps.

1. Click into the New User monitor.
2. Select notification recipients for new user alerts.

3. Click Save.

   Example: If your policy requires that only designated integration users connect to a specific app, and someone OAuth-authenticates using their personal Salesforce account instead, this monitor will alert you immediately so you can investigate and reinforce the policy.

Expected Results

After configuring monitors for an application:

• Object & Field Access alerts fire whenever the application reads objects or fields outside its established baseline
• Uptime alerts fire if no API traffic is detected within your defined monitoring window
• New User alerts fire whenever a new OAuth connection is established with the application
• All alerts are delivered via email to the recipients you specified

Troubleshooting