DVCS Stats
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Environment
Jira Data Center 9.8.0+
Intro
DVCS has a number of statistics written to the primary Jira log file (atlassian-jira.log*). Starting with Jira 10.4.0, these statistics are now written to a dedicated log file (atlassian-jira-stats.log*). These are logs which contain aggregated information of what is happening in DVCS, which is expensive to log for every event, but may be very useful when determining how crucial different parts of DVCS perform: processing internal events represented in message queue, handling inbound traffic (i.e. webhooks) and generating outbound traffic (initiated by DVCS to git providers). DVCS stats inherit Jira-Stats concept and is providing structured information every 5 minutes in log file (atlassian-jira.log*). Logs can be divided to two types - "snapshot" presenting aggregated information for last 5 minutes and "total" representing all measured statistics from start of Jira instance.
Why we do this :
detect problems as they occur and capture sufficient information to help analyze the problem more quickly
detect problematic interactions with internal components before they cause acute problems
Types of stats logs
Note that DVCS stats are being added incrementally sinceJSW 9.8.0. The list below describes the latest set of available statistics.
All stats have common prefix [JIRA-STATS] which is followed by second prefix always describing area of monitoring. By convention it will always hold
Stats prefix | Description | Since | More |
|---|---|---|---|
[JIRA-STATS] [DVCS-MESSAGE] | Stats related to internal event processing system. Every event is presented as message, placed in queue and consumed. | JSW 9.8.0 | |
[JIRA-STATS] [DVCS-HTTP] | Stats related to http traffic which is deducted to two separate streams - inbound and outbound traffic. | JSW 9.8.0 | |
[JIRA-STATS] [DVCS-PERFORMANCE] | Stats related to performance of adding git organisations or updating existing. | JSW 9.8.0 |
For more information about Jira-Stats check Jira stats logs.
Troubleshooting performance with Jira Stats and DVCS Stats
Please review the related KB article to check how stats-logs (metrics) can be used to troubleshoot different performance problems: Troubleshooting performance with Jira Stats
Statistics configurations
Currently we have two Jira System Properties which can be set up for custom configurations - snapshot stats time interval and dvcs.topn properties.
Snapshot time interval is set to 5 min by default.
By passing this param period of stats can be changed to 5, 15, 30 or 60 minutes. More detailed information can be found here : Setting snapshot time interval.
-Dcom.atlassian.jira.stats.logging.interval=interval5min (default)
Second Jira System Property can preconfigure dvcs.topn parameters which are observed.
By passing this param statistic example of topn fields in can be changed. Default value is set to 10 but can be any positive number.
-Dcom.atlassian.jira.stats.dvcs.topn.repositories=20
Was this helpful?