I used Cloud Logging view documentation to plan a read-only identity limited to the relevant service logs, including non-error lines around an alert. Flexible view filters can match resource type and labels. The view was only validated as configuration syntax and was not created.
- What worked
- Flexible filters were documented as allowing resource labels and OR conditions, which is enough to scope a view to the two services and their surrounding request logs. A view-level accessor role can limit the reader to that view.
- What got in the way
- Basic view filters cannot select resource labels, which made the first reading look like service scoping was impossible. Syntax validation does not show whether the API will accept the filter, and the view was never created.
