We were working on Sitecore 10.2 upgrade.
We are not able to see the experience graph, but we can see the graph in our lower environment(UAT) with same database.
Can you help us to find the troubleshooting steps?
6
-
can you see some errors there?– Gaurav AgarwalCommented Dec 28, 2022 at 5:40
-
Check these - sitecore.stackexchange.com/questions/28052/… tothecore.sk/2018/07/11/…– Gaurav AgarwalCommented Dec 28, 2022 at 5:57
-
What is your original Sitecore version? See the detailed Upgrade Guide here: sitecoredev.azureedge.net/~/media/… for additional steps you have to undertake for your xDB configuration and data during the upgrade depending on your current version– Kate OrlovaCommented Dec 28, 2022 at 9:26
-
I don't see any errors in that dashboard and CM server logs. We can see the graph in our lower environment by using the upgraded reporting database. I have already tried the steps given in those link, which suggested by sitecore team in the ticket created with them.– AstleCommented Dec 28, 2022 at 12:54
-
Try to turn on Debug level logging on your CM/CD and then check logs. Some of the analytics calls can be seen only like that. Is it hosted on PaaS or VM? Can you check logs for Reporting role? Are all certificates correct? himynameistim.com/blog/debugging-sitecore-9-analytics-issues– Kamil CCommented Dec 29, 2022 at 8:20
|
Show 1 more comment
2 Answers
A fact that you don't see any errors suggests that this is likely to be a data problem.
I would recommend to rebuild the Reporting database and xDB search index.
The Reporting DB rebuild is a semi-automated process and can be initiated by the pre-built script on CM instance, just open the below link on your CM:
{your_cm_site_domain}/sitecore/admin/RebuildReportingDB.aspx
Read more here.
Once the Reporting DB has been successfully rebuilt you need to manually trigger the rebuild of the xDB search index depending on your search provider. See this article about how to rebuild the xDB index in Solr.
answered Dec 28, 2022 at 16:32
-
1
There were some duplicate items in our Sitecore content tree(Master DB) inside experience analytics folder. We have cleaned up and it is working fine now.