Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location
Mob_nav_barsMENU

IBM Exam C1000-150 Topic 6 Question 59 Discussion

Actual exam question for IBM's C1000-150 exam
Question #: 59
Topic #: 6
[All C1000-150 Questions]

What can be done to generate a higher level of detail if the operator logs are not detailed enough?

Show Suggested Answer Hide Answer
Suggested Answer: D

To generate a higher level of detail in operator logs, you can configure a detailed operator trace in a ConfigMap. This allows you to specify the level of logging for different components of the operator and can provide more information about the operator's behavior. The level of logging can be set to 'debug', 'info', 'warning' or 'error' in the ConfigMap. You can access the ConfigMap by using the 'oc edit configmap' command and then editing the 'loglevel' field.

It's also important to note that there are other ways to troubleshoot issues with operators and their logs, such as running the 'oc logs' command on the operator pod, or using the 'oc adm must-gather' command to collect cluster state and diagnostic information.


https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/troubleshoot/troubleshoot_logging.html

https://docs.openshift.com/container-platform/4.6/operations/troubleshooting/troubleshooting-logging.html

https://docs.openshift.com/container-platform/4.6/operations/troubleshooting/debugging-operators.html

by Art at Aug 03, 2025, 01:08 PM

Limited Time Offer

25%

Off

Get Premium C1000-150 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Leonora
3 days ago
I think increasing the verbosity in the Ansible log could help, but I'm not entirely sure if that's the best approach for operator logs specifically.
upvoted 0 times
...
Latanya
9 days ago
Configuring a detailed operator trace in a ConfigMap sounds like it could be the most comprehensive solution, but I'll need to research how to do that properly.
upvoted 0 times
...
Haley
14 days ago
Increasing the verbosity in the Ansible log could be worth a try, but I'm not sure if that's the most direct way to get the level of detail we need.
upvoted 0 times
...
Bettye
20 days ago
Specifying the image for the oc adm must-gather command seems like a promising option. I'll make sure to double-check the syntax on that.
upvoted 0 times
...
Lynelle
25 days ago
Okay, let's see. The logs command on the operator pod could be a good start, but I'm not sure if that's the best approach here.
upvoted 0 times
...
Malinda
1 months ago
Hmm, this looks like a tricky one. I'll need to think through the options carefully.
upvoted 0 times
...
Loren
2 months ago
I prefer specifying the image when running the oc adm must-gather command.
upvoted 0 times
...
Krissy
2 months ago
I like C. Increasing the verbosity in the Ansible log is a great way to get more information without too much hassle.
upvoted 0 times
...
Wava
3 months ago
I agree with Natalie, that could provide more detail.
upvoted 0 times
...
Shenika
3 months ago
Option B seems the way to go. The must-gather command can really help us get the detailed logs we need.
upvoted 0 times
Ming
1 months ago
B) That's a good point, using the must-gather command can provide us with the necessary details.
upvoted 0 times
...
Blythe
2 months ago
D) Configure a detailed operator trace in a ConfigMap.
upvoted 0 times
...
Ceola
2 months ago
B) Specify the image when you run the oc adm must-gather command.
upvoted 0 times
...
...
Natalie
3 months ago
I think we should run the logs command on the operator pod.
upvoted 0 times
...

Save Cancel