> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/events-postgresql.md).
# Events
The Events tab displays a complete, chronological audit trail of all lifecycle and operational activities performed on your database service. Each entry records the action taken, the username responsible, and the exact date and time.
***
## What actions appear in the Events log?
The Events tab records all significant service lifecycle changes, including:
* Service created, started, or stopped
* Switchover and switchback operations
* Failover and failback operations
* Storage resize operations
* DR instance addition or deletion
For **cloned services**, the following additional details are captured for each refresh:
| Detail | Description |
| -------------- | ------------------------------------------------------- |
| User | The user who initiated the refresh |
| Refresh method | Whether the refresh used a snapshot or PITR |
| Scheduled | Whether the refresh was scheduled or triggered manually |
| Date and time | The exact timestamp of the refresh |
Figure 1 — Events tab
---
# 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.tessell.com/tessell/database-engines/tessell-for-postgresql/db-services/readme-postgresql/homepage-postgresql/events-postgresql.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.
