mirror of
https://github.com/hanzoai/o11y.git
synced 2026-10-15 12:58:33 +00:00
zeekay
c3dc2f1ecf
HIP-0132 unified o11y_logs, o11y_traces and o11y_metrics into one `event`
database and dropped them. The commit that restored the reads repointed
three files and said so; it was thirty. The rest went on naming databases
that no longer exist, so trace funnels, the Kafka and queue panels, the
v3/v4 logs and traces builders and the PromQL adapter each answered
Code: 81 UNKNOWN_DATABASE, and the golden tests agreed with them because
they pinned the same dead SQL.
pkg/telemetryplane is the one address for the name, imports nothing, and
is reachable from every depth that needs it. Its test walks the tree and
fails the build on a literal that names a dropped database, tests
included — a golden encoding broken SQL is a second vote for the bug, not
coverage.
Two service views turned a failed read into an offer to instrument an
already-instrumented application. A failure now shows the failure, and
onboarding is offered on a successful empty read.
Cherry-picked from salvage/blue-wt-o11y-readers 83ecbec03c.
19 lines
796 B
Go
19 lines
796 B
Go
package telemetryaudit
|
|
|
|
import "github.com/hanzoai/o11y/pkg/telemetryplane"
|
|
|
|
// DBName is NOT the event plane. o11y_audit holds the audit trail, which has a
|
|
// different retention and a different access gate from telemetry and was not in
|
|
// HIP-0132's scope. The name is spelled in pkg/telemetryplane with the plane and
|
|
// the other survivors.
|
|
const (
|
|
DBName = telemetryplane.AuditDBName
|
|
AuditLogsTableName = "distributed_logs"
|
|
AuditLogsLocalTableName = "logs"
|
|
TagAttributesTableName = "distributed_tag_attributes"
|
|
TagAttributesLocalTableName = "tag_attributes"
|
|
LogAttributeKeysTblName = "distributed_logs_attribute_keys"
|
|
LogResourceKeysTblName = "distributed_logs_resource_keys"
|
|
LogsResourceTableName = "distributed_logs_resource"
|
|
)
|