Can HumDay connect to Google Cloud Logging?

Yes. HumDay reads Google Cloud Logging's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 39 operations are documented.

Do I need to write code to automate Google Cloud Logging?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Cloud Logging account.

What can HumDay do in Google Cloud Logging?

24 of the 39 documented operations change something in Google Cloud Logging, and 15 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Cloud Logging account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Cloud Logging is held behind that approval.

Automate Google Cloud Logging

HumDay reads Google Cloud Logging’s own published API description and derives 39 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Cloud Logging is

Writes log entries and manages your Cloud Logging configuration.

API host: logging.googleapis.com

What HumDay can do in Google Cloud Logging

24 documented operations change something in Google Cloud Logging.

POSTCreates a new exclusion in the Default sink in a specified parent resource./v2/{parent}/exclusions
PATCHUpdates a sink. This method replaces the following fields in the existing sink with values from the new sink: destination, and filter.The updated sink might also have a new writer…/v2/{sinkName}
PUTUpdates a sink. This method replaces the following fields in the existing sink with values from the new sink: destination, and filter.The updated sink might also have a new writer…/v2/{sinkName}
PUTCreates or updates a logs-based metric./v2/{metricName}
POSTAsynchronously creates a linked dataset in BigQuery which makes it possible to use BigQuery to read the logs stored in the log bucket./v2/{parent}/links
POSTCreates a sink that exports specified log entries to a destination./v2/{parent}/sinks
POSTCreates a view over log entries in a log bucket./v2/{parent}/views
POSTCreates a log bucket that can be used to store log entries./v2/{parent}/buckets
POSTCreates a logs-based metric./v2/{parent}/metrics
POSTCreates a log bucket asynchronously that can be used to store log entries.After a bucket has been created, the bucket's location cannot be changed./v2/{parent}/buckets:createAsync
POSTCopies a set of log entries from a log bucket to a Cloud Storage bucket./v2/entries:copy
POSTStreaming read of log entries as they are ingested./v2/entries:tail
POSTWrites log entries to Logging./v2/entries:write
DELETEDeletes a view on a log bucket./v2/{name}
PATCHUpdates a view on a log bucket./v2/{name}
DELETEDeletes all the log entries in a log for the Default Log Bucket./v2/{logName}
DELETEDeletes a sink. If the sink has a unique writeridentity, then that service account is also deleted./v2/{sinkName}
DELETEDeletes a logs-based metric./v2/{metricName}
POSTStarts asynchronous cancellation on a long-running operation./v2/{name}:cancel
POSTUndeletes a log bucket./v2/{name}:undelete
POSTUpdates a log bucket asynchronously.If the bucket has a lifecyclestate of DELETEREQUESTED, then FAILEDPRECONDITION will be returned.After a bucket has been created, the bucket's l…/v2/{name}:updateAsync
PATCHUpdates the Log Router settings for the given resource.Note: Settings for the Log Router can currently only be configured for Google Cloud organizations./v2/{name}/settings
PATCHUpdates the Log Router CMEK settings for the given resource.Note: CMEK for the Log Router can currently only be configured for Google Cloud organizations./v2/{name}/cmekSettings
POSTLists log entries. Use this method to retrieve log entries that originated from a project/folder/organization/billing account. For ways to export log entries, see Exporting Logs (/v2/entries:list

What HumDay can read from Google Cloud Logging

These are the operations a schedule or a trigger can watch.

GETGets the latest state of a long-running operation./v2/{name}
GETGets a sink./v2/{sinkName}
GETGets a logs-based metric./v2/{metricName}
GETLists the descriptors for monitored resource types used by Logging./v2/monitoredResourceDescriptors
GETLists links./v2/{parent}/links
GETLists sinks./v2/{parent}/sinks
GETLists views on a log bucket./v2/{parent}/views
GETLists information about the supported locations for this service./v2/{name}/locations
GETLists log buckets./v2/{parent}/buckets
GETLists logs-based metrics./v2/{parent}/metrics
GETLists operations that match the specified filter in the request./v2/{name}/operations
GETLists all the exclusions on the Default sink in a parent resource./v2/{parent}/exclusions
GETLists the logs in projects, organizations, folders, or billing accounts./v2/{parent}/logs
GETGets the Log Router settings for the given resource.Note: Settings for the Log Router can be get for Google Cloud projects, folders, organizations and billing accounts./v2/{name}/settings
GETGets the Logging CMEK settings for the given resource.Note: CMEK for the Log Router can be configured for Google Cloud projects, folders, organizations and billing accounts./v2/{name}/cmekSettings

How automating Google Cloud Logging works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Cloud Logging account.
Grant access, then go live. You approve the specific Google Cloud Logging operations it may use — and only those.