Plan observability for an application's Algolia search journey. Define measurements for availability, latency, index freshness, relevance, and event health, then map them to dashboards, alerts, traces, and service objectives using product baselines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Instrument an Algolia integration for actionable availability, latency, freshness, relevance, and event-health signals. Use when defining dashboards, alerts, traces, or service objectives. Trigger with "monitor Algolia", "Algolia metrics", or "search observability".
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This skill instruments the application-owned search journey rather than substituting generic provider claims. It connects client outcomes, request IDs, index publication, source freshness, and product-level relevance indicators.
Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.
Telemetry must exclude API keys, raw personal data, sensitive queries, and unrestricted record payloads. Use approved read-only monitoring access where provider data is needed.
Do not log secrets or raw sensitive queries, create arbitrary alert thresholds, or enable high-cardinality labels without review.
Return the signal catalog, field and redaction schema, SLO mapping, dashboards, alerts, synthetic checks, test evidence, and known blind spots.
| Condition | Response |
|---|---|
| Request ID unavailable | Preserve local trace correlation and full redacted error metadata. |
| High cardinality detected | Aggregate or hash approved identifiers. |
| Provider and app latency differ | Split the spans and investigate the dominant segment. |
| No product SLO exists | Report measurements and request an owner decision. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
journey=product-search; slo=company-owned; fields=operation,outcome,duration,index
Expected handoff:
secret-fields=blocked; freshness-sentinel=pass; alert-threshold=baseline-derived
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.