Jira indexing-limits 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
Summary
Environment
Jira Data Center 8.22.2 / 9.0.0 / 8.20.12 and later
Jira Stats
Learn more about Jira Stats: Jira stats logs
In Jira 8.22.2 we've introduced Safeguards in Jira DC index. As part of the feature, we've added stats to help you gather information around the indexing of issue-related entities.
Solution
You can search for the stats in the logs by the prefix [JIRA-STATS] [INDEXING-LIMITS].
settings - configuration parameters
maxCommentsIndexed - maximum number of comments per issue that are being indexed
maxWorklogsIndexed - maximum number of worklogs per issue that are being indexed
maxChangeHistoryIndexed- maximum number of change history items per issue that are being indexed
shouldFilterOutUnsupportedFields - if change history items should be filtered out to contain only six supported fields
indexIssueWithRelated - how many times an issue with any related entities (comments, worklogs, change history) index was triggered
indexComments - how many times a comment index was triggered
indexWorklogs - how many times a worklog index was triggered
indexChangeHistory - how many times a change history item index was triggered
indexAll - how many times an issue with all related entities (comments and worklogs and change history) index was triggered
numberOfTimesCommentsLimited - how many times issue comments reindex was limited
numberOfTimesWorklogsLimited - how many times issue worklogs reindex was limited
numberOfTimesChangeHistoryLimited - how many times issue change history items reindex was limited
topIssuesWithLimitedComments - list of top N issues that has the greatest number of comments outside of the indexing limit
topIssuesWithLimitedWorklogs - list of top N issues that has the greatest number of worklogs outside of the indexing limit
topIssuesWithLimitedChangeHistory - list of the N issues that has the greatest number of change history items outside of the indexing limit
Configuration:
settings:
maxCommentsIndexed: default 500, can be overridden with system property: jira.safeguards.indexing.issue.comments
maxWorklogsIndexed: default 100, can be overridden with system property: jira.safeguards.indexing.issue.worklogs
maxChangeHistoryIndexed: default 100, can be overridden with system property: jira.safeguards.indexing.issue.changelogs
shouldFilterOutUnsupportedFields: default true, can be overridden with system property: jira.safeguards.indexing.issue.changelogs.do.not.filter.out.unsupported.fields
set to 0 to disable indexing of a given collection of issue related entities
set to -1 to have no limit when indexing a given collection of related entities (not recommended)
topIssuesWith: for topN stats we have following default values:
default topN stored items: 1000, can be overridden with system property: com.atlassian.jira.issue.index.limits.stats.max.issue.stored
default topN printed items: 10, , can be overridden with system property: com.atlassian.jira.issue.index.limits.stats.max.issue.printed
Indexing-limits stats example:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
[JIRA-STATS] [INDEXING-LIMITS] total stats: duration=PT5M0.445S, statsOverhead=n/a, data=
{
"settings": {
"maxCommentsIndexed": 500,
"maxWorklogsIndexed": 100,
"maxChangeHistoryIndexed": 100,
"shouldFilterOutUnsupportedFields": true
},
"indexIssueWithRelated": {
"value": 427
},
"indexComments": {
"value": 21
},
"indexWorklogs": {
"value": 21
},
"indexChangeHistory": {
"value": 427
},
"indexAll": {
"value": 21
},
"numberOfTimesCommentsLimited": {
"value": 20
},
"numberOfTimesWorklogsLimited": {
"value": 0
},
"numberOfTimesChangeHistoryLimited": {
"value": 0
},
"numberOfComments": {
"count": 20,
"min": 30095,
"max": 30298,
"sum": 605757,
"avg": 30287,
"distributionCounter": {
"0": 0,
"1": 0,
"10": 0,
"100": 0,
"1000": 0,
"10000": 0,
"20000": 0,
"50000": 20
}
},
"numberOfWorklogs": {
"count": 20,
"min": 0,
"max": 0,
"sum": 0,
"avg": 0,
"distributionCounter": {
"0": 20,
"1": 0,
"10": 0,
"100": 0,
"1000": 0,
"10000": 0,
"20000": 0,
"50000": 0
}
},
"numberOfChangeHistory": {
"count": 426,
"min": 0,
"max": 0,
"sum": 0,
"avg": 0,
"distributionCounter": {
"0": 426,
"1": 0,
"10": 0,
"100": 0,
"1000": 0,
"10000": 0,
"20000": 0,
"50000": 0
}
},
"topIssuesWithLimitedComments": {
"TEST-2": 20
},
"topIssuesWithLimitedWorklogs": {},
"topIssuesWithLimitedChangeHistory": {}
}Was this helpful?