✅ Why doesn't "Get recent logs" work sometimes?

[LuvsSurfing]

As an admin user, I am trying to understand how to use the "Logs" panel under the Monitor/Setup section (the one with the "spanner"/tools like symbol). When I try to get the recent logs by entering a number in the "Get recent logs" box, it either doesn't let me enter a number, or if I enter a number, sometimes, it doesn't do anything. Can someone explain how to use this panel correctly so I can monitor Xcalar logs?

[nogievetsky]

This screen returns up to 500 recent log entries. It will work if you had activity on the requested node, and requested up to 500 recent log records (otherwise you will be alerted with an error if you click on the blue checkmark to the right of the "get recent logs" number).

Hope this answers your question.

[LuvsSurfing]

Hello!

Thanks for the reply! While browsing the documentation, I found a section in the Xcalar documentation where there's a section called: "Understanding log messages" - see:

https://www.xcalar.com/documentation/help/XD/1.2.3/Content/C_AdvancedTasks/L_UseSetup.htm

After playing with it based on this document, I found that there are two modes: the "get recent logs" mode, and a streaming mode (which is entered if I click on the "Start Monitor Stream" button). These modes are mutually exclusive - so if I am in the streaming mode, latest logs are posted in the window, and keep rolling up as new logs are generated, whereas the "get recent logs" just gets the latest logs one time. If I am in the streaming mode, entering a number in the get recent logs window doesn't do anything or disallows me from entering a number - until I quit the streaming mode by clicking on "Stop Stream".

So maybe I was in the streaming mode, when I posted this question...which disallowed me from entering the number in the "get recent logs" window. Maybe the panel could be made more intuitive (e.g. when I enter the number in the "get recent logs" button, it could warn me that I am in streaming mode...).

-Susan

[nogievetsky]

Thank you for pointing this out. We will submit this to the list of possible enhancements.