> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/operations-and-features/overview-and-navigation/devices/stifler-server.md).
# StifleR Server
## StifleR Leaders
The StifleR Leaders section contains several subsections which filter the various types of StifleR clients functioning as leaders.
### All Leader Roles
The list of leaders is a real-time reporting of all the StifleR leaders. Select the below subsections to filter on Red, Blue, or Green leaders.
## Beacons
The Beacons page displays a list and status of all of the StifleR Beacon servers reporting into the StifleR server.
## Performance
The Performance page provides an overview of the current performance of the StifleR server. Some metrics include Memory and CPU usage, Client connections, Client counts, and Download jobs.
## [Templates](/stifler/operations-and-features/overview-and-navigation/devices/stifler-server/templates-detail.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://documentation.2pintsoftware.com/stifler/operations-and-features/overview-and-navigation/devices/stifler-server.md?ask=&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.
