Aug 8, 2025

Speeding up the path from alert to resolution

Every second an alert sits unresolved is time your customers feel the impact. But “resolving” is more than just finding the cause. It’s configuring the tools, digging through logs, and deciding whether action is even required. If that process is clunky, your agents (and, by extension, your engineers) lose valuable time.

Today’s update makes Unpage agents:

  • Simpler to configure: picking an LLM is now guided, with sensible defaults and recommendations

  • More decisive: your default agent can now (optionally) auto-resolve PagerDuty incidents that don’t require human intervention

  • Easier to control: intuitive subcommands mean less CLI guesswork and clutter

  • Better at investigation: new log search tools for Datadog and Papertrail let agents go straight to the source

Here’s what’s new 👇

Simplified LLM configuration

Configuring an LLM for your agents used to mean digging into YAML and hunting for the right provider/model syntax. Now, unpage configure walks you through provider and model selection with built-in recommendations and descriptions. Here’s how it works:


LLM configuration docs →

New tool: Auto-resolve PagerDuty incidents

We’ve added a new pagerduty_resolve_incident tool 😎

With it, your default agent can (if you choose) automatically resolve PagerDuty incidents that it determines don’t require further investigation (and even leave a resolution message).

This helps close the loop on false alarms and keeps on-call rotations focused on what actually matters.

PagerDuty plugin docs →

More intuitive subcommands

MCP-related commands (server, tools, and client) are now grouped under a top-level mcp namespace.

Before

# Start the MCP server 
uv run unpage start

After

# Start the MCP server
uv run unpage mcp start

This makes it easier to discover and run all MCP-related commands in one place. Additionally, the visualize command has been removed for now to cut down on noisy output, and the PagerDuty plugin configuration docs have been updated for clarity.

Updated MCP command reference docs →

Updated Agent command reference docs →

Log search for Datadog and Papertrail

Your agents can now query logs directly via the new log_search tools in the Datadog and Papertrail plugins, which means o more switching contexts to find relevant traces or historical events. Just ask your agent to look it up 😄

Datadog log search docs →

Papertrail log search docs →

___

Thanks again to our early alpha users for kicking the proverbial Unpage tires. These updates are aimed squarely at speeding up your investigation-to-resolution loop. We can’t wait to hear what you think.

And for anyone who’s not gotten started yet…

👉 GitHub repo

💬 Join our Slack community to connect with other users and chat directly with the Unpage team

© APTIBLE INC.

© APTIBLE INC.

© APTIBLE INC.