I personally think C is the way to go. Selecting the specific service on the Configuration page sounds like the most logical way to find related log messages.
That's a good point. But I'm not sure if that's the most efficient approach. Wouldn't it be better to try and find the logs directly related to the errors shown in the graph?
I agree, option C doesn't seem very relevant. Option D, on the other hand, might be worth considering. Selecting the machine the service is running on could give you access to the relevant log files.
Hmm, I'm not sure about option C. Using the Configuration page to select the service doesn't seem directly related to finding the log messages for the errors. That seems like a bit of a detour.
Yeah, that makes sense. But option B also seems like a good approach. Double-clicking on the spikes in the graph could directly show you the related log messages, which could be more efficient.
Okay, let's start with option A. Using the options on the left side of the Logs page does seem like a logical way to find the related log messages. That way, you can filter down to the specific errors shown in the graph.
Hmm, this is an interesting question. I think the key here is to find the specific log messages associated with the errors shown in the graph. Let's go through the options and see what makes the most sense.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Merilyn
7 months agoInes
7 months agoArlette
7 months agoRonald
7 months agoElza
7 months agoYun
7 months agoBette
8 months agoRaul
8 months agoPenney
8 months agoHerminia
8 months agoRonny
8 months agoRuthann
8 months ago