ソリューション

アクセス ログ

By default Jira will ship with Tomcat's access log valve enabled.  This is set within server.xml:

<Valve className="org.apache.catalina.valves.AccessLogValve" pattern="%a %{jira.request.id}r %{jira.request.username}r %t &quot;%m %U%q %H&quot; %s %b %D &quot;%{Referer}i&quot; &quot;%{User-Agent}i&quot; &quot;%{jira.request.assession.id}r&quot;"/>

Here is an example of an user access Jira's dashboard:

0:0:0:0:0:0:0:1 673x575x1 admin [15/Mar/2019:11:13:32 -0700] "GET /secure/RapidBoard.jspa?rapidView=3&useStoredSettings=true HTTP/1.1" 200 12078 121 "http://localhost:8080/secure/Dashboard.jspa" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36" "hehlph"

• Here we can see that the "admin" user had accessed an Agile board in Jira on 15/Mar/2019
• There's a lot more information to grab here, but we'll only focus on the users here.

Unique users per day

With the details above from the access logs, here is an example of how it can be parsed to determine how many unique users are accessing Jira per day:

$ awk '{print $3}' access_log.2019-03-14 | sort | uniq
-
admin
testuser
dchan
joeblack
scrooge

• Note that the "-" is an anonymous user.  This could be an user access Jira for the first time and has not yet logged in.  Or even Jira making a call to itself for some additional resources for a previous page load request.
• If you want to extend the time range, simply include log files for each extra day.