---
schema_version: "1"
id: 08ab599c0407805fe8a792145c47fa1d9a309590e15a8cb4f0e7255648e5006b
title: API Functional Monitoring in Anypoint Monitoring
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-functional-monitoring/afm-in-anypoint-platform.md
canonical_url: https://docs.mulesoft.com/api-functional-monitoring/afm-in-anypoint-platform
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5564b3312f97b34e16f1d1e4ce9f59cd5a9bfd68ec0ad91da74e9344bb33e1f9
description: MuleSoft Documentation Site
latest: true
---
---
product: API Functional Monitoring
---

# API Functional Monitoring in Anypoint Monitoring

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

API Functional Monitoring enables you to monitor responses to requests sent to API resources at
their endpoints. You monitor APIs by accessing the **Functional Monitoring** section of Anypoint
Monitoring, which you select from the home page of Anypoint Platform.

The **Functional Monitoring** section contains tools for creating and editing monitors.
Additionally, you can upload custom test suites written in BAT, a Behavior Driven Development (BDD)
language.

The following image illustrates the components of a monitor:

![afm ui overview a new](/mulesoft/current/en-us/api-functional-monitoring/_images/afm-ui-overview-a-new.png)

A monitor includes a test and one or more schedules for running tests.

A monitor test includes the following:

- The endpoints to verify

- Optional assertions to verify at the endpoints (for example, a 200 status code)

- Optional HTTP headers to include when sending requests to the endpoints

- Optional tools, such as SumoLogic and Slack, used to send test reports

A monitor test schedule includes the following:

- The location from which to run the test

  Locations can be public or private. For details, see
  [Monitoring the Endpoints of Public APIs](https://docs.mulesoft.com/api-functional-monitoring/afm-monitoring-public-apis) and
  [Monitoring the Endpoints of Private APIs](https://docs.mulesoft.com/api-functional-monitoring/afm-monitoring-private-apis).

- The time interval between tests

The Functional Monitoring page with a monitor selected is shown in the following image:

![AFM page showing a selected monitor’s details](/mulesoft/current/en-us/api-functional-monitoring/_images/afm-ui-test-versions-and-schedules-new.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Duration of the test for the selected monitor.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>Daily average response time in milliseconds of all tests to all endpoints. The colors in each bar indicate the breakdown of the average time for each of the steps in a test. Hover over the bar to see the breakdown details.</td></tr><tr><td><i data-value="3"></i><b>3</b></td><td>Schedule information, including when the next run is scheduled, the schedule interval, and information about the location where the tests are scheduled to run.</td></tr><tr><td><i data-value="4"></i><b>4</b></td><td>Details about the previous execution, including the method executed and the assertions.</td></tr><tr><td><i data-value="5"></i><b>5</b></td><td>A summary list of the last few executions.</td></tr><tr><td><i data-value="6"></i><b>6</b></td><td>Option to add schedules to the selected monitor.</td></tr></tbody></table>

The bar graph shows the daily average response time in milliseconds of all tests to all endpoints.
The colors in each bar indicate the average time for each of the steps in a test. Hover over the bar
to see the details.

## See Also

- [Creating Monitors](https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor)

- [Uploading Monitors](https://docs.mulesoft.com/api-functional-monitoring/afm-upload-monitor)