> For the complete documentation index, see [llms.txt](https://docs.skyledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyledge.com/knowledge-base/articles/event-stream-filtering.md).

# Event Stream Filtering

The event stream filtering feature, helps you manage information and extract meaningful insights from the event data packets in various assets, event types or different importance statuses. It involves the use of rules and conditions to sort, prioritize, or manipulate information to achieve specific goals or meet particular requirements

With a few clicks of the mouse, you can

* Select between live and cleared events.
* Displaying selected importance levels
* Filter the events by time or date
* Filter the events by event type
* Drill further into the event attributes and filter on a subset data point

![](https://lh6.googleusercontent.com/ZCca4_r4Mz1W3EbjNIVUcF-hTAFaRq2d-aNrn_PYsYHp7PCnUQMSa4pSw2HX6fz76v2jUTXsZtUadxWsi240K8bDGqOCLZ5wY6tD6Tkmr_j8um3qLfK8kBZ9HIWPw7grZVf6Mrj4pt6zlYl1DskWWdA)

{% embed url="<https://youtu.be/_FFEKB5reY8>" %}

<details>

<summary>Tags</summary>

The event stream filtering feature, helps you manage information and extract meaningful insights from the event data packets in various assets, event types or different importance statuses. It involves the use of rules and conditions to sort, prioritize, or manipulate information to achieve specific goals or meet particular requirements

time, date, importance, events, attribute

</details>


---

# 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.skyledge.com/knowledge-base/articles/event-stream-filtering.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.
