Need help with getting Jira user info

[AisM]

Hello,

We are in the process doing some performance testing for our Jira application. For this, we are looking to acquire user workload for a 24hour period for the below simple use cases,- (to name a few)

* No of user cloning issues 

*No of user clicking the Issue EDIT option

*No of users opening Structure

*No of users browsing projects 

*No of users browsing Boards

*No of user Viewing Board

Is there any straight forward way to get this information. Or is there any Plugin available to get this information. Any help is appreciated. 

Thank you

[Tuncay Senturk _Snapbytes_ · Accepted solution]

Hello @AisM ,

Thanks for mentioning me.

I concur with @Nic Brough -Adaptavist- 's points.

It's important to recognize that Jira's primary function is as an issue tracking tool, not a comprehensive user activity monitoring system. As a result, it doesn't inherently offer the specific metrics you're seeking directly within its core features. I'm unsure if there are any third-party apps available on the Atlassian Marketplace that can provide this data, but I'm aware that your organization might be hesitant to adopt new apps.

I apologize if my response didn't fully meet your expectations.

[AisM]

@Tuncay Senturk _Snapbytes_ Thank you the comment :) Yes, we do understand how acquiring these metrics is extremely hard. But, the testing team really want this no matter what, as the current testing set up is hitting the test environments 10 times more than Prod. So, they want a number close to prod for these individual test cases. 

But sadly, I could not find any plugin or app that could help with this. Some suggested getting the info from the DB, but not sure how that would be.

[AisM]

@Tuncay Senturk _Snapbytes_  Thank you for sharing your thoughts on the topic.
I did manage to get some of the metrics from the DB & via Splunk. But am I confident about the accuracy of these numbers, maybe not so much. But, this works for the time being ;)

[Nic Brough -Adaptavist- · Accepted solution]

Jira does not track user activity at that level, it's an issue tracker, not a micro-management tool.

None of those metrics have anything to do with workload monitoring, which leads me to the simple question of "why?".  Why are you trying to look at these numbers?

[AisM]

@Nic Brough -Adaptavist- We are in the process of migrating projects from a different Jira instance to another one (Initially the organisation had two Jira instances). So, this new migration is gonna cause a huge increase in the number of users accessing Jira , maybe a 3fold increase. 
So, we are currently doing some performance testing in our UAT to check for how the application would behave with that many new number of concurrent users hitting the application.

Hope this explains 

[Nic Brough -Adaptavist-]

None of those metrics are going to help you with performance, none of them are particularly heavy on loading your Jira instance.

The main thing that affects Jira performance is searching.  Not just the "run a filter" stuff, but also the things that call searches without telling the users that they are doing it.  Dashboards are the obvious ones, but boards do it a lot more than you think.

But "board usage" is still not going to tell you anything about performance, and its worse for Cloud systems - Cloud is totally different software, and will try to auto-scale for your usage, so there's no need for you to try to gather numbers on your server - it is of no use when migrating.

[AisM]

@Nic Brough -Adaptavist-  Yes, I can understand where you are coming from and how some of those metrices are not gonna be useful, but from an organization point of view, they need those numbers. 

So, is there any way possible to get that information - atleast for number of users accessing Boards or Dashboards in 24hrs 

[Nic Brough -Adaptavist-]

Why?  Why do they think they need those numbers?  What do they think it will tell them?

The only way you can get those numbers is to run access logging on your proxy server, but you'll find it doesn't tell you anything of any use.

[AisM]

@Nic Brough -Adaptavist-  The org wants to understand how the Jira nodes & SQL servers will perform if the user load performing daily activities increases exponentially. 

Do you think getting this info can be gathered to some extent from the Jira Database, or maybe from a third party monitoring tool (we have Dynatrace)

[Nic Brough -Adaptavist-]

It's going to slow down.  You don't need to look at these usage metrics, they're actually completely the wrong ones to be looking at if you're worried about performance.

Could you explain why you think they might be useful?

[AisM]

@Nic Brough -Adaptavist- To be honest, the management is convinced it is needed to find the node availability during high user traffic & to calculate the response times of each transactions. They want to make sure, its <5sec. So, they need all the user metrics for the most basic use cases..

For create issues in 24hrs & comment added in 24 hrs - We were able to try & get some info from the DB table.

But the other scenarios are quite challenging, how many users clicked on browse projects, boards, dashboards, opened structure . not sure where to start & how to gather the info.

[Nic Brough -Adaptavist-]

Ok, this is not really the best way to be looking at performance, but what you'll need to do is start monitoring the proexy or load-balancer logs for load times.

[AisM]

@Nic Brough -Adaptavist- I did manage to get some of these metrics. Not sure how accurate they are. For those, that involve adding values in the DB (example - add comment, add attachment), I got these directly from the DB. For the others like, "Users clicking dashboard, structure, cloning issue" - got these from Splunk.

Thank you for the insights you provided on the topic. Appreciate your help :) 

[AisM]

Hi @Tuncay Senturk _Snapbytes_ , Hope you are doing well :):) Though I did receive some comments on this ask from Nic, would like to hear your thoughts as well . .

Is there any SQL query that can be used to retrieve info from the DB. Maybe for no. of users adding a comment in 24 hours, or editing an issue in 24hours.