google.golang.org/cloud/logging (go): Package logging contains a Stackdriver Logging client suitable for writing logs. For reading logs, and working with sinks, metrics and monitored resources, see package cloud.google.com/go/logging/logadmin.  This client uses Logging API v2. See https://cloud.google.com/logging/docs/api/v2/ for an introduction to the API.  Note: This package is in beta.  Some backwards-incompatible changes may occur.  Use a Client to interact with the Stackdriver Logging API.  For most use cases, you'll want to add log entries to a buffer to be periodically flushed (automatically and asynchronously) to the Stackdriver Logging service.  You should call Client.Close before your program exits to flush any buffered log entries to the Stackdriver Logging service.  For critical errors, you may want to send your log entries immediately. LogSync is slow and will block until the log entry has been sent, so it is not recommended for normal use.  An entry payload can be a string, as in the examples above. It can also be any value that can be marshaled to a JSON object, like a map[string]interface{} or a struct:  If you have a []byte of JSON, wrap it in json.RawMessage:  You may want use a standard log.Logger in your program.  An Entry may have one of a number of severity levels associated with it.  You can view Stackdriver logs for projects at https://console.cloud.google.com/logs/viewer. Use the dropdown at the top left. When running from a Google Cloud Platform VM, select "GCE VM Instance". Otherwise, select "Google Project" and then the project ID. Logs for organizations, folders and billing accounts can be viewed on the command line with the "gcloud logging read" command.  To group all the log entries written during a single HTTP request, create two Loggers, a "parent" and a "child," with different log IDs. Both should be in the same project, and have the same MonitoredResouce type and labels.  - Parent entries must have HTTPRequest.Request populated. (Strictly speaking, only the URL is necessary.)  - A child entry's timestamp must be within the time interval covered by the parent request (i.e., older than parent.Timestamp, and newer than parent.Timestamp - parent.HTTPRequest.Latency, assuming the parent timestamp marks the end of the request.  - The trace field must be populated in all of the entries and match exactly.  You should observe the child log entries grouped under the parent on the console. The parent entry will not inherit the severity of its children; you must update the parent severity yourself.
Keywords: cloud-bigquery|cloud-datastore|cloud-pubsub|cloud-storage|go|golang|google-cloud