Keep your Data Flowing

0 of 5 lessons complete (0%)

Lesson 1: What’s built in to FME Flow

You don’t have access to this lesson

Please register or sign in to access the course content.

FME Flow has built in features for analyzing how the jobs are performing, including the Jobs tab, the Analytics tab, and Dashboards.

Jobs Tab:

The Jobs tab lets you view which jobs are Completed, Queued, and Running. However, on an active system running tens of thousands of jobs a day, it’s hard to see any trend. Making it difficult to explain when or why those failures are happening.


The image above shows a standard FME Flow Jobs tab showing the status of completed jobs.

FME Dashboards:

The built-in dashboards give visibility into what’s failing and how many jobs have completed, among other things. However, the process has to be scheduled within FME, and it won’t tell you if an engine or core has dropped out of the cluster.

The image above shows a standard FME Flow dashboard tracking total job runs by day. In this example, an engine rebooted and didn’t rejoin the cluster properly. It’s not a common failure mode, but it happens. Monitoring total completed jobs per day in ArcGIS Monitor turns an unexpectedly low count into an alert, flagging the issue for system admins before it’s noticed some other way.


Analytics Tab:

The Analytics tab is genuinely useful, giving you a read on how many jobs your system is handling over a given timeframe. However, it doesn’t visualize failure trends, and you can’t filter it by workbench name or engine host.

The image above shows a standard FME Flow Analytics tab showing the number of completed jobs for the last 4 hours.

All of the tools above ship with FME Flow, and each one is useful in its own right. They’re all part of getting real visibility into how FME Flow is handling jobs. However, all of the tools above have one point of failure from an observability aspect – they rely on FME Flow to run.

Imagine a situation of major issues, for example, none of the engines are able to run. If that’s the case, then FME is unable to execute jobs, and is therefore unable to alert you to that important fact.

In this case, it’s important to have another system, that is able to monitor and execute queries – alerting you to the system issues.

FME Flow 2026.3 has a new feature that allows you connect AI that supports MCP to its logging mechanism. This is a huge step forward in understanding what is failing, allowing you to ask questions about what is erroring and why.

The rest of this course covers how to extend that visibility using ArcGIS Enterprise Dashboards, ArcGIS Server query layers, and ArcGIS Monitor.