Thank you very much:
What I am doing is using logViewer on the IBM i directly (after a while I could understand the small differences between Linux and qshell) and connecting from a Linux using sshfs and using filebeat to feed these logs to Elastic.
Your proposal of using logViewer in Linux instead of running it from IBM i, sounds very practical, given that it will allows my team to be responsible for it to be up and running, instead of having to split that responsibility with IBM i administrators <-- that's more a practical point that may not apply to other shops.
------------------------------
Daniel Jose Lema Guanziroli
------------------------------
Original Message:
Sent: Wed December 28, 2022 01:49 PM
From: Don Bourne
Subject: logViewer for WAS on IBM i
Hi Daniel,
One possibility is that you could write your logs to a local, but shared directory on your IBM i machine, then use the logViewer command on your Linux machine with the -repositoryDir option to read from that shared directory. Note that it's better not to write your logs directly to a remote filesystem as that could cause latency when writing your logs/trace which could slow down threads that are logging/tracing in your server.
------------------------------
Don Bourne
WebSphere Observability Architect
Original Message:
Sent: Tue December 13, 2022 11:57 AM
From: Daniel Jose Lema Guanziroli
Subject: logViewer for WAS on IBM i
Good day:
Does anyone knows where is the logViewer.sh file located on WAS on IBM i, if there is one? Is there a way of using logViewer remotely from a Linux machine against IBM i installed WAS?
Thank you so much.
------------------------------
Daniel Jose Lema Guanziroli
------------------------------