> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor integrations

> Monitor on-premises integrations in Cognite Data Fusion (CDF) using tasks, Task log, Task run details, and notifications.

After an on-premises **integration** completes its **connection** (extractor startup and check-in), review **tasks** in <span class="ui-element">Task log</span> and open a row for <span class="ui-element">Task run details</span>.

<Info>
  Integrations is in [public preview](/cdf/product_feature_status#public-preview) and may change. **Tasks** appear only after the connection succeeds. For Extraction pipelines, see [Monitor extraction pipelines](/cdf/integration/guides/interfaces/monitor_integrations).
</Info>

## Open tasks for an integration

<Steps>
  <Step title="Open Integrations">
    Navigate to <span class="ui-element">Data fusion</span> > <span class="ui-element">Integrate</span> > <span class="ui-element">Integrations</span>.
  </Step>

  <Step title="Open the integration">
    Select the on-premises integration. Use the <span class="ui-element">Overview</span>, <span class="ui-element">Errors</span>, and <span class="ui-element">Configuration</span> tabs as needed.
  </Step>

  <Step title="Open a task">
    On <span class="ui-element">Overview</span>, select a **task** by name. A task is a named unit of work from the extractor, such as a query or a continuous process.
  </Step>
</Steps>

## Review Task log

On the task page, use <span class="ui-element">Task log</span> to list executions. Columns include Started, Finished, Status, Configuration, and Details.

<Check>
  If <span class="ui-element">Task log</span> is empty, confirm the extractor is running and that the connection succeeded.
</Check>

## Open Task run details

<Steps>
  <Step title="Open one execution">
    Select a row in <span class="ui-element">Task log</span>, or select <span class="ui-element">See more</span> when it appears.
  </Step>

  <Step title="Inspect the run">
    In <span class="ui-element">Task run details</span>, review <span class="ui-element">Details</span> and <span class="ui-element">Configuration</span>.
  </Step>
</Steps>

## Task types

| Task type                                  | Meaning                                                                                                                         |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| <span class="ui-element">Batch</span>      | Runs to completion in one execution, then finishes. Examples: a one-time startup task, or a scheduled run that exits each time. |
| <span class="ui-element">Continuous</span> | Starts once when the extractor starts and keeps running for the extractor lifetime. Example: a persistent subscription loop.    |

## Review errors

On the integration <span class="ui-element">Errors</span> tab, extractors can report structured errors that you can search and filter.

Each error can include:

| Field              | What it tells you                                                                                                                                   |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Severity           | How serious the issue is: <span class="ui-element">Warning</span>, <span class="ui-element">Error</span>, or <span class="ui-element">Fatal</span>. |
| Error type         | The category of failure, such as general or configuration.                                                                                          |
| Link to task       | Which **task** reported the issue.                                                                                                                  |
| Started / Finished | When the error began and ended, so you can see if it is still active.                                                                               |

Use severity and time range to find active issues, then open the linked **task** to inspect <span class="ui-element">Task log</span> and <span class="ui-element">Task run details</span>.

## Run remote actions

On-premises extractors can declare actions that you trigger from CDF, such as start task, end task, or a custom action. CDF does not need inbound ports on customer infrastructure. The extractor picks up the action on the next check-in, with an optional message and metadata.

Action lifecycle:

| Status    | Meaning                                                      |
| --------- | ------------------------------------------------------------ |
| Pending   | CDF queued the action. The extractor has not started it yet. |
| Running   | The extractor is running the action.                         |
| Succeeded | The action completed successfully.                           |
| Failed    | The action did not complete successfully.                    |
| Canceled  | The action was canceled before it finished.                  |

<Steps>
  <Step title="Open the integration">
    Navigate to <span class="ui-element">Data fusion</span> > <span class="ui-element">Integrate</span> > <span class="ui-element">Integrations</span>, then open the on-premises integration.
  </Step>

  <Step title="Trigger an action">
    Select the action the extractor exposes, for example start or end a **task**. Add a message or metadata if the UI offers those fields.
  </Step>

  <Step title="Track the result">
    Wait for the next extractor check-in, then confirm the action moves from <span class="ui-element">Pending</span> to <span class="ui-element">Running</span>, and then to <span class="ui-element">Succeeded</span>, <span class="ui-element">Failed</span>, or <span class="ui-element">Canceled</span>.
  </Step>
</Steps>

## Configuration

On the <span class="ui-element">Configuration</span> tab, review or update remote configuration keyed by the integration external ID.

## Set up notifications

Receive email notifications when a **task** fails or resumes regular activity, and when there is no activity for a set time.

<Steps>
  <Step title="Open notification settings">
    Open the integration. From the integration menu next to the name, select <span class="ui-element">Edit notifications</span>.
  </Step>

  <Step title="Add subscribers">
    On <span class="ui-element">Subscriptions</span>, select <span class="ui-element">Add users to receive notifications</span> and choose the users who should get email alerts.
  </Step>

  <Step title="Set the inactivity threshold">
    Select <span class="ui-element">Inactivity threshold</span>. Enter how long CDF should wait with no activity before it notifies the error log and subscribers. The value is in minutes (for example `1440`).
  </Step>
</Steps>

## Further reading

* [About Integrations](/cdf/integration/guides/interfaces/about_unified_integrations)
* [Set up an on-premises integration](/cdf/integration/guides/interfaces/set_up_on_premises_integration)
* [Monitor extraction pipelines](/cdf/integration/guides/interfaces/monitor_integrations)