# 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.

## Install

```bash
npx skillstore add logbrewco/instrument-app
```

## Metadata

- Status: approved
- Slug: logbrewco-instrument-app
- Skillstore revision: r1
- Version status: missing
- Tree hash: eda4e75150c16c46a68f99b01fd5130a298611566e156a71e7abe550b76ee282
- Author: logbrewco
- GitHub username: logbrewco
- License: MIT
- Repository: https://github.com/logbrewco/skills/tree/abac3ee500d980ca7fa4edb6c75949094d3ea792/plugins/logbrew/skills/instrument-app
- Ref: 07bd35e828bc5e79e3fd7ad19a1298e33cdbb753
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, env\_access, filesystem
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/logbrewco-instrument-app
- Manifest: https://skillstore.pages.dev/api/skills/logbrewco-instrument-app/manifest

## Capabilities

- Detect the application runtime and framework using the LogBrew CLI.
- Select SDK packages and provide setup examples for several frameworks.
- Configure project ingest keys and service, environment, and release metadata.
- Connect supported existing loggers and add a test event.
- Read back events and check their service, environment, and release.
- Apply guidance for structured logging, privacy, traces, and client shutdown.

## Use Cases

- Instrument a web service: Add server-side error capture and structured logging to an existing service.
- Verify a deployment: Send a test event and confirm its service, environment, and release.
- Improve logging practices: Review event fields, secret handling, and trace correlation guidance.

## Prompt Templates

### Review the application

```
Identify the framework, existing logger, and entry point in this application.
```

### Add instrumentation

```
Set up LogBrew for this application using its existing framework and secret configuration.
```

### Verify delivery

```
Send a safe test event and verify its service, environment, and release by reading it back.
```

### Review an existing integration

```
Inspect the existing instrumentation for duplicate senders, sensitive log fields, release metadata, and shutdown flushing.
```

## Limitations

- Requires LogBrew access, appropriate credentials, and network connectivity for event delivery and read-back.
- Frameworks without a full example require consulting the relevant SDK documentation.
- A successful ingest response alone does not prove the event is readable.
- Existing logs and SDK defaults require a privacy review before forwarding.

## Best Practices

- Store ingest keys in protected secret configuration and never paste them into chat.
- Review existing logs and SDK capture defaults for sensitive data before forwarding.
- Confirm the test event through read-back and verify its deployment metadata.

## Anti Patterns

- Treat an accepted send as proof that an event is readable.
- Add a second sender for the same signal without discussing existing instrumentation.
- Log credentials, full request bodies, or unnecessary personal data.

## Security Audit

- Audited at: 2026-10-27T11:31:16.964\+00:00
- Summary: 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.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0