Skip to main content

EXTENSIONS

Built by operatives — models, drivers, vaults, and reports, the parts that plug into Swamp.

Filter by what you need and pull what fits.

Selection
9 results
label:logs

Aws/logs

@swamp/aws/logs · v2026.10.06.1

AWS LOGS infrastructure models

upd Oct 674 pullsA100/100

Cloudflare/logs

@swamp/cloudflare/logs · v2026.09.30.1

Cloudflare logs infrastructure models

upd Sep 3049 pullsA100/100

Aws/logs

@webframp/aws/logs · v2026.09.24.2

Query and analyze CloudWatch Logs for operational visibility and incident investigation.

upd Sep 25107 pullsA100/100

Datadog/logs

@webframp/datadog/logs · v2026.09.18.1

Datadog Logs — log search, aggregation, and analytics

upd Sep 2021 pullsA100/100

Victorialogs

@magistr/victorialogs · v2026.09.19.2

VictoriaLogs query API — run LogsQL queries, field/stream stats, and hits

upd Sep 1931 pullsA100/100

Observability Agent

@magistr/observability-agent · v2026.09.19.2

Install and configure a host-native metrics + logs agent on a remote

upd Sep 1914 pullsA100/100

Openobserve

@sntxrr/openobserve · v2026.08.29.1

Operate a self-hosted OpenObserve instance from swamp, and decide safely whether a newer upstream release should be rolled out to it. OpenObserve publishes release candidates into the same tag namespace as stable releases -- on 2026-08-29 the newest tag was v1.0.0-rc1, published eleven days AFTER the newest stable v0.92.2 -- so anything that reads the tag list and sorts it pins an RC. That is worse here than for a stateless app: OpenObserve is a log store, and an RC that migrates the on-disk schema is not undone by re-pinning the previous tag, because the previous binary can no longer read what the new one wrote. The `check_update` method reads GitHub *releases* rather than tags, excludes drafts and prereleases (by the GitHub flag OR a semver prerelease suffix, since the flag is hand-set and occasionally wrong), applies real semver precedence so a prerelease sorts before its own release, and reports the newer prereleases it skipped so a pending major stays visible without being auto-applied. It then confirms the candidate tag actually resolves in the registry before offering the update -- a GitHub release and a pushed image are separate events, and proposing a bump whose image does not exist yet fails the deploy at `compose pull`, after the running container has already been stopped. The `health` method probes /healthz, treating a refused connection as a health result rather than a model error so a down instance is distinguishable from a broken check.

upd Aug 2932 pullsA100/100

Audit Timeline

@jentz/audit-timeline · v2026.07.30.1

Workflow-scope report that renders a change-audit timeline from CloudWatch

upd Jul 3120 pullsA100/100

Grafana Ext

@shrug/grafana-ext · v2026.07.11.1

Grafana swamp-native gaps: a control-plane admin model (idempotent ensureServiceAccount over basic-auth) plus a queryLogs extension that adds LogQL/Loki reads to @keeb/grafana/instance alongside its queryMetrics.

upd Jul 1121 pullsA100/100