Instrument Your App with LogBrew
Application errors and logs can be difficult to trace across deployments. This skill configures LogBrew instrumentation and checks that a test event can be read back.
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
Review the Skillstore skill "instrument-app" from https://skillstore.io/skills/logbrewco-instrument-app.md and its manifest at https://skillstore.io/api/skills/logbrewco-instrument-app/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
"instrument-app" 사용 중입니다. Instrument an Express service and verify delivery.
예상 결과:
The service uses the Express integration. The test event was read back with the expected service, environment, and release.
"instrument-app" 사용 중입니다. Check why a test event is missing.
예상 결과:
The read-back returned no event. Check the project, time range, ingest key, and client flush behavior before reporting success.
Most static matches are Markdown, SDK configuration, or safe secret-handling guidance. The Rails key export can expose a secret in shell history, and the workflow should validate install commands and review existing logs before forwarding them.
이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.
버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.
https://skillstore.io/skills/logbrewco-instrument-app/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/logbrewco-instrument-app?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/logbrewco-instrument-app?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/logbrewco-instrument-app/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/logbrewco-instrument-app.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>logbrewco. (2026). instrument-app security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/logbrewco-instrument-app/audits/1@techreport{logbrewco-logbrewco-instrument-app-2026,
author = {logbrewco},
title = {instrument-app security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/logbrewco-instrument-app/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "instrument-app security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "logbrewco"
date-released: "2026-10-27"
url: "https://skillstore.io/skills/logbrewco-instrument-app/audits/1"
identifiers:
- type: other
value: "skillstore:logbrewco-instrument-app:audit:1"
description: "Skillstore immutable audit report identifier"
Add server-side error capture and structured logging to an existing service.
Send a test event and confirm its service, environment, and release.
Review event fields, secret handling, and trace correlation guidance.
Identify the framework, existing logger, and entry point in this application.
Set up LogBrew for this application using its existing framework and secret configuration.
Send a safe test event and verify its service, environment, and release by reading it back.
Inspect the existing instrumentation for duplicate senders, sensitive log fields, release metadata, and shutdown flushing.
작성자
logbrewco라이선스
MIT
Skillstore 리비전
r1
버전 안내
작성자가 버전을 선언하지 않았습니다.
참조
07bd35e828bc5e79e3fd7ad19a1298e33cdbb753
유지보수 최신성
2026. 10. 27.
사용량
0 다운로드 · 0 조회
파일 구조
Debug Production Failures With Evidence
Production failures can be difficult to trace across errors, releases, logs, and affected users. This skill organizes the investigation and verification into seven steps.
Verify Release Health After Deployment
Release decisions can be difficult when error counts and traffic change together. Compare release evidence and receive a Go, Rollback, or Wait recommendation.
Diagnostica errores de producción más rápido
작성자 sickn33
Depurar errores de producción es lento cuando los logs, las trazas y los releases están dispersos. Esta skill guía a Claude, Codex y Claude Code mediante un análisis estructurado de causa raíz y mejoras de observabilidad.
Depurar problemas de producción con evidencia
작성자 sickn33
Los fallos complejos son difíciles de triar cuando los registros, trazas y evidencia del código están dispersos. Esta habilidad guía a Claude, Codex y Claude Code mediante un diagnóstico estructurado, planificación de correcciones y validación.
Crear agentes LangChain de producción
작성자 sickn33
Los agentes LangChain de producción necesitan una arquitectura clara, memoria, evaluación y observabilidad. Esta skill guía a Claude, Codex y Claude Code a través de patrones de LangGraph, herramientas asíncronas, RAG, pruebas y despliegue.
Diagnostica errores con depuración inteligente
작성자 sickn33
Depurar fallos de producción es lento cuando la evidencia está dispersa entre logs, trazas y código. Esta habilidad guía la clasificación inicial, la priorización de hipótesis, la instrumentación segura, las correcciones y la validación.
Añadir patrones de observabilidad en Python
작성자 0xDarkMatter
Los servicios de Python a menudo carecen de patrones consistentes de registro, métricas y trazado. Esta habilidad proporciona ejemplos prácticos de structlog, Prometheus y OpenTelemetry para aplicaciones de producción.
Instrumentar aplicaciones de Azure con Application Insights
작성자 microsoft
Agregar telemetría fiable a aplicaciones alojadas en Azure puede ser difícil entre distintos frameworks y modelos de despliegue. Esta habilidad proporciona orientación concisa para configurar Application Insights, referencias de SDK y patrones de configuración de Azure.