Google Cloud Logging · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Google Cloud Logging Entries:write API

2 actions 2 updates phrasing extends openapi/google-cloud-logging-entries-write-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Google Cloud Logging's API. It is a proposal applied on top of the contract, not a document Google Cloud Logging publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 2

$.info
$.paths['/v2/entries:write'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Google Cloud Logging Entries:write API
  version: 1.0.0
extends: openapi/google-cloud-logging-entries-write-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 1
- target: $.paths['/v2/entries:write'].post
  update:
    x-apievangelist-phrasing:
      intent: Write log entries to Cloud Logging
      effect: write
      questions:
      - Can I send my application's log messages straight to Google Cloud Logging?
      - Is there a dry-run option to test writing log entries without storing them?
      - What happens to the valid entries in a batch if one of them is rejected?
      instructions:
      - text: Write these log entries {entries} to log {logName}.
        slots:
          entries: requestBody.entries
          logName: requestBody.logName
      - text: Do a dry run writing {entries} to make sure they would be accepted.
        slots:
          entries: requestBody.entries
      - text: Write {entries} to {logName}, keeping the valid ones even if some fail.
        slots:
          entries: requestBody.entries
          logName: requestBody.logName
      method: generated
      generated: '2026-10-01'