> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/logging.md).
# Logging
Logging is done with our S3 server access and object-level API activity. We utilize versioning to track changes over time, which allows easy rollback to previous versions. Flosum also uses cross-region replication for geographically separate backups and enhanced availability. We maintain object locks and MFA delete on backup buckets.\
\
Logs are collected through Syslog from multiple instances and tiers, including application, network, and OS events. These logs are then centrally reviewed and analyzed for further insights and actions. Additional logging is available in the AWS Cloud Trail for the tool.\
\
Extensive audit trails record all actions performed by users (login/creation/change/addition/deletion of content, settings, parameterizations, etc.) and on users (creation/change/deletion of users, inclusion/change/deletion of access profiles, password changes, etc.).
---
# 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.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/logging.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.