Logging monitoring

Skill event4u-app/agent-config/src/skills/logging-monitoring

Universal AI Agent OS — audited skills, governance rules, replayable state. One contract, every host agent.

Install

npx -y skills add event4u-app/agent-config --skill logging-monitoring

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when working with logging or monitoring — Sentry error tracking, Grafana/Loki log aggregation, structured logging channels, or monitoring helpers.

SKILL.md

3.2 KB, as published. Nobody here has run it

logging-monitoring

When to use

Use when adding logging, configuring monitoring stack, or integrating Sentry/Grafana/Loki.

Do NOT use when:

Creating Grafana dashboards (use grafana skill)
Dashboard design decisions (use dashboard-design skill)

Procedure: Add logging or monitoring

Read the framework's logging config for available channels (config/logging.php in Laravel, LOGGING in Django, winston/pino in Node).
Check for Grafana module: app/Modules/Grafana/.
Read agents/ docs for module-specific logging.

Monitoring stack

Tool	Purpose	Integration
Sentry	Error tracking	`sentry/sentry-laravel`, `MonitoringHelper`
Grafana	Dashboards	Connected to Loki
Loki	Log aggregation	`itspire/monolog-loki` via Monolog
Slack	Alert notifications	Webhook for error-level

Log channels

Channel	Purpose
`stack_without_slack`	Daily file + errorlog (no Slack)
`slack`	Error alerts to Slack
`loki`	Send logs to Grafana Loki
`loki_import_*`	Import-specific Loki with custom labels
`daily`	Rotating file logs

Loki labels

'globalLabels' => ['app' => '{project}', 'service' => '{service}', 'env' => $env],

The service label differentiates log types in Grafana queries.

Config flags

Env Variable	Purpose	Default
`LOG_CLIENT_SOFTWARE_REQUESTS`	Log incoming API requests to DB	`false`
`LOG_EXTERNAL_API_REQUESTS`	Log outgoing external API requests	`true`
`LOG_WEBHOOK_REQUESTS`	Log webhook requests to DB	`false`
`LOG_CHANNEL_IMPORT`	Channel for import logs	`daily`

Grafana/Loki dashboard rules

Hide Loki metadata columns: labelTypes, traceID, traceID (field).
Use correct Loki service labels: import_result for final states, import_snapshot for cron.
Verify column names match data semantics.

Conventions

→ See guideline php/logging.md for log levels, structured context, what to log, Sentry patterns.

Validate

Verify log level matches severity (no Log::error() for info-level events).
Confirm structured context is passed (not string interpolation).
Check that no sensitive data (passwords, tokens, PII) appears in log output.
Verify Sentry captures include relevant context for debugging.

Output format

Logging configuration or structured log statements
Sentry integration with proper context and breadcrumbs

Gotcha

Sentry has 200KB event size limit — large context gets truncated.
Structured logging keys must be snake_case.
Don't create Loki channels without corresponding Grafana dashboard query.

Do NOT

Do NOT use Sentry SDK directly — use MonitoringHelper.
Do NOT interpolate variables into log messages — use context array.
Do NOT log at error level for expected/handled conditions.

Auto-trigger keywords

logging
monitoring
Sentry
Grafana
structured logging
log levels