> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-2-system-administrator-manual/boomerang_system.md).

# Boomerang System

The ICU Scandinavia Boomerang is a flexible, distributed client-server monitoring system. Its simplified structure is shown below.

![](https://800956157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvyGt5xgoAU3kZytuvW1J%2Fuploads%2Fgit-blob-3a4d35a36f2ee78c7c92c915faaddd30db267fc2%2Fimage227.png?alt=media)

Figure 1 Boomerang 2 system diagram

The Boomerang system collects the measurements from its sensors, saves the readings into its database, checks if the values read are within the user defined limits and generates alarms if they are outside the boundaries. Alarms are also generated in case of system malfunction like lack of readings or system infrastructure problems.

The system status can be presented in different ways including web page view and the alarms are distributed using user defined methods like email or SMS.

The active access to the system requires user rights which can have different levels defined by the system administrator. Two user access methods are provided, using Boomerang client application or via a web interface.

The system creates database backups automatically to protect the data collected. System reports and data exports can be generated on request or automatically.


---

# 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://help.boomerang3.com/boomerang-2-system-administrator-manual/boomerang_system.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.
