golang-observability
Instrument Go Services for Production Observability
Missing telemetry makes production failures difficult to diagnose. This skill guides Go instrumentation with structured logs, metrics, traces, profiling, and analytics privacy considerations.
توقف واطلب التأكيد قبل التثبيت.
راجع الخطة واحصل على موافقة صريحة من المستخدم قبل تغيير الملفات.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
Review the Skillstore skill "golang-observability" from https://skillstore.io/skills/samber-golang-observability.md and its manifest at https://skillstore.io/api/skills/samber-golang-observability/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "golang-observability". Review request metrics that label every request with its full path and user ID.
النتيجة المتوقعة:
- Both labels can create unbounded time series and increase monitoring memory use.
- Replace raw paths with route templates and remove user IDs from metric labels.
- Use access-controlled traces for necessary user-level correlation.
جارٍ استخدام "golang-observability". Our 99.9% availability alert produces noise during short error spikes.
النتيجة المتوقعة:
- Review the availability definition and error-budget calculation.
- Pair short and long burn-rate windows to distinguish sustained degradation from brief spikes.
- Validate thresholds and persistence durations against historical traffic before enabling paging.
جارٍ استخدام "golang-observability". Review a proposed production profiling integration.
النتيجة المتوقعة:
- Keep pprof on a protected internal listener.
- Use encrypted collector transport and redact credentials from startup logs.
- Start with selected profile types and measure overhead on a limited replica set.
التدقيق الأمني
مخاطر عاليةMost static findings are false positives involving Markdown, Go syntax, PromQL expressions, and evaluation fixtures; one profiling URL example encourages credentials over plaintext HTTP. Five additional findings cover credential logging, missing authorization in privacy examples, incomplete erasure reporting, unbounded metric labels, and misleading identifier privacy claims. No evidence found of malicious execution, unauthorized exfiltration intent, or audit-directed prompt injection.
مخاوف أمنية مؤكدة (5)
عناصر مراجعة القدرات (1)
هذه قدرات محلية حقيقية قد يُتوقع وجودها لهذه المهارة، لذا فهي تتطلب مراجعة ولكن لا تُحتسب كسلوك خبيث مؤكد.
عوامل الخطر
⚙️ الأوامر الخارجية (38)
🌐 الوصول إلى الشبكة (8)
📁 الوصول إلى نظام الملفات (5)
🔑 متغيرات البيئة (1)
⚡ يحتوي على سكربتات (2)
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/samber-golang-observability/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](https://skillstore.io/skills/samber-golang-observability?utm_source=security_passport_badge)شارة HTML
<a href="https://skillstore.io/skills/samber-golang-observability?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-observability/security.svg" alt="Skillstore security assessment" loading="lazy"></a>بطاقة قابلة للتضمين
<iframe src="https://skillstore.io/embed/skills/samber-golang-observability.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
samber. (2026). golang-observability security audit report (audit version 1) [Author version 1.3.2]. Skillstore. https://skillstore.io/skills/samber-golang-observability/audits/1اقتباس BibTeX
@techreport{samber-samber-golang-observability-2026,
author = {samber},
title = {golang-observability security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-observability/audits/1},
note = {Author version 1.3.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-observability security audit report (audit version 1)"
version: "1.3.2"
type: report
authors:
- name: "samber"
date-released: "2026-10-18"
url: "https://skillstore.io/skills/samber-golang-observability/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-observability:audit:1"
description: "Skillstore immutable audit report identifier"
تقييم Skillstore
سبب هذا التقييم موثوقية الأدلة: متوسطما الذي يمكنك بناؤه
Instrument a New Go API
Add request metrics, structured logs, and trace spans before releasing a new service.
Improve Production Alerting
Review metric labels, latency histograms, and error-budget alerts to reduce monitoring noise and identify coverage gaps.
Review Analytics Data Flows
Evaluate server-side event tracking, consent handling, identifiers, and deletion workflows with engineering and privacy stakeholders.
جرّب هذه الموجّهات
Review this Go handler for structured slog fields, context propagation, log levels, and sensitive data. Explain the smallest useful changes.
Instrument this Go router with request counters and latency histograms. Use route templates, bounded labels, suitable buckets, and PromQL comments.
Review this Go service's OpenTelemetry setup. Preserve context across database and HTTP calls, correlate slog records, and propose sampling and exemplar settings.
Audit this Go repository across logs, metrics, traces, profiles, and analytics. Report evidence, security gaps, and prioritized fixes without changing production settings.
أفضل الممارسات
- Validate library APIs and telemetry examples against the versions installed in your project.
- Use bounded metric labels, intentional sampling, and tested alert thresholds before production rollout.
- Protect profiling endpoints, redact secrets, and verify authorization and consent before processing user telemetry.
تجنب
- Copying examples into production without security review or integration tests.
- Using raw paths, user IDs, or request IDs as metric labels.
- Treating pseudonymous identifiers as anonymous data or assuming analytics examples guarantee compliance.