> For the complete documentation index, see [llms.txt](https://brixxbox.gitbook.io/brixxbox-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brixxbox.gitbook.io/brixxbox-documentation/client-api-reference/functions/logadd.md).

# logAdd

The brixxbox offers a client-side event log. Events like save/delete record, data validation messages, internal events etc. will be logged. In addition, the log can be accessed through brixxApi. The log view is located in the side bar. It will be shown in an extra tab page (only if data is available). Per default only entries for the current brixxApi Object (and its children) will be visible.

### Parameters

Parameters can be passed as a json object.

1. text: the actual log text. If this value is missing no entry will be generated.
2. context: This should be set to a plausible group-criteria (e.g. “save” for record saved. “validate” for data validation). This value can also be used to remove the complete group from the log (see example).
3. status: Status can have the following values “info”, “success”, “warning”, “danger” or “error”. The log entry will get its color set accordingly. “danger” and “error” are interchangeable.
4. info: Additional info can be set. If empty its value will reflect the app title of the brixxApi object.
5. recordId: If not passed as a parameter the value will be set to record-ID of the brixxApi object (brixxApi.record.id).

### Example Usages

```javascript
brixxApi.logAdd({context: "GroupCriteria", status: "info", text: "Lorem ipsum dolor sit amet, consectetur adipisici elit"})
```

To remove an existing context from the log for the current brixxApi object **logReset** is available:

```javascript
brixxApi.logReset("GroupCriteria")
```


---

# 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 dynamically by asking a question.

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

```
GET https://brixxbox.gitbook.io/brixxbox-documentation/client-api-reference/functions/logadd.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.