# KPI Monitoring ## General KPI monitoring Ylem provides an extremely powerful way of calculating various KPIs from commonly known metrics (ARR, MRR, LTV, etc) to custom ones, that you can define on your own. Metrics can be calculated in the [Query](https://docs.ylem.co/pipelines/tasks-ip/query) itself or using an [Aggregator](https://docs.ylem.co/pipelines/tasks-ip/aggregator). Typically the result is compared with a certain target and sent as a notification to **Slack** or channels afterward.

## AVG, SUM, MIN, MAX, and other aggregated monitoring The pipeline above can be used for monitoring different KPIs represented by mathematical functions such as average values, number of items, minimal and maximal values, etc. More information about using them in [Condition](https://docs.ylem.co/pipelines/tasks-ip/condition) and [Aggregator](https://docs.ylem.co/pipelines/tasks-ip/aggregator) tasks can be found on a [special separate page](https://docs.ylem.co/pipelines/mathematical-functions). ## ARR Monitoring

## MRR monitoring

## Stream sales or other revenue KPIs Sales or other Revenue teams are the most KPI-driven in an organization. Ylem allows easy monitoring of their KPIs, comparing with a target, and taking different actions depending on whether it is already achieved or not yet:

## Monitor average value per customer Ylem allows easy monitoring of average values (amounts, orders, bank transfers, contract values) per customer. As an example the following pipeline represents the calculation of an average amount per customer and taking actions for different sizes of it:

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ylem.co/use-cases/functional-use-cases/kpi-monitoring.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.