> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/appcademy/appfarm-professional/security-and-operations/debugging-and-app-health.md).

# Debugging and App Health

The ability to debug is what differentiates a professional from a beginner. But it is difficult without the correct tools.

Appfarm comes with Debug Tools for both Apps and Services. It also comes with a tool inside Appfarm Create for validating your App setup: *App Health*.

### Testing and debugging Apps: Debug Tool and App Health

This article summarizes how to test and debug your Apps:

* [Test and debug](/how-to/security-testing-and-deployment/test-and-debug.md)

You may also jump straight to our articles on the Developer tool and App Health:

* [Developer Tools](/reference/appfarm-client/developer-tools-for-apps.md)
* [App Health](/reference/apps/app-health.md)

### Services

You can test, debug, and monitor [services](/reference/services.md) using [Developer tools for services](/reference/appfarm-client/developer-tools-for-services.md) and [Logs](/reference/operations/logs.md).


---

# 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://docs.appfarm.io/appcademy/appfarm-professional/security-and-operations/debugging-and-app-health.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.