MCP DB Hub v0.1.1 — OTLP audit logs

MCP DB Hub v0.1.1 adds OTLP audit log export to OpenTelemetry Collector and compatible observability backends. Configure it in the English administration UI under Settings → Audit log export.

New in this release

• HTTP/protobuf and gRPC, with HTTPS, custom CA certificates, and encrypted authentication headers.
• Asynchronous export from the persisted audit trail, bounded batches, retry/backoff, saved delivery progress, and recovery after service or receiver restarts.
• Test log and delivery status in Settings, including pending/accepted/rejected counts and safe error feedback. Stored authentication headers are never returned by the API.
• Sanitized OTLP records: caller, source, operation, request ID, keyed query fingerprint, timing, row count, and error category. SQL text, parameters, results and credentials are excluded.
• English default README, installation instructions and release content, with complete Simplified Chinese documentation alongside them.

Export is disabled by default. Enabling starts with new audit events. Delivery may repeat events after ambiguous acknowledgements; use service.instance.id plus mcpdbhub.audit.id for deduplication. Partial/permanent rejections are counted and not retried; permanent errors pause subsequent exports until corrected settings are saved. Unsent events share the 30-day local audit retention limit.

OTLP setup and delivery semantics · Collector configuration · 中文说明

Download and upgrade

Asset	Platform / purpose
mcpdbhub-0.1.1-linux-amd64.tar.gz	Linux x86_64 / amd64
mcpdbhub-0.1.1-linux-arm64.tar.gz	Linux aarch64 / arm64
SHA256SUMS	SHA-256 checksums for both packages and the validation report
VALIDATION.json	Source commit, CI, focused database and actual archive verification

Packages require glibc 2.36 or newer and include the embedded UI, private C++ libraries, bilingual documentation, examples and third-party notices. No Go or Node.js runtime is needed. Keep the complete extracted directory and launch ./mcpdbhub serve.

Stop the existing service, back up its configuration database and matching master key, then start the new program with the existing data directory. Source credentials and Agent grants are retained. See the installation and upgrade guide.

Verification scope

• All four uploaded assets were downloaded again from GitHub and matched local SHA-256 hashes. Both downloaded packages independently passed all 21 installation and OTLP checks again.

• Native Linux amd64 and arm64 GitHub CI passed: Go tests, race checks, UI/numeric-parameter checks and CLI build.

• Both actual distribution archives passed 21 checks each after independent extraction, including HTTP/stdio MCP, OTLP HTTP/protobuf and gRPC, receiver outage, restart recovery, token revocation and password recovery.

• OrbStack: full Go race checks, frontend build and lossless numeric-parameter checks passed. Real PostgreSQL 17.11 adapter and HTTP MCP checks passed, including six query/error and six rejected-operation cases.

• Official OpenTelemetry Collector 0.160.0 accepted real HTTP/protobuf and gRPC logs. Receiver downtime did not prevent queries; pending records survived Hub restart and were delivered after recovery.

• Local Chrome verified the English configuration flow, errors, credential clearing, keyboard interaction and desktop/390px layouts without application console errors.

The database adapters are unchanged. The full 18-product / 20-version matrix remains the historical v0.1.0 evidence; it was not rerun for this audit-export update. Linux amd64 package execution on the local arm64 OrbStack host uses emulation; native architecture CI is recorded separately. Native macOS, Windows and Alpine/musl distributions are not included.

A project license has not yet been selected. Third-party notices are included in the repository and packages.