> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/feature-guides/data-management/snapshots.md). # Snapshots Utilize Snapshots in Bindplane Snapshots provide a way to view logs, metrics, and traces recently collected by a collector. ## Viewing Snapshots can be viewed by clicking the `View Recent Telemetry` button found below the details table on a collector page. ### Logs
Bindplane docs - Snapshots - image 1
**Metrics**
Bindplane docs - Snapshots - image 2
If no metrics are available, it's possible none have been collected yet. For example, if a collector has been running for 30 seconds and collecting metrics with a 60-second interval, it won't have any recent metrics to show. ### Limitations For recent telemetry to be available for a collector, there are two requirements: 1. The collector must be connected to Bindplane 2. The collector must be using a managed configuration --- # 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.bindplane.com/feature-guides/data-management/snapshots.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.