No. It's a web-based service, so "actively connected" isn't really a useful concept.
If someone has a Jira page open in their browser, then you might think that counts as "active". But Jira doesn't care because it's given their browser some information and that's all it needs to do until the next time they make a request. Which might be in the next millisecond, or an hour later.
The best you could do is log the access and read off the last handful of lines to see who last did something, but that's still not going to tell you that Dave has a page open, wandered off for a coffee, comes back 30 minutes later and clicks "commit"
You can look at the "last login" in the list of users as well.
I'm not aware of a Tomcat log particularly, I've always run Jira behind Apache which is usually configured to log most or all hits. (Which does the job of "who's active" quite well for me)
You can also enable access logging in the logging and profiling screens in Jira, but I've not really tried to use that for this sort of thing, so I don't know how suitable it might be
You can tap the Tomcat Valve and get access logging directly from the Application Server but the feedback isn't much more informative than that provided by the standard HTTP logging in JIRA, although for completeness sake the way to implement both solutions is covered in this document: https://confluence.atlassian.com/display/JIRA/User+access+logging
All the best,
There are two approaches I'd use here.....
First is to enable JMX on your Jira server and then get hodl Visual VM. It enables you to get a visual view of all the threads running in Jira. If any of the threads called httPrequest and showing as GREEN, then someone is using Jira. If they all show as yellow, it's quiet.
JMX: https://confluence.atlassian.com/display/DOC/Live+Monitoring+Using+the+JMX+Interface (it's confluence but the details are the same)
Visual VM: visualvm.java.net
The second approach is to do a SQL query to see the last login times, should give you an idea of who to contact.
Here's one we use for MS-SQL, the tricky bit is formatting the millisecond timestamp to something readable, it will be different for any other database flavour,
cast(cwd_user_attributes.attribute_value as bigint) % 1000,
DATEADD(SECOND, cast(cwd_user_attributes.attribute_value as bigint) / 1000, '19700101')) as lastLogin
cwd_user_attributes.attribute_value, cwd_user.user_name, cwd_user.display_name
from "JiraDB"."jira"."cwd_user_attributes", "JiraDB"."jira"."cwd_user"
order by cwd_user_attributes.attribute_value desc
And then, put the announcement banner up to warn people, make it big & RED just before the outage so they can't ignore it.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs