The steps outlined below are for ArcGIS Monitor 2026 and newer. The ability to execute custom SQL queries on a registered database was added in the 2026 release. If you’re on a release older than 2026 but newer than 2024.1, you can still query the data by pointing a Check Service observer at an ArcGIS Server service built on the query layers outlined earlier in this course. More on that approach here:
While logged in as an Administrator in ArcGIS Monitor, we’ll register the FME Flow database by navigating to the Monitoring tab and clicking “Register component” in the upper left corner.
Choose the machine with the Monitor Agent that has access to the FME Flow database.
Choose the database type of your FME Flow database. In the example below, we’re choosing PostgreSQL, since that’s the default database for FME Flow.
Provide a name, description, and label for the component.
This adds the FME Flow database as a registered component in ArcGIS Monitor, alongside any other databases you’ve already registered.
Click the newly added FME Flow database component’s name to view detailed information about the database, including its version, number of connections, and similar stats.
In the upper right corner, click the Observers tab.
We’ll walk through adding the “count failed jobs” query below. You can add the rest of the queries the same way, based on your own configuration.
Note: ArcGIS Monitor’s Database Query observer requires a query that returns a single numeric value. This is why we’re creating a separate observer for each query, rather than combining them.
The example query below counts the number of failed jobs over the last minute in the fme_job_history table, filtering to status IDs 9 and 10 (FAILURE), for a SQL Server database.
SELECT COUNT(*)
FROM fme_job_history
WHERE job_status IN (9, 10)
AND date_finished >= DATEADD(MINUTE, -1, GETDATE());
If you’d like the PostgreSQL versions of the queries, check out our GitHub repository.
Click “Add observer” in the upper left. Choose “Database query” in the upper left and click next.
Provide a name and description.
Set your interval to one minute and paste your query into the “Query” window.
Click “Test” and then “Add Observer”.
Configuring monitor Alerts:
Now that the queries are added and ArcGIS Monitor is pulling in data from the FME Flow database, you can configure automated alert rules to notify admins when performance breaches defined thresholds. For example, you can trigger email notifications if:
- the queued job count exceeds 15.
- if the number of active engines drops below 2.
To set up custom notification rules and triggers for your environment, check out the ArcGIS Monitor Alert Rules Documentation
Course Conclusion:
By bridging FME Flow with ArcGIS Enterprise and ArcGIS Monitor, you’ve transformed unreadable, scattered log streams into a proactive, real-time command center. Decoupling your monitoring infrastructure from FME Flow ensures complete operational visibility—catching dropped engines and job failures automatically, even if the primary server goes offline. With real-time dashboards and automated alerts now protecting your spatial pipelines, you can stop reacting to broken workflows and start managing your enterprise infrastructure with confidence. Keep your data flowing!
Have questions about tailoring this setup to your enterprise environment? Reach out to Spatialty! Our team is here to help you design, deploy, and troubleshoot your spatial data observability stack, visit spatialty.com to connect.