Skip to content

Default filters

Default filters are a preset combination of filters, sorting, and full-text search that LogMan.io Alerts applies to the ticket list. They define what the user sees when opening the ticket list for the first time, and serve as the reference point for the Reset filters action.

Default filters are stored in Library as /Alerts/List/default.json.

File Structure

The default.json file contains three optional top-level keys:

  • filters – advanced filters applied to the ticket list
  • sort – initial sorting of the ticket list
  • search – full-text search pre-filled in the search field

Any of these keys can be omitted. If the file is empty or missing entirely, no default filters are applied.

Default Filters Declaration

{
  "filters": {
    "status": ["open", "triaged"]
  },
  "sort": {
    "type": "desc"
  },
  "search": "Ticket-01"
}

filters

A map of field names to one or more values. Each entry is rendered as a filter pill above the table, and the corresponding query is added to the ticket list request.

Each value must be an array of strings.

In the above example:

  • the ticket list is filtered by status with two values — open and triaged.

Multiple fields can be combined:

{
  "filters": {
    "status": ["open", "triaged"],
    "severity": ["high", "critical"]
  }
}

sort

A map of field names to a sort direction. Field names are application-specific (e.g. severity, ticket_id, type, status, responder, _m, _c).

Supported directions:

  • asc — ascending
  • desc — descending

Only one sort direction per field is allowed.

In the above example:

  • the ticket list is sorted by type in descending order.

Advanced sorting can combine multiple fields:

{
  "sort": {
    "type": "desc",
    "_c": "asc"
  }
}

A string pre-filled into the search field. It is applied to the same full-text search as if the user had typed it manually.

{
  "search": "Ticket-01"
}

When Default Filters Are Applied

Default filters are applied automatically only when the user opens the ticket list with no filters, sorting, or search set by the user (typically on the first visit). Once the user has modified any of these, the defaults are no longer reapplied automatically — this preserves the user's current view across navigation.

To return to the default filters, use the Reset filters button in the ticket list header.

Reset filters covers several cases

  • Defaults are not visible — the user previously modified filters, and the table does not reflect the current default.json. Clicking Reset filters restores the defaults.
  • Defaults were changed in Library — the default.json file was updated, but the table still shows the old state. Clicking Reset filters applies the new defaults.
  • User added their own filters — the user wants to go back to the view defined in Library. Clicking Reset filters discards the user-defined filters, sorting, and search, and reapplies the defaults.

If default.json is empty or missing, Reset filters simply clears all filters, sorting, and search, and returns the table to page 1.

Disabling Default Filters

To disable default filters without deleting the default.json file, disable the disabled file in the Library.

Warning

Disabling default filters does not affect filters already present in the URL or the user's session — only the automatic application of defaults on the first visit is suppressed. Filters set by users are not affected by this change.