RTC3 - monitor capabilities
4 answers
1. Use Tomcat access log or WebSphere Security Auditing. This will allow you to capture who is authenticating and with a little scripting be able to determine peak concurrency/audits. Note: you will need to tune these to turn down the verbosity! They are quite verbose by default.... We use this extensively on our production servers at oncloudone.net
2. Use something like splunk.com or sumologic.com - at least that is what I'm looking into! It's on my list for our customers at oncloudone.net
2. Use something like splunk.com or sumologic.com - at least that is what I'm looking into! It's on my list for our customers at oncloudone.net
Hi,
@Benjamin.Chodroff
Thanks for the reply.
Can you be more specific. We looked at the tomcat logs and found no evidence for user login.
Which log file to monitor?
Also, do we need to tune the log level in order to get this information?
If you can send me an example it will be very valuable.
Last thing: I think it should be introduced within the jazz platform and without the need to script it.
Thanks
@Benjamin.Chodroff
Thanks for the reply.
Can you be more specific. We looked at the tomcat logs and found no evidence for user login.
Which log file to monitor?
Also, do we need to tune the log level in order to get this information?
If you can send me an example it will be very valuable.
Last thing: I think it should be introduced within the jazz platform and without the need to script it.
Thanks
Comments
Daniel Toczala
FORUM MODERATOR / JAZZ DEVELOPER Oct 14 '12, 7:52 p.m.