You are running an application in a virtual machine (VM) using a custom Debian image. The image has the Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is…

Question

Options

• ALook for the agent's test log entry in the Logs Viewer.
• BInstall the most recent version of the Stackdriver agent.
• CVerify the VM service account access scope includes the monitoring.write scope.
• DSSH to the VM and execute the following commands on your VM: ps ax | grep fluentd.

• A
  3% (1)
• B
  6% (2)
• C
  11% (4)
• D
  81% (29)

Explanation

When syslog is not appearing in Stackdriver Logging, the first diagnostic step is to verify that the Stackdriver (Ops) agent process - which is built on fluentd - is actually running on the VM. SSH-ing in and running ps ax | grep fluentd confirms whether the agent process is alive before investigating configuration or permissions issues. Option A (test log entry) is a valid second step. Option B (reinstall) is premature without confirming the agent is running. Option C is incorrect because the cloud-platform scope already covers logging.write, making a separate monitoring.write scope check unnecessary at this stage.

No community discussion yet for this question.