You are using Stackdriver to monitor applications hosted on Google Cloud Platform (GCP). You recently deployed a new application, but its logs are not appearing on the Stackdriver dashboard. You need to troubleshoot the issue. What should you do?
A.
Confirm that the Stackdriver agent has been installed in the hosting virtual machine.
B.
Confirm that your account has the proper permissions to use the Stackdriver dashboard.
C.
Confirm that port 25 has been opened in the firewall to allow messages through to Stackdriver.
D.
Confirm that the application is using the required client library and the service account key has proper permissions.
Why do you complicate stuff.
A is the answer.
Why not D, because if A is not there D is useless. Question says you are using Stackdriver monitoring, not saying you have an agent installed already. You need the agent to export logs. So first thing you'll always see in the agent is there, and running. Next service account, next client libraries.
I hope this clears your doubts.
You are assuming the new application is deployed on compute engine though there is no reference in question that says where the application is deployed.
D - The question states that you are already using Stackdriver for the GCE instance (assuming the agent is already installed). However, the "new" application has issues shipping the logs
The question mention application logs, not only monitoring metrics, so I think "D" is correct.
The stackdriver agent would only provide metrics of resources. I think you need to setup logging "client libraries" on the application in order to have the logs, therefore "D". https://cloud.google.com/logging/docs/reference/libraries
D. Stackdriver agent or Cloud Monitor agent only ships metrics, not log. If opt A change to Ops agent then it will be correct since Ops Agent handles both metrics and log.
https://cloud.google.com/logging/docs/agent/ops-agent/configuration#default
"The Ops Agent collects both metrics and logs by default. You can change this default behavior by configuring the Ops Agent."
https://cloud.google.com/monitoring/agent/monitoring/installation#:~:text=The%20Ops%20Agent%20collects%20both%20metrics%20and%20logs%20by%20default.%20You%20can%20change%20this%20default%20behavior%20by%20configuring%20the%20Ops%20Agent.
A. Store the Terraform code in a version-control system. Establish procedures for pushing new versions and merging with the master.
Using a version-control system such as Git, allows you to store different versions of the code and track changes that are made to it. This allows you to easily roll back to a previous version if necessary, and ensures that all team members are working on the same version of the code. It also allows team members to collaborate on the code and merge changes with the master version. This is the most effective way to share code and maintain versioning, as it provides a centralized location for all code and allows for easy collaboration and management of code changes.
My last message was wrong, this is the good one:
A. Confirm that the Stackdriver agent has been installed in the hosting virtual machine.
To troubleshoot the issue of logs not appearing on the Stackdriver dashboard, you should first confirm that the Stackdriver agent has been installed in the hosting virtual machine. This is because the agent is responsible for sending the logs from the machine to the Stackdriver service
Key sentences for this question:
1. You recently deployed a NEW APPLICATION,
2. If it is a new application you CAN'T assume Stackdriver agent is already installed
B) Wrong this is not a dashboard issue, even do, the first step is check if agent is installed
C) Wrong, port 25 is used for SMTP server
D) Wrong, if you are using GCP, VM, wth..
I think a lot the best answer is B, because the question not suggest the application is running in compute engine, and if the user has dashboard viewer permissions but no logs viewer permissions the problem mentioned in the question can happen
I think A
Troubleshoot legacy monitoring
- agent installed ed run: ps -ax | grep fluentd
- logging test is visible?
- VM API Access scope (ie Full Access scope or Logging Write for logging agent)
- Service account (if not default is used) or credential key
- Application Client library installed
- Exclusion rule exists on Log Router?
- Firewall rule?
The correct answer is A not D..D is mentioning one wrong thing thats why.
https://cloud.google.com/logging/docs/agent/logging/troubleshooting#try-installing
A and D seems correct. I think D is less correct because since you are hosting on GCP, best practice is to not add a service account to the application itself but instead leverage the native logging capabilities of GCP's offerings like GKE, GCP, etc.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
KyubiBlaze
Highly Voted 2 years, 6 months agoMeyucho
7 months, 3 weeks agocsrazdan
1 year, 10 months agoric79
2 years, 5 months agohfudjdn
Highly Voted 2 years, 8 months agoJohnnieWalker
2 years, 8 months agomuthucts
Most Recent 1 week, 4 days agoMeyucho
7 months, 3 weeks agojomonkp
8 months, 1 week agomaxdanny
8 months, 3 weeks agozanhsieh
1 year, 1 month agoJonathanSJ
1 year, 6 months agoJonathanSJ
1 year, 6 months agohanweiCN
1 year, 7 months agoWhyIronMan
1 year, 8 months agojuancambb
1 year, 8 months agossmb
1 year, 9 months agoeliC
2 years, 1 month agoric79
2 years, 4 months agoSekierer
2 years, 6 months agoTNT87
2 years, 7 months agonot_thanos
2 years, 7 months ago