المهارات observability-and-instrumentation
📦

observability-and-instrumentation

مراجعة المحتوى r2 آمن ⚙️ الأوامر الخارجية📁 الوصول إلى نظام الملفات🔑 متغيرات البيئة

Instrument Production Systems with Clear Telemetry

Production teams need reliable evidence when services fail, slow down, or behave unexpectedly. This skill helps design useful logs, metrics, traces, alerts, and verification steps.

يدعم: Claude Codex Code(CC)
🥉 78 برونزي

التثبيت باستخدام Agent لدي

انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.

طلب الوكيل
Review the Skillstore skill "observability-and-instrumentation" from https://skillstore.io/skills/addyosmani-observability-and-instrumentation.md and its manifest at https://skillstore.io/api/skills/addyosmani-observability-and-instrumentation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.

موارد مهيّأة لـ Agents

استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.

اختبرها

جارٍ استخدام "observability-and-instrumentation". A payment retry feature needs telemetry for success rate, permanent failures, and provider latency.

النتيجة المتوقعة:

  • Use structured events for payment outcomes and provider error codes.
  • Add a latency histogram with percentiles for provider calls.
  • Trace a sampled checkout request and retain error traces.

جارٍ استخدام "observability-and-instrumentation". A team wants to page on CPU usage and label metrics with customer IDs.

النتيجة المتوقعة:

Use user-facing error rate or latency for paging, and move customer identifiers to logs or traces. Keep metric labels bounded.

جارٍ استخدام "observability-and-instrumentation". A service has alerts but no runbooks or staging verification.

النتيجة المتوقعة:

  • Link every alert to a short runbook with meaning, first check, and escalation path.
  • Test induced failures and confirm telemetry reaches the correct channel.

التدقيق الأمني

آمن

All 41 static findings are false positives caused by Markdown backticks, documentation syntax, benign example code, or a relative reference. The reviewed skill contains no executable commands, credential exfiltration, unsafe file access, or prompt injection.

1
الملفات التي تم فحصها
239
الأسطر التي تم تحليلها
0
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة
لم يكتشف أحدث تدقيق ثابت ودلالي مكتمل أي نتائج أمنية مؤكدة. ولا يثبت ذلك أن المهارة خالية من الآثار الجانبية.
شارك واستشهد بهذا التقرير

شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.

فتح التقرير المرتبط بالإصدار
تقييم الأمان

نسخ رابط التقرير

https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

شارة Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-observability-and-instrumentation/security.svg)](https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge)

شارة HTML

<a href="https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-observability-and-instrumentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

بطاقة قابلة للتضمين

<iframe src="https://skillstore.io/embed/skills/addyosmani-observability-and-instrumentation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
الاستشهادات الأكاديمية (APA · BibTeX · CFF)

اقتباس APA

addyosmani. (2026). observability-and-instrumentation security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2

اقتباس BibTeX

@techreport{addyosmani-addyosmani-observability-and-instrumentation-2026, author = {addyosmani}, title = {observability-and-instrumentation security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "observability-and-instrumentation security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2" identifiers: - type: other value: "skillstore:addyosmani-observability-and-instrumentation:audit:2" description: "Skillstore immutable audit report identifier"

تقييم Skillstore

سبب هذا التقييم موثوقية الأدلة: متوسط
55
الهندسة المعمارية
85
قابلية الصيانة
87
المحتوى
65
المجتمع
91
الامتثال للمواصفات

ما الذي يمكنك بناؤه

Instrument a New Endpoint

Define the endpoint questions, add structured logs, and select RED metrics with bounded labels.

Improve Incident Diagnosis

Add correlation IDs, distributed tracing, and actionable alerts so on-call engineers can follow a failing request.

Review Production Readiness

Use the verification checklist to assess telemetry coverage, secret handling, alert quality, and staging validation.

جرّب هذه الموجّهات

Start with Observability Questions
Review this feature description and list two to four questions an on-call engineer must answer. Map each question to a log, metric, or trace.
Design Structured Logging
Design structured log events for this endpoint. Include stable event names, safe fields, log levels, correlation IDs, and entry-point attribution.
Plan Service Telemetry
Create an observability plan for this service and its dependencies. Cover RED metrics, bounded labels, OpenTelemetry traces, sampling, and symptom-based alerts.
Audit an Instrumentation Change
Review this instrumentation diff against the observability checklist. Identify missing signals, cardinality risks, sensitive data exposure, alert weaknesses, and staging tests.

أفضل الممارسات

  • Start from concrete on-call questions and map every signal to one question.
  • Allowlist telemetry fields and exclude secrets, tokens, passwords, and full PII.
  • Verify telemetry and alert delivery in staging before calling the work complete.

تجنب

  • Adding unstructured logs without a stable event name or correlation ID.
  • Using user IDs, raw URLs, or error text as metric labels.
  • Paging on infrastructure causes without a user-facing symptom or runbook.

الأسئلة المتكررة

What does this skill help me instrument?
It guides logging, metrics, distributed tracing, alerting, runbooks, and telemetry verification for production features.
Does it recommend a specific monitoring vendor?
No. It favors vendor-neutral OpenTelemetry concepts and explains how to adapt them to common backends.
Why are structured logs important?
Structured fields make events searchable, consistent, and easier to correlate during incidents.
How should I choose metric labels?
Use small fixed sets such as route templates, status classes, and provider names. Keep unbounded values in logs or traces.
Should every alert page an engineer?
No. Page only for actionable user-facing symptoms. Use tickets for degradations that can wait.
How do I validate new telemetry?
Induce a staging failure, inspect structured logs, send test traffic, follow a trace, and test each alert and runbook link.

تفاصيل المطور

المؤلف

addyosmani

الترخيص

MIT

مراجعة Skillstore

r2

تنبيه الإصدار

لم يعلن المؤلف عن إصدار.

مرجع

5d5054f8a23586f9b500fece1cb613a9dffc787b

حداثة الصيانة

١٩‏/٩‏/٢٠٢٦

الاستخدام

1 تنزيلات · 0 مشاهدات

بنية الملفات

📄 SKILL.md

المزيد من addyosmani

عرض الكل
عرض الكل
📦

appinsights-instrumentation

84

تجهيز تطبيقات Azure باستخدام Application Insights

بواسطة microsoft

قد تكون إضافة بيانات قياس موثوقة إلى التطبيقات المستضافة على Azure صعبة عبر أطر العمل ونماذج النشر المختلفة. توفر هذه المهارة إرشادات موجزة لإعداد Application Insights، ومراجع SDK، وأنماط تكوين Azure.

DevOps والبنية التحتية عرض