# Searching

BugSplat provides powerful searching, filtering, and grouping tools that help users better understand the various intricacies of their crash data. Users can build complex queries via the BugSplat search controls, share the results with co-workers, and export the results for use in other tools.

Need to isolate all crashes that happened before a certain date? Looking for any crash that contains a specific function anywhere in the call stack? Want to group crashes based on their IP Address? BugSplat can do it all! Crafting a search to isolate the crash data you need is straightforward and intuitive.

BugSpat's data can also be searched and filtered directly via our web-services [APIs](/introduction/development/web-services/paging-filtering-and-grouping.md).

{% content-ref url="/pages/-MebBB5qGLH01QJXM2uu" %}
[Table Filtering](/introduction/development/searching/search.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mg6Z4RN3VvPkNLdR\_yt" %}
[Table Grouping](/introduction/development/searching/grouping.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bugsplat.com/introduction/development/searching.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
