Create, manage, and run Unpage agents
agent
command provides functionality to create, manage, and run agents that analyze incidents and alerts, leveraging the infrastructure knowledge graph and LLM capabilities.
Command | Description |
---|---|
create | Create a new agent configuration file and open it in your editor |
delete | Delete an agent |
edit | Edit an existing agent configuration file |
list | List the available agents |
quickstart | Get up-and-running with an incident agent in <5min! |
route | Determine which agent will be used to analyze the given payload |
run | Run an agent with the provided payload and print the analysis |
serve | Run the Unpage Agent server to automatically process incoming alerts |
templates | List the available agent templates |
Option | Description |
---|---|
--profile TEXT | Use profiles to manage multiple graphs [env var: UNPAGE_PROFILE] [default: default] |
--overwrite | Overwrite the agent file if it already exists |
--template TEXT | The template to use to create the agent file [default: default] |
--editor TEXT | The editor to use to open the agent file [default: from $EDITOR env var] |
--no-edit | Do not open the agent file in your editor |
-h, --help | Show help message and exit |
Option | Description |
---|---|
--profile TEXT | Use profiles to manage multiple graphs [env var: UNPAGE_PROFILE] [default: default] |
--debug | Enable debug mode to print the history of the agent |
--pagerduty-incident TEXT | PagerDuty incident ID or URL to use instead of payload or stdin |
-h, --help | Show help message and exit |
Option | Default | Description |
---|---|---|
--host TEXT | 127.0.0.1 | The host to bind to |
--port INTEGER | 8000 | The port to bind to |
--workers INTEGER | 1 | The number of workers to use |
--profile TEXT | default | The profile to use for configuration |
--reload / --no-reload | False | Reload the server when code changes |
--tunnel / --no-tunnel | False | Tunnel the server through ngrok for external access |
--ngrok-token TEXT | From env var | The ngrok token for tunneling |
--ngrok-domain TEXT | None | The ngrok domain for tunneling |
/webhook
endpoint that receives alert payloads as JSON via POST requests