jcoffey-dev
13cf9a30cb
Full rebrand across cosmetic branding, code identifiers, and infrastructure/data-plane naming, using the supplied Cairn OBS logo package. Cosmetic: favicon/logo swap (also closes a stale license-audit finding -- the old favicon was SvelteKit's unreplaced scaffold logo), new centered welcome landing page, larger/legible sidebar logo, page titles, CLAUDE.md/README/docs prose. Code identifiers: Go module path github.com/sentry/sentry -> github.com/cairnobs/cairnobs across all 13 modules and ~91 files (protoc regenerated); Rust crates sentry-agent/sentry-parser/sentry-search -> cairnobs-*; CLI sentryctl -> cairnobsctl; Terraform provider fully renamed (sentry_dashboard etc. -> cairnobs_dashboard, provider type, env vars); every session/auth cookie name; agent config paths and Windows service identity. Deliberately preserved: the gRPC wire protocol's protobuf packages (sentry.logs.v1, sentry.agent.v1) and their Go import directory (proto/sentry/...) -- renaming the wire-level package would break every currently-deployed agent binary (confirmed two real hosts, including mail.inbuxa.com, are actively streaming through this exact contract) until rebuilt and redeployed in lockstep with an ingest cutover. Only the Go module path wrapping the generated code changes. Infrastructure: every docker-compose container name (root and three component-level compose files); the Helm chart (directory, Chart.yaml, named-template helpers, all templates, values.yaml image repos); Kubernetes Operator (CRD group sentry.io -> cairnobs.io, both CRD YAML files, Go identifiers, RBAC markers); the coupled enterprise/tenantcrd package. Caught and fixed real path-coupling bugs along the way: the Helm chart's search/ingest volume mounts and the dev-only-credential detection constant vs. docker-compose.yml's literal values had to move together or a security warning would have silently stopped firing. Data plane: Postgres database sentry_metadata -> cairnobs_metadata and role sentry -> cairnobs; ClickHouse database sentry -> cairnobs; Kafka topic sentry.logs.raw -> cairnobs.logs.raw and its consumer groups. Source-level defaults, docker-compose.yml, and every migrate.sh/ provision script default updated together; already-applied migration files left untouched per this repo's immutable-migration convention. Verified at every layer: all 13 Go modules build/vet/test clean, both Rust workspaces (agent, search) build/clippy/test clean, npm run check/ build clean, docker compose config validates on all four compose files. Live-verified against a real docker stack multiple times through this work, including a final fresh-volume run confirming the actual renamed Postgres database/role, ClickHouse database, and Kafka topic all work end to end with a real login and query, zero console errors.
80 lines
2.9 KiB
Protocol Buffer
80 lines
2.9 KiB
Protocol Buffer
syntax = "proto3";
|
|
|
|
package sentry.logs.v1;
|
|
|
|
option go_package = "github.com/cairnobs/cairnobs/proto/sentry/logs/v1;logsv1";
|
|
|
|
// LogIngest is the service agents use to ship batched log records to the
|
|
// ingest service over mTLS. Phase 0: single unary batch push. Streaming
|
|
// (client-streaming for continuous shipping) is a likely Phase 1 upgrade
|
|
// once backpressure/flow-control behavior is characterized.
|
|
service LogIngest {
|
|
rpc PushBatch(PushBatchRequest) returns (PushBatchResponse);
|
|
}
|
|
|
|
// Severity follows OTel's severity number ranges (1-24), collapsed here to
|
|
// the coarse names agents actually need to set. Numeric value stored
|
|
// downstream may be a full OTel severity_number computed by ingest.
|
|
enum Severity {
|
|
SEVERITY_UNSPECIFIED = 0;
|
|
SEVERITY_TRACE = 1;
|
|
SEVERITY_DEBUG = 2;
|
|
SEVERITY_INFO = 3;
|
|
SEVERITY_WARN = 4;
|
|
SEVERITY_ERROR = 5;
|
|
SEVERITY_FATAL = 6;
|
|
}
|
|
|
|
message LogRecord {
|
|
// Unix epoch nanoseconds, set by the agent at time of read (not parse or
|
|
// send time) to preserve original ordering as closely as possible.
|
|
int64 timestamp_unix_nano = 1;
|
|
|
|
// Hostname the agent is running on. Agent fills this from its own config
|
|
// or system hostname; not trusted as an identity claim (mTLS client cert
|
|
// is the identity boundary).
|
|
string host = 2;
|
|
|
|
// Logical service/unit name. For journald sources, this is typically the
|
|
// systemd unit name; for file sources, it comes from agent config.
|
|
string service = 3;
|
|
|
|
Severity severity = 4;
|
|
|
|
// Original, unparsed log line. Always populated, even when structured
|
|
// fields below are also present, per the schema-on-read fallback
|
|
// requirement in CLAUDE.md.
|
|
string message = 5;
|
|
|
|
// Structured fields extracted by the agent's parser (e.g. RFC 5424
|
|
// syslog header fields), plus source-provided fields (e.g. Windows
|
|
// Event Log's winevt.event_id/winevt.provider/winevt.channel). Empty
|
|
// when the raw-passthrough fallback fires and the source added nothing.
|
|
map<string, string> attributes = 6;
|
|
|
|
// Stable per-record identifier, used to join Tantivy full-text search
|
|
// hits back to their ClickHouse row (Phase 1). Always empty as sent by
|
|
// the agent — ingest's PushBatch handler assigns this server-side,
|
|
// once, before producing to Redpanda, since both the ClickHouse-writer
|
|
// consumer and the Tantivy-indexer consumer read the same Redpanda
|
|
// messages and need to agree on the same ID for the same record. See
|
|
// /ingest/README.md.
|
|
string record_id = 7;
|
|
}
|
|
|
|
message PushBatchRequest {
|
|
// Agent-assigned identifier for dedup/idempotency on retry. Ingest may
|
|
// use this to avoid double-writing a batch if a retry follows a
|
|
// timeout on an actually-successful push.
|
|
string batch_id = 1;
|
|
|
|
repeated LogRecord records = 2;
|
|
}
|
|
|
|
message PushBatchResponse {
|
|
// Number of records ingest accepted. Phase 0: batches are all-or-nothing,
|
|
// so this equals len(records) on success. Partial-acceptance semantics
|
|
// are not implemented yet.
|
|
uint32 accepted = 1;
|
|
}
|