slug: google-cloud-logging provider: Google Cloud Logging generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 6 edges: - tag: Entries:list spec_file: google-cloud-logging-entries-list-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.8 evidence: POST /v2/entries:list listLogEntries List log entries; schema LogEntry reason: Querying log entries from running systems is core log-based observability, making the running service understandable in production. - tag: Entries:tail spec_file: google-cloud-logging-entries-tail-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.8 evidence: POST /v2/entries:tail tailLogEntries Tail log entries reason: Real-time tailing of log streams is live production log observability. - tag: Entries:write spec_file: google-cloud-logging-entries-write-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.8 evidence: POST /v2/entries:write writeLogEntries Write log entries; schema LogEntry reason: Ingesting application and system log entries is the instrumentation side of Observability Management (logs/metrics/traces). - tag: Google Cloud Logging API spec_file: google-cloud-logging-google-cloud-logging-api-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: '"Google Cloud Logging API v2 writes log entries and manages Cloud Logging configuration including buckets, sinks, exclusions, log-based metrics"; operations "Get sink", "Delete sink" with schema LogSink' reason: Operations manage Log Router sinks — the routing/configuration surface of a production log management service. That is observability tooling (logs, metrics) for running services, not a business-domain capability. Mapped to Observability Management; some chance the intended home is generic IT Operations Management, hence moderate confidence. - tag: Sinks spec_file: google-cloud-logging-sinks-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: '"List sinks", "Create sink" on /v2/{parent}/sinks, schema LogSink; spec "manages Cloud Logging configuration including buckets, sinks, exclusions, log-based metrics"' reason: Log sink lifecycle for a real-time log management service = log pipeline/observability configuration. Mapped to Observability Management; the alternative reading is plain IT operations, so not maximal confidence. - tag: Entries:copy spec_file: google-cloud-logging-entries-copy-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.7 evidence: POST /v2/entries:copy copyLogEntries Copy log entries reason: Copying log entries between log storage destinations is log data handling within a log management service — Observability Management.