Session Logs
Viewing the application's logs output for a specific session
Being able to monitor the application's log outputs is crucial for efficient troubleshooting of your applications. The Session Logs function lets you do just that.
Navigate to the space containing the instance where you want to view logs.
Navigate to the instance containing the application.
Make sure you are in the Current state.
On the sidebar click the Screen button (Applications), which shows you the Application list.
On the row of the application of interest, click ... under Actions.
In the drop-down click SESSIONS.
The screen shows the sessions for the given application.
To review the logs of a specific session, click the ... menu under Actions and click SEE LOGS.
As a security measure, you are only able to see the logs for a specific application session if:
You started the session
OR
The application was run in SHARED MODE for that specific session
This will take you to the Session logs screen. The Application's name and the specific session's ID you are viewing are shown. The log output is shown in a descending order, i.e., the latest logs are shown at the bottom of the output window.
Logs are collected in real time but due to processing, they can be a delayed up to a few minutes until visible on the interface. Also, logs can be retrieved only for the last 7 days.
Log Interface Controls
Show Timestamp
Toggle timestamp visibility in the output
Log messages may or may not have a timestamp in the message itself
Number of lines
Sets the maximum number of lines of logs that is displayed (default = 100 lines of log output)
Filter(s)
After Timestamp - Set a timestamp only on or after which such logs will be shown (default = no timestamp, so show the latest log messages)
Log text - Show logs to only those containing the text specified. Note that:
The filters are applied at different stages:
The timestamp and number of lines filters are applied first (i.e. at the time of query) then,
The text filters are applied in Nuvolos after the logs are retrieved.
For example: there are 150 lines of log output for a given application, the last 100 of which are comprised of:
50 lines with the text
warning30 lines with empty log messages
20 lines that do not contain the relevant text ("warning")
With the default filters, before the
warningtext filter is applied, the last 100 lines of log output will be shown. Whenwarningis typed in the text filter, the text filter is then applied, so the log output displays 50 lines with the relevant text.
Last updated
Was this helpful?