> For the complete documentation index, see [llms.txt](https://revhero.gitbook.io/revhero-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://revhero.gitbook.io/revhero-docs/automation/event-log/filtering-and-search.md). # Filtering and search How to narrow tens of thousands of Event Log lines down to the few that answer your question. An active property builds up tens of thousands of [Event Log](/revhero-docs/automation/event-log.md) lines. Finding the line you need is a filtering problem, not a scrolling problem. If you remember only 1 combination, remember this order: **date range, then Source, then Status**. It answers most questions anyone will ask you. ![Filters narrowing the Event Log to a few lines](https://272652298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnzEa7YGji6t92Mfc0ZJ1%2Fuploads%2Fgit-blob-48e7814768f809383d169b4ed1f0f0a5028f86b2%2Ffilters-narrow-the-log.svg?alt=media) *Date range first, then Source, then Status — and tens of thousands of lines become the few that answer your question.* ## The filter row The filters sit above the table. They apply together, so each filter you add narrows the result further. Active filters appear as chips, and you can remove each chip on its own. **Reset filters** clears them all and returns to the default of the last 7 days. | Filter | Default | Notes | | ---------------------- | ----------- | -------------------------------------------------------------------------------------------------------------- | | **Date range** | Last 7 days | Quick picks for 24 hours, 7, 30 and 90 days, plus a custom range | | **Source** | All | Manual, Integration, System and others, depending on what runs on your property | | **Action Type** | All | RATES, LOS, STOP SALES, RMS and the rest. See [Event types](/revhero-docs/automation/event-log/event-types.md) | | **Status** | All | Narrows to the lines that went through, or the lines that did not | | **User** | All | Only useful when Source is set to Manual | | **Stay date / period** | Any | The date the change *applied to*, not the date it was made | | **Room type** | All | Your published room types | | **Integration** | All | Becomes available once Source is set to Integration | {% hint style="info" %} **Date range** and **Stay date** ask 2 different questions, and they work independently. A rate you send this morning for next December matches a "last 24 hours" date range *and* a December stay-date filter. Confusing the 2 filters is the most common reason a search returns nothing. {% endhint %} ## Free-text search The search box matches the reason field and the notes field at the same time. Use it to find every line with a particular rejection message, or every line somebody annotated during a busy week. The search matches fragments of words, so a short word matches too many lines. Do 2 things instead: 1. Put the phrase in quotation marks, for example `"rate plan inactive"`. 2. Narrow the date range at the same time. ## Built-in views The presets put you on a useful set of lines before you touch any control. These are the ones you will use most. | Preset | What it shows | | -------------------- | ----------------------------------------------------- | | **Today's activity** | Last 24 hours, everything | | **Failures only** | Last 7 days, only the changes that did not go through | | **Manual sends** | Last 7 days, Source = Manual, Action = RATES | Build any other view yourself, then bookmark it. ## Bookmarking and sharing a view Your filter choices are held in the page address. You can therefore bookmark a filtered view and reopen it exactly as you left it. You can also paste the address to a colleague. This is quicker than a screenshot. It also stays accurate as new lines arrive, which a screenshot does not. To hand over an investigation, send the link. ## The combinations worth memorising | Your question | The filters to set | | -------------------------------------- | --------------------------------------------------------------- | | Did rates go out yesterday? | Last 24 hours · Source = Manual · Action = RATES | | What failed this week and needs me? | Last 7 days · Status set to the changes that did not go through | | Who sent rates for next weekend? | Stay date = that weekend · Source = Manual · Action = RATES | | Are my connections syncing? | Last 24 hours · Source = Integration · Action = SYNC | | What did this person do last week? | Last 7 days · Source = Manual · User = the person | | What configuration changed this month? | Last 30 days · Action = TOOLS, BOARD, POLICY, COMMISSION, SPO | ## Filter in the right order 1. **Narrow the date range first.** 2. **Then set the Source.** 3. **Then refine by Status.** If you start from a user or a stay date, you usually end up with too few lines to see a pattern. Date, then source, then status keeps enough context for you to recognise what normal looks like. Results are ordered newest first. Click any column title to sort by that column. The count above the table tells you how many lines matched. That count is a useful check in itself. If a property normally records 50 sends a day and shows 5, the count is your finding. ## Downloading what you filtered **Download** exports the lines you have filtered to, as a CSV file or an Excel file. The file contains every column, even the columns hidden on screen. Filters narrow rows, not columns. Filter first and download second. That is always faster than exporting everything and cutting it down in a spreadsheet, and the file cannot go out of date while you work on it. Exporting is not available to every role. If **Download** is greyed out, ask an administrator at your property for download access. ## If something looks wrong | What you see | Usual cause | What to do | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- | | A filter chip will not clear when you click the cross | The page is holding an old view | Reload the page | | Your filters are in the address, but the page shows everything | Your browser or your network removed the query from the link | Apply the filters again on the page | | The date picker refuses a future date | Events happen in the past, so a future *event* date means nothing | Use **Stay date** for future stays | | Your search matches far too many lines | The search matched a fragment of a short word | Put the phrase in quotation marks, and narrow the dates | | Nothing matches at all | There are genuinely no lines, or 2 filters cannot both be true — for example Source = Manual with an integration selected | Reset the filters, then rebuild them 1 control at a time | | The download has columns you did not filter on | Filters narrow rows, not columns | This is expected | ## Related * [Event Log](/revhero-docs/automation/event-log.md) * [Event types](/revhero-docs/automation/event-log/event-types.md) — the values behind Source and Action Type * [Investigating a rate send](/revhero-docs/automation/event-log/investigating-a-rate-send.md) *** **Was this page helpful?** If something here is wrong, unclear or missing, email [support@revhero.com](mailto:support@revhero.com?subject=Manual%20feedback%20%5Ben%5D%20event-log%2Ffiltering-and-search.md) and quote this page: `event-log/filtering-and-search.md`. Say what you expected to find — that is the part we can fix.