Integration health and sync logs

Overview

Integration health shows whether each connected integration is keeping its data current in Zluri. Sync logs record every sync Zluri runs, with its status, stages, and timings.

A connected integration can stop syncing without losing its connection. The Health column on the Connected page flags these integrations, and Sync Logs shows which syncs ran, what data they covered, and where a failed sync stopped. Users who can view the Connected page can view health and sync logs. Users who can act on the Connected page can also reconnect integrations.

What this feature enables

The table below summarizes what integration health and sync logs provide.

Health states

Each instance on the Connected page shows one of the following health states.

Health updates automatically and recovers on its own after the next successful full sync, upload, or push. Instances whose setup isn't complete don't appear on the Connected page.

How Zluri calculates health

Zluri judges health in two ways, depending on how an integration gets its data.

For scheduled integrations, the following rules apply.

• A full sync is a scheduled sync that fetched every type of data the integration collects and finished updating Zluri. Users-only syncs don't change health or Last Sync.
• Zluri retries a failed sync automatically, after 45 minutes and again after 90 minutes. Health reflects the failure only after these retries. Credential failures show Errored straight away, without retries.
• A new instance shows Initiated for up to 48 hours while its first full sync runs, and doesn't show Critical in that time.
• Zluri judges each instance only on the types of data its integration collects.
  For uploaded or pushed integrations, only the latest finished upload or push counts. A CSV file uploaded once a month stays Healthy as long as the latest upload succeeded. Uploads still in progress don't change health.

When syncs are paused for an instance, an integration, or your organization, the instance shows Degraded, however long the pause lasts.

View integration health

The Connected page lists every connected instance, grouped under its integration. Integrations needing attention appear at the top.

Steps

1. Navigate to Sources > Integrations > Connected.
2. Hover over the health badge on a collapsed integration to see how many of its instances need attention.
   • The integration badge shows the most severe state among its instances, in this order: Errored, Critical, Degraded, Initiated, Healthy, Disconnected. Disconnected instances don't change the integration badge.
   • The count includes instances in Degraded, Critical, and Errored.
3. Select the arrow next to an integration to expand its instances.
   • The Health column stays visible on the right as the table scrolls horizontally.
4. Hover over an instance's health badge to see the reason for its state.
5. Select a filter chip (Errored, Critical, Degraded, Healthy, Disconnected, or Initiated) to show only instances in that state.
   Each instance row shows the following columns.

Reconnect an errored integration

An instance shows Errored when Zluri can't use its current credentials. The health badge tooltip reads "Unable to use current credentials. Reconnect this connector with updated credentials."

Steps

1. Navigate to Sources > Integrations > Connected.

2. Select the arrow next to the integration to expand its instances.

3. Select the three-dot menu on the row of the instance marked Errored.

4. Select Reconnect.

5. Complete the connection steps for the integration using the updated credentials.
   

   

View an instance

Select an instance name on the Connected page to open its page. The header shows the instance name, health, type, who connected it, and Last sync.

The instance page has the following tabs.

The Integration Details panel shows Health, Application, Connected by, Scopes Connected, Capabilities, Users, Accounts, and Connected on.

View sync logs

Zluri shows sync logs in two places: Sources > Sync Logs for every integration, and the Sync Logs tab on an instance page. Each row is one sync, with the newest first.

Steps

1. Navigate to Sources > Sync Logs.

   • To see one instance only, open the instance page and select the Sync Logs tab instead.

2. Select a status chip to show only syncs with that status.

3. Select the filter icon, then select Type to show only syncs from certain integration types.

4. Select the search icon, enter a connector or instance name, and press Enter.
   

   

The sync log table includes the following columns.

Data Coverage Up To applies to incremental data only. Its tooltip reads "Applies to incremental data only: how far this run fetched new data up to, which is not the same as when it ran."

Each sync has one of the following statuses.

The Type filter includes the following integration types: Direct, CSV, JDBC, AI Powered, SDK, Agent, and Partner.

View sync details

Select any row in Sync Logs to open the sync details panel. The panel title shows the sync start time.

Steps

1. Navigate to Sources > Sync Logs.

2. Select a sync row.

3. Review the stage timeline under Status.

4. Select the copy icon next to Sync ID to copy it.

5. Select the link icon next to the connector at the bottom of the panel to open the instance page.
   

   

The panel shows the following details for each sync.

Every sync passes through the following stages.

Each stage shows In Progress, Successful, Failed, or Skipped, with the time it ran.

View entity details and uploaded files

For CSV, SDK, LDAP, JDBC and certain direct integrations, the sync details panel includes an Entities tab. The tab breaks the sync down by entity, such as Users, and lists any uploaded CSV files.

Steps

1. Navigate to Sources > Sync Logs.
2. Select the Entities tab.
3. Select the arrow next to an entity to expand it.
   • The expanded entity shows its stages, start time, and runtime.
4. Under Uploaded CSVs, select the download icon next to a file to download it.

   • Each file shows its record count, for example 10 records.
     

     

Messages

The following messages appear in health tooltips and sync details.

Constraints

The following constraints apply to integration health and sync logs.