> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/controlbee-docs/en/checken/monitoring.md). # Monitoring Monitor KPIs to test performance against the objectives The KPIs are monitored to see whether the organization's performance is in line with the objectives. An example of a monitoring activity is an annual program.
Uitleg monitoring
## Create monitoring When creating the monitoring, the user gives the monitoring a name and enters the start date and end date.
Aanmaken monitoring
Aanmaken en koppelen acties onder KPI monitoring
## Link KPIs to the monitoring KPIs can be linked to the monitoring. Select existing KPIs and click 'link'; linking multiple KPIs at once is also possible. You can also create a new KPI by clicking 'add'. An extensive explanation of creating KPIs can be found in [KPIs](/controlbee-docs/en/plannen/kpis.md).
KPI’s koppelen aan de monitoring
## Enter KPI score and value For each KPI, the value is entered and the score is selected. In addition, a description can be given of the monitoring activity. Click 'save' to save the changes.
KPI-score en waarde invullen
## Create and link actions under KPI monitoring When actions arise from the monitoring activity, it is possible to create them directly or link an existing action. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.controlbee.nl/controlbee-docs/en/checken/monitoring.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.