oneuptime_help

com.oneuptime/mcp · Verify this server

Get help and guidance for using the OneUptime MCP server. Returns information about available resources and common operations. Use this tool first to understand what you can do with OneUptime. AVAILABLE RESOURCES: - Teams: Groups of users with shared access to project resources. - Labels: Labels for organizing and filtering project resources. - Security Cases: Manages Security Case resources in OneUptime. - Security Case Notes: Manages Security Case Note resources in OneUptime. - Security Detections: Manages Security Detection resources in OneUptime. - Security Playbooks: Manages Security Playbook resources in OneUptime. - Status Pages: Public-facing page showing the status of your services to your customers. - On-Call Duty Policies: Defines escalation rules and schedules for incident response. - Monitors: Defines what to monitor (websites, APIs, servers) and how to check their health and availability. - Monitor Statuses: Represents the health states of monitors (e.g., Operational, Degraded, Offline). - Incident States: Represents the lifecycle states of incidents (e.g., Created, Acknowledged, Resolved). - Incidents: Represents service disruptions or issues affecting your systems. Track incident lifecycle from creation to resolution. - Incident State Timelines: History of state changes for incidents. Creating an entry changes the incident's state (this is how acknowledge/resolve work). - Incident Internal Notes: Internal team-only notes on incidents. - Incident Public Notes: Status-page-visible notes on incidents, seen by customers and subscribers. - Incident Severities: Severity levels for incidents (e.g., Critical, Major, Minor). List these to find the incidentSeverityId required by create_incident. - Alert States: Lifecycle states of alerts (e.g., Created, Acknowledged, Resolved). - Alerts: Notifications triggered when monitors detect issues. Configures who gets notified and how. - Alert State Timelines: History of state changes for alerts. Creating an entry changes the alert's state. - Alert Internal Notes: Internal team-only notes on alerts. - Alert Severities: Severity levels for alerts. List these to find the alertSeverityId required by create_alert. - Incident Alerts: Links an alert to an incident (many-to-many). Create one to link an alert to an incident, delete it to unlink. List these by incidentId to see an incident's linked alerts, or by alertId to see the incidents an alert is linked to. - Monitor Status Events: History of monitor status changes — useful for investigating when a monitor went down or recovered. - Status Page Announcements: Announcements posted to your status pages. - Scheduled Maintenance States: Lifecycle states for maintenance events (e.g., Scheduled, Ongoing, Completed). - Scheduled Maintenance Events: Manages Scheduled Maintenance Event resources in OneUptime. - Scheduled Maintenance State Timelines: Manages Scheduled Maintenance State Timeline resources in OneUptime. - Logs: OpenTelemetry log records from your services. Filter by time range and service. - Spans: OpenTelemetry trace spans from your services. - Metrics: OpenTelemetry metrics from your services. - Exception Instances: Application exceptions captured via telemetry. - Monitor Logs: Raw probe results for monitors — explains why a monitor check passed or failed. - Kubernetes Cost Allocations: Manages Kubernetes Cost Allocation resources in OneUptime. - Security Events: Manages Security Event resources in OneUptime. - Change Events: Manages Change Event resources in OneUptime. - Threat Intel Indicators: Manages Threat Intel Indicator resources in OneUptime. - Acknowledge Incident: Manages Acknowledge Incident resources in OneUptime. COMMON WORKFLOWS: 1. Orient yourself: Use oneuptime_whoami to see your project 2. List incidents: Use list_incidents to see current incidents 3. Respond: Use acknowledge_incident / resolve_incident / add_incident_note 4. Investigate: Use list_logs, list_metrics, list_spans, list_monitor_logs (always with a time-range filter) 5. Create incident: Use list_incident_severities to get a severity ID, then create_incident