stackdoctor
by lepri89
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_URL | No | Redis connection URL for Redis checks | |
| CELERY_APP | No | Optional: Python path to your Celery app (e.g., myproject.celery:app) to use your app's queues/routes/config | |
| LOG_SOURCES | No | Comma-separated list of log sources: file paths, docker:<container>, or bare container names | |
| LONG_TASK_S | No | Seconds after which a task counts as long-running | 60 |
| DATABASE_URL | No | Postgres connection URL for database checks | |
| LONG_QUERY_S | No | Seconds after which a query counts as long-running | 30 |
| CELERY_QUEUES | No | Comma-separated list of extra queue names to measure | |
| CHECK_TIMEOUT_S | No | Per-check timeout inside diagnose (seconds) | 8 |
| LOG_ERROR_SPIKE | No | Problem lines in 5 minutes that count as a spike | 10 |
| QUEUE_THRESHOLD | No | Messages waiting before a queue counts as a backlog | 100 |
| CHAIN_WINDOW_MIN | No | How far apart (in minutes) cause and effect may be for chaining | 30 |
| EXPECTED_WORKERS | No | Report missing workers if fewer than this number reply (0 = off) | 0 |
| MAX_OUTPUT_CHARS | No | Per-tool response cap in characters (diagnose gets 2×) | 20000 |
| CELERY_BROKER_URL | No | Celery broker URL for inspect and queue length checks | |
| REDIS_MEM_WARN_PCT | No | Percentage of maxmemory that counts as near the limit | 85 |
| STACKDOCTOR_ENV_FILE | No | Path to a .env file to load configuration from. Defaults to .env in the working directory. | |
| CELERY_RESULT_BACKEND | No | Celery result backend URL for failed tasks and task details | |
| CELERY_INSPECT_TIMEOUT_S | No | How long to wait for Celery worker replies (seconds) | 1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues