> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/workflows/observability.md).
# Observability
### Data sync observability
To monitor the health, performance, and status of a data sync, navigate to the Integrations page.
Click on an integration row to expand it and view metrics on **fetch time** (ie. data being ingested into Violet) and **data transfer time** (ie. data being synced to a destination tool like NetSuite or Manufacturo):
Data ingestion metrics
Data sync metrics
Monitor details of sync progress and any potential warnings or errors in the **integration timeline:**
View progress and errors in the integration timeline
View details of sync errors and warnings
And subscribe to receive email summaries of sync progress (or just warnings and errors):
Subscribe to email summaries of sync progress or failures
---
# 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.violetlabs.com/features/workflows/observability.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.
