You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In that article, I would like to share the usage of new functionality from 8.10 Jira DC in the cluster monitoring tab and say thank you to the Atlassian development team. Because previous we do parsing logs, check indexes via Luke, and do testing via benchmark tools.
As we know many recommendation around custom fields creation:
But one problem is unclear, when we need to start to investigate a problem, why is SysOps annoying if we want to add new custom fields, how to measure?
So Atlassian enrolled in 8.10.x the UI and released a feature with the name the more insights for custom fields. It’s part of feature Indexing Stats - cost of indexing custom fields which works for the Server and DC release from 8.1.x (https://confluence.atlassian.com/jirakb/indexing-stats-cost-of-indexing-custom-fields-1002473438.html).
If you are on a DC release, I hope you’re already on it.
Let’s review the feature:
As a result we can find the 10 Total and 10 Snapshot time consuming fields.
Also, I am really happy with that feature which can be exported and do analysis, and do cleanup based on that info.
Based on that info I will review the top time consuming the fields.
Please, be aware that top time consuming fields are related to the one of test installation. Please, do an investigation on your instance before making a conclusion.