'on-call' 검색 결과

Prepare handoffs between engineers responsible for responding to system incidents. Organize active incidents, investigations, recent changes, and upcoming events into shift summaries, with guidance for mid-incident transfers, asynchronous updates, and checks that the incoming engineer receives alerts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare an on-call shift handoff summary
• Transfer incident response leadership during an active incident
• Arrange asynchronous handoffs across time zones

Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a one-page service operations guide in HTML. It organizes service details, alerts and first responses, dashboard links, procedures with copyable commands, an on-call schedule, and an incident checklist so teams can find operational instructions together.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an operations guide for a service
• Documenting first responses to alerts
• Organizing deployment and rollback procedures

Maintain legacy Java code that uses the deprecated Azure Communication CallingServer SDK. Compare old and replacement dependencies, client classes, and recording examples to plan a migration to Call Automation and identify APIs needing verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Maintain legacy Java CallingServer code
• Compare dependencies and client class names
• Review existing call recording code

Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design production alerts, route notifications by severity, and organize on-call schedules. Use configuration examples to define backup contacts, escalation steps when alerts go unanswered, and runbooks that guide responders through incident investigation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define alert thresholds and severity levels
• Route notifications to Slack and PagerDuty
• Plan on-call rotations and holiday coverage

Create incident response runbooks with ordered recovery steps, severity levels, escalation contacts, and status update templates. Help on-call engineers follow clear procedures during outages, verify recovery, and keep stakeholders informed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a payment service outage runbook
• Documenting database incident recovery
• Preparing guides for new on-call engineers

Investigate Sentry alerts using Datadog logs and recent GitHub changes, then post an initial diagnosis with a severity assessment. Notify the on-call team when severity reaches the configured threshold or the investigation remains inconclusive, without changing monitored systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate new and unresolved Sentry alerts
• Compare failures with logs and recent deployments
• Notify on-call staff for severe or inconclusive alerts

Write the weekly on-call handoff: everything the incoming on-call needs, triage-ready, posted to the channel at shift boundary. Use when the weekly routine fires, or when someone asks for a handoff / shift summary / "catch the next on-call up".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bootstrap a Claude-assisted on-call for this channel/repo: discover the available connectors, mine incident history into draft triage playbooks, interview the human for policy, validate against held-out incidents, and install the scheduled routines. Use when the user wants to "set up on-call", "bootstrap the on-call kit", "onboard this channel", or has just installed the oncall-kit plugin. Five gated phases — never run more than one phase per turn, and never activate anything before Phase 4 sign-off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

On-call 轮值和 Runbook 维护时使用。适用于值班制度设计、操作手册编写、升级路径定义。融合 PagerDuty On-call + Atlassian Runbook。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Betteruptime — better Uptime monitoring, status pages, incident management, on-call scheduling, and heartbeat tracking. Covers monitor configuration, response time analysis, incident lifecycle, on-call rotations, and SLA reporting. Use when managing uptime monitors, reviewing incident history, configuring on-call schedules, or analyzing response times in Better Uptime.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build server-side calling workflows in Java with Azure Communication Services. Implement automated phone menus, incoming and outgoing calls, transfers, recording, spoken prompts, and recognition of speech or keypad input, with examples for handling call events.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building automated phone menus in Java
• Routing incoming calls to another number
• Adding spoken prompts and keypad or speech input

Create or update step-by-step instructions for recurring operational tasks. Document exact commands, expected results, failure responses, verification checks, rollback steps, and escalation contacts so operations teams have a concrete procedure to follow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting recurring operational tasks
• Turning experienced staff knowledge into written procedures
• Adding troubleshooting and rollback steps to existing instructions

Generate an operational runbook template from a service name. Provide sections for starting, stopping, health checks, incident handling, maintenance, and rollback, so teams can add service-specific commands and build consistent operating procedures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an initial runbook for a new service
• Standardizing incident procedures across teams
• Preparing documentation for on-call onboarding

Assess startup engineering operations across delivery, hiring, team structure, and production practices. Use delivery metrics, hiring conversion rates, and staffing data to identify bottlenecks, estimate candidate needs, and plan management roles and operational improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find where development work waits before release
• Estimate candidate volume needed for hiring goals
• Review team structure and manager hiring needs

Build a single-page operations guide for engineers on call, the people assigned to respond to service issues. Organize service dependencies, alert thresholds, dashboard links, copyable commands, duty rotations, and an incident response checklist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Bring service operations information onto one page
• Document alert severity, thresholds, and procedure links
• Prepare commands and checklists for incident response

Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining legacy code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up alerting rules, configure on-call rotations, and manage incident response workflows. Integrate with PagerDuty, Opsgenie, or Grafana OnCall for alert routing and escalation. Use when implementing alerting strategies and on-call management for production systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build AI-enabled .NET applications with Semantic Kernel using services, plugins, prompts, and function-calling patterns that remain testable and maintainable. USE FOR: adding AI-driven prompts, plugins, or orchestration to a .NET app; reviewing kernel construction, service registration, or plugin usage; building function-calling. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst tiering, and shift handoffs. Use when the user mentions 'SOC,' 'security operations,' 'SOC analyst,' 'alert triage workflow,' 'runbook,' 'escalation,' 'on-call,' 'SOC tiering,' 'tier 1 / tier 2,' 'MTTD,' 'MTTR,' 'alert fatigue,' 'alert tuning,' 'shift handoff,' 'SOAR,' or wants to design or improve a security operations team.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Better Stack (formerly Better Uptime + Logtail) is an observability platform that combines uptime monitoring, log management, incident response with on-call escalation, and status pages. Use when a user asks to set up uptime monitors or heartbeat monitoring for cron jobs, create escalation policies, send logs with @logtail/node or the Pino transport, manage Better Stack through its API or Terraform provider, or publish status page updates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.