Investigate a monitor
Read current status and recent response logs.
/oo OpenStatus: Get status and HTTP response logs for OpenStatus monitor [monitor ID], then summarize regional failures and returned response codes.
Ask your AI assistant to work with OpenStatus: investigate Monitor Status and Response Logs.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read current status and recent response logs.
/oo OpenStatus: Get status and HTTP response logs for OpenStatus monitor [monitor ID], then summarize regional failures and returned response codes.
Read a monitor's aggregated metrics for the supported period.
/oo OpenStatus: Get summary metrics for OpenStatus monitor [monitor ID] over [time range] and explain the returned latency and availability data.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect using your OpenStatus API Key.
Connect OpenStatus →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
OpenStatus monitor actions give an AI assistant current regional status, aggregated metrics, and HTTP response logs.
Read current status and recent response logs.
Read a monitor's aggregated metrics for the supported period.
List OpenStatus HTTP, TCP, and DNS monitors in the authenticated workspace.
openstatus.list_monitors Retrieve one OpenStatus monitor configuration by ID.
openstatus.get_monitor Retrieve the current OpenStatus monitor status for each configured region.
openstatus.get_monitor_status Retrieve aggregated OpenStatus monitor metrics for a time range and regions.
openstatus.get_monitor_summary List recent OpenStatus HTTP response logs for a monitor.
openstatus.list_http_response_logs Trigger an immediate OpenStatus monitor check across configured regions.
openstatus.trigger_monitor Create a new OpenStatus HTTP monitor.
openstatus.create_http_monitor Partially update an existing OpenStatus HTTP monitor.
openstatus.update_http_monitor Delete an OpenStatus monitor by ID.
openstatus.delete_monitor No matching tools.
trigger_monitor starts an immediate check across configured regions; inspect status or logs for the resulting evidence.
create_http_monitor requires a name, URL, and periodicity.
Summary metrics are aggregated. Use the separate HTTP response log operation for returned request records.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.