Google Cloud Fundamentals: Getting Started with Deployment Manager and Cloud Monitoring Reviews

Go S. · Reviewed almost 6 years ago

Viktor T. · Reviewed almost 6 years ago

Tanuj R. · Reviewed almost 6 years ago

Adrian M. · Reviewed almost 6 years ago

Viktor T. · Reviewed almost 6 years ago

ok

Praveen K. · Reviewed almost 6 years ago

Pavel M. · Reviewed almost 6 years ago

Saipranith M. · Reviewed almost 6 years ago

Mathew M. · Reviewed almost 6 years ago

Jerome P. · Reviewed almost 6 years ago

Mathew M. · Reviewed almost 6 years ago

Achraf G. · Reviewed almost 6 years ago

Rubendrababu N. · Reviewed almost 6 years ago

UMAIR M. · Reviewed almost 6 years ago

Viktor T. · Reviewed almost 6 years ago

NA

shashi M. · Reviewed almost 6 years ago

Ashish A. · Reviewed almost 6 years ago

Krzysztof B. · Reviewed almost 6 years ago

Dhirajkumar J. · Reviewed almost 6 years ago

SCHARTNER T. · Reviewed almost 6 years ago

Vinayak P. · Reviewed almost 6 years ago

Raveen K. · Reviewed almost 6 years ago

Abdullah A. · Reviewed almost 6 years ago

Could have been fun, but there are some issues: - That 'sed' stuff is sad; itjust emphasizes the immaturity of the deployment tool - the debian image in the deployment file triggers a deprecation warning - The install of the logging and metrics agents fail with ... Failed to start LSB: data collector for Treasure Data. ... I think it did not get a proper service account injected. More data: $ sudo cat /var/log/google-fluentd/google-fluentd.log ... 2020-12-14 15:43:05 +0000 [warn]: Failed to count metrics for uptime. error_class=Signet::AuthorizationError error= "Error code 404 trying to get security access token\nfrom Compute Engine metadata for the default service account. This\nmay be because the virtual machine instance does not have permission\nscopes specified.\n"

Leon W. · Reviewed almost 6 years ago

Kumar V. · Reviewed almost 6 years ago