> For the complete documentation index, see [llms.txt](https://aurelia-1.gitbook.io/v1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aurelia-1.gitbook.io/v1-docs/aurelia-packages/store/defining-custom-loglevels.md).

# Defining custom loglevels

The Aurelia Store plugin provides various logging features to help you understand the flow of actions and state changes. You can customize the log levels used for different features using the `logDefinitions` option during plugin registration.

```typescript
// main.ts
import { Aurelia } from 'aurelia-framework';
import { initialState } from './state';

export function configure(aurelia: Aurelia) {
  aurelia.use.standardConfiguration().feature('resources');

  aurelia.use.plugin('aurelia-store', {
    initialState,
    logDispatchedActions: true, // Enable logging of dispatched actions
    logDefinitions: {
      dispatchedActions: 'debug', // Log dispatched actions with 'debug' level
      performanceLog: 'info', // Log performance info with 'info' level
      devToolsStatus: 'warn', // Log DevTools status with 'warn' level
    },
  });

  aurelia.start().then(() => aurelia.setRoot());
}
```

**Available Log Levels:**

You can use the following standard log levels:

* `'log'`
* `'debug'`
* `'info'`
* `'warn'`
* `'error'`

**Customizable Log Features:**

You can control the log levels for the following features:

* **`dispatchedActions`:** Logs information about dispatched actions (name, parameters).
* **`performanceLog`:** Logs performance measurements (if `measurePerformance` is enabled).
* **`devToolsStatus`:** Logs the status of the Redux DevTools integration (connected, disconnected).

**Example:**

In the example above, dispatched actions will be logged using `console.debug`, performance information will be logged using `console.info`, and DevTools status will be logged using `console.warn`.

{% hint style="info" %}
The `logDispatchedActions` option must be set to `true` to enable logging of dispatched actions, regardless of the `logDefinitions` setting.
{% endhint %}


---

# 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://aurelia-1.gitbook.io/v1-docs/aurelia-packages/store/defining-custom-loglevels.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.