> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/monitoring-and-alarms/monitoring-alarms-view-events.md).

# View Events

You can view the various events generating for audit purpose by OpenStack Ceilometer.

You can search for events based on advanced search criteria such as event types and/or a date range that can be entered in the from and to fields.

{% hint style="info" %}
**Note**

You must be an administrator to perform this operation.
{% endhint %}

To view OpenStack events, follow the steps given below.

1. Log in to Clarity.
2. Click Events and Alarms in the left pane.
3. Click the Events tab to view the Events. 
Click Advanced Search options and enter the one or more search criteria to filter the required events.
4. Click the column, for example Event Type, to sort event data on the column.

You can navigate between pages to view the events. The events are listed in a chronological order starting with the most recent events.

Refer to [OpenStack Ceilometer documentation](https://docs.openstack.org/ceilometer/pike/admin/telemetry-events.html) for further details on events.


---

# 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.platform9.com/managed-openstack/monitoring-and-alarms/monitoring-alarms-view-events.md?ask=<question>&goal=<user_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.