> For the complete documentation index, see [llms.txt](https://developer.textmaster.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.textmaster.com/integrations/akeneo/monitoring.md).
# Monitoring
Learn how to monitor your translation projects sent to TextMaster.
Monitoring the progress of your translation projects and their respective products sent to TextMaster is conveniently manageable directly from either an Akeneo view or the middleware's dashboard.
## **Create a view**
To monitor translation status per product and to see if they've already been sent, you can create a view by following these steps:
1. Press "Create View" on the product grid page
2. Name this new view
3. Modify the columns:
* Add the Translation attributes
* Find them
* Drag them to the right columns
* Then press "Apply"
4. Click on the three dots button and save the view
## Middleware's dashboard
To monitor the overall translation status and synchronization between TextMaster and your Akeneo instance, you can use your personal dashboard your project manager provided you during the configuration phase.
---
# 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://developer.textmaster.com/integrations/akeneo/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.
