> 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/menu_-_administration/application_settings_-_watchdog.md).

# Application settings… - Watchdog

Boomerang system often monitors crucial or critical parameters so it is of highest importance to be sure it works correctly. Using a built-in watchdog functionality, all Boomerang services can be monitored by B2WEB server. At start, stop or contact lost a message will be sent via email or SMS.

The Watchdog settings define the monitoring B2WEB server.

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

Select ‘Use Watchdog’ to start using watchdog.

Enter the watchdog receiver page URL into ‘URL’ field. For example, if B2WEB runs on the same computer then enter ‘<http://localhost/WatchdogReceiver.aspx’>.

Enter site name. The same name must be used during watchdog setup on B2WEB server.

For watchdog to operate correctly, the settings must be adjusted on B2WEB server as described in SG419-0001-B2 ‘ICU Watchdog User Guide’.


---

# 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/menu_-_administration/application_settings_-_watchdog.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.
