The Overview tab answers one question: is audit data arriving from Dynamics 365 the way it should be. It is the first place to look when something feels wrong, and the place you can safely ignore when everything is healthy.

Select Dashboard in the left navigation, then Overview.

Audit Overview

Four figures across the top.

Figure 1. The Dashboard Overview tab showing the Audit Overview KPI row, Environment Status and Sync Latency cards for a single environment.

Figure Tells you Total Audit Records How many audit records EaseLog holds for this environment, with the change this month. Active Users Today How many audited users have been active today, and what share of all users that is. Synced Environments How many environments are connected, and how many of those are healthy. Avg Daily Growth How many records are arriving per day on average.

Avg Daily Growth is the one to watch over time. A sudden change means either something in Dynamics 365 changed, or the sync is struggling.

Environment Status

Synced environment count and a health percentage, with a bar breaking the environments into Healthy, Warning and Failed.

Anything other than 100 percent healthy is worth following up on the Queue Overview page for the affected environment.

Sync Latency

How far behind EaseLog is running, measured as the delay between an event happening in Dataverse and arriving in EaseLog.

Current Latency sits on a scale from 0 minutes to 20 or more. Min Latency and Max Latency show the range. Low numbers mean EaseLog is keeping pace.

Sync Completion

Incremental offload progress, as a ring showing the percentage complete, with the number of records Synced and the number Remaining.

100 percent with zero remaining means this environment is fully caught up.

Figure 2. The lower half of the Dashboard Overview tab showing the Sync Completion ring at 100 percent and the Mirror Lag by Environment chart.

Mirror Lag by Environment

How stale each environment's copy is compared with the newest audit record, banded into three:

Band Meaning Fresh Less than an hour behind. Lagging Less than a day behind. Stale Further behind than that.

Lagging is not automatically a problem. An environment set to sync every 12 hours will spend most of its time lagging by design. Read this alongside the sync schedule before drawing a conclusion.

While the first sync is running

If an environment is still completing its first pull, a banner appears above the cards reading Initial sync in progress with a percentage, and warns that the charts cover imported data only. Figures will look low until it finishes. That is expected.

Note

Every card has its own refresh control and a Last updated time. Refresh all at the top of the page updates every card at once.