Best Practices for Reporting and Performance Analytics Upgrades (Lener)

[Adam Stout]

Before you upgrade

1. Review the Performance Analytics, Reporting, and Dashboard release notes for the version you are upgrading to

• Kingston
• Jakarta
• Istanbul

 

On Upgraded Sub-Prod

1. Test any custom visualization or custom interactive filters
2. Run all active jobs (excluding on-demand) and look for any new errors
3. Check insert counts and run times pre and post upgrade to identify any significant changes.
4. Starting with Kingston, review the diagnostics on a sub prod prior to upgrading to prod)
5. Review the application indicators (OOTB and Custom) with application owners to ensure everything is still relevant.
6. Review new content packs, we keep adding more and more and more (which is awesome but doesn't do any good if no one looks at it)

 

Post Upgrade

1. Dashboard Owners should review their dashboards after the initial post-upgrade collection
2. Review the PA Solution Library (activate via plugin) to review updates and new content with the new release. It also provides descriptions of the dashboard content, with screenshots.

[Uncle Rob]

Came for the reporting knowledge... stayed for the discovery of "Document" post type, which apparently has a whole other rating system on top of like/bookmark.

This is like the 3rd thing I've learned from you completely by accident this week.

#Synergy #NowBros

[Pierre P_ Mouri]

@Adam Stout thank you for these best practices.

Would you say these best practices are still applicable 3 years later?

One thing I would add is leveraging ATFs to test some of the custom content, as was covered over the summer in PA Office Hours (link).