- 4 minutes to read

Nodinite Monitoring of the Data Factory service and related Pipelines in Azure

Gain full visibility and control over your Azure Data Factory and pipelines with Nodinite. This page shows you how to monitor Data Factory resources, receive proactive alerts, and take action, without ever needing direct Azure Portal access.

  • ✅ Get alerts for Data Factory and pipeline issues through Alarm Plugins
  • ✅ Monitor and manage thresholds for Data Factory pipeline runs
  • ✅ Access actionable details and Remote Actions from a single interface

Nodinite helps your integration and support teams detect, analyze, and resolve issues quickly. Share access to Data Factory resources securely using Role-based Monitor Views. This approach streamlines troubleshooting, reduces risk, and keeps your business running smoothly. The Managing Data Factory page details the Remote Actions.

Azure Data Factory and Pipelines as Resources in a Monitor View
Example: List of monitored Data Factory resources in a Nodinite Monitor View.

How Data Factory Monitoring Works

The Nodinite Azure Agent reads the pipeline runs within the lookback period through the Azure REST API, compares the execution count and duration with your thresholds, and reports the state to the Nodinite Monitoring Service. State changes reach your team through Alarm Plugins.

graph LR DF["fa:fa-industry-windows Data Factory
Pipeline runs"] -->|"REST API"| AG["fa:fa-monitor-waveform Azure Agent"] AG --> OK["fa:fa-check OK
Within thresholds"] AG --> WA["fa:fa-triangle-exclamation Warning
Warning threshold breached"] AG --> ER["fa:fa-xmark Error
Error threshold breached"] AG --> UN["fa:fa-ban Unavailable
Cannot evaluate"] WA --> AP["fa:fa-bell Alarm Plugins"] ER --> AP ER --> RA["fa:fa-edit Edit thresholds"] style OK fill:#93d16d style WA fill:#FFD525 style ER fill:#c33d34,color:#fff style UN fill:#c33d34,color:#fff style AG fill:#2678BD,color:#fff

Diagram: The Azure Agent evaluates each pipeline into OK (green), Warning (yellow), or Error and Unavailable (red) based on run count and duration; Warning and Error raise alerts, and you tune thresholds with a Remote Action.

Monitoring Features

  • State Evaluation – Nodinite evaluates state according to pre-defined policy.

    If Nodinite can't check your Data Factory items' state, chances are no one else can use them either.

  • Automatic Discovery – The Nodinite Azure Agent uses the Azure REST API to discover Data Factory resources automatically.
  • Category-based monitoring – Nodinite groups monitored Resources by Categories.
  • Role-based access – Share access to individual items with Users through one or more role-based Monitor Views.

State evaluation

Nodinite presents each Data Factory and related pipeline as a Resource. For example, if you have three Data Factories with two pipelines each, Nodinite displays nine resources.

  • The Resources name matches the deployed Data Factory name.
  • Monitored Data Factory resources belong to the 'Data Factory' Category.
  • The Application name uses the pattern: Configuration name/Resource Group Name.

Many other Azure-related Categories exist. See the Azure Logging and Monitoring Overview.

Each item (presented as a Resource) evaluates with a state (OK, Warning, Error, Unavailable). Override the evaluation for any Nodinite Resource with the Expected State option. Enable Data Factory monitoring in the agent Configuration.

Data Factory

For Data Factory Resources, Nodinite evaluates state as follows:

State Status Description Actions
🚫 Unavailable Resource not available
  • Nodinite cannot evaluate the 'Data Factory' due to network or security issues
Review prerequisites
❌ Error Error threshold breached Not implemented -
⚠️ Warning Warning threshold breached Not implemented -
✅ OK Within user-defined thresholds Details

Data Factory Pipeline

For Data Factory Pipeline Resources, Nodinite evaluates state as follows:

State Status Description Actions
🚫 Unavailable Resource not available
  • Nodinite cannot evaluate the 'Data Factory Pipeline' due to network or security issues
Review prerequisites
❌ Error Error threshold breached Within the lookback period, one or more Pipeline runs:
  • Did not run the minimum expected number of times
  • Ran more times than the maximum expected number of times
  • Took too long to execute according to user-defined threshold
Edit
⚠️ Warning Warning threshold breached Within the lookback period, one or more Pipeline runs:
  • Did not run the minimum expected number of times
  • Ran more times than the maximum expected number of times
  • Took too long to execute according to user-defined threshold
Edit
✅ OK Within user-defined thresholds Details

The minimum execution count works like Non-Events Monitoring: a pipeline that stops running on schedule raises an alert even though nothing failed. When the state is Unavailable, check the Azure rights of the App Registration and the firewall settings in the Prerequisites.


Alert history for Data Factory

Analyze the alert history for Data Factory resources in Nodinite. When you troubleshoot, search for historical state changes for any time span, either for all Data Factories or for individual resources. See the Add or manage Monitor View page and the Resource State History user guide for more details.

Search Resource history
Search for alert history for all resources in the Monitor View
Search for alert history for all resources in the Monitor View
Alert history for the selected Data Factory item
Alert history for the selected Data Factory item

Frequently asked questions

Use the Troubleshooting guide to find answers to common questions and known issues.

Next Steps