> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/system/clocksync.md). # clocksync Explanation The clocksync NDM is a system NDM designed to detect situations where a flow source is sending flows to Netography with timestamps that are out of sync with Netography’s clock. Bad timesta **Explanation** The clocksync NDM is a system NDM designed to detect situations where a flow source is sending flows to Netography with timestamps that are out of sync with Netography’s clock. Bad timestamps can make network events hard to correlate with each other. **What to Look For** Examine the configuration of the device sending flows to determine if its clock is set properly. Also check network time settings on the device to make sure that the device clock is kept in sync with a valid network time server. --- # 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.fusion.vectra.ai/detection-models/library/system/clocksync.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.