I would go with Sitecore PowerShell Extensions. It supports your version as well.
My idea is to run query and process all items you want to check.
In the past I used something like this to compare revisions between master and web database:
$webItem = Get-...
I figured out the problem. Turns out I had Sitecore.Analytics.Processing.Aggregation.Services.config and Sitecore.Analytics.Processing.Services.config files disabled. I had disabled them during the install of another module and never re-enabled them. Once I re-enabled them then the reporting database rebuild worked fine.
Continuous Updating is automatically configured. It is the process of xDB which takes interactions that have just ended, out of shared session, into the repository, and then processed and aggregated against.
It starts as soon as Sitecore initializes and runs until the the server is turned off. In most distributed environments, a collection of server roles ...
First Method (recommended):
Install the Analytics Database Manager version 3.0
When Analytics Database Manager is installed, access the application from the Sitecore
Go on the "REMOVE OLD DATA" tab, select the desired options and click start.
Delete your MongoDB Databases related to the Sitecore instance.
Replace the Reporting ...
The [Unknown page] entries may appear due to following reasons:
Items may have been deleted which were already tracked.
Pages are opened and tracked which are not Sitecore items e.g. You created a test.aspx page in root folder and open it, This page does not have a corresponding item in Sitecore and will show as Unknown.
You can check URLs and Names of ...
To be able to insert new fields into the analytics index, you should have the following:
The crawler inherits from the ObserverCrawler<T> type. The generics type identifies the kind of IIndexable object the crawler handles. For example, one of the crawler handles visit objects and another crawler handles ...
This is very nice solution that I implemented in my project:
In the content editor the left margin of the content tree is known as gutter. In this area we can show a icon that can be used to display the status of item i.e published or not published. For this you have to create a Custom GutterRenderer Class:
public class PublishStatusGutter : GutterRenderer
It might be worth having a look into the publishing queue. This is the piece that keeps track of every change made in Sitecore and is used by the "Incremental Publish" option.
There is even an API to use:
IdList queue = Sitecore.Publishing.PublishManager.GetPublishQueue(startDate, ToDate, Context.CurrentDatabase)
The publish queue will give you a list of ...
According to the Official Sitecore Documentation, there is a note that reads
You can only run the RebuildReportingDB.aspx and
RedeployMarketingData.aspx pages from a content management server.
However, in a distributed environment, where you have the content management and processing/aggregation servers separated, you should not be running this on the ...
These reports are made from the aggregated xdb data.
You can tweak the aggregation and processing intervals to make sure your data is put to the reporting database more frequently. You need to alter the following setting value for aggregation agents: <Interval>0.00:00:15</Interval>
Please refer to this guideline from official Sitecore ...
I've followed this process a number of times and haven't hit any ongoing issues yet.
The (Waiting to receive to data status) message is displayed for as long as the timer setting is set in the ...
There is KB article for similar problem, The may occur when a contact submits a particular web form created using the WFFM module two or more times.
Please see below link -
and there is good blog as well by Chaturanga - https://sitecorefootsteps.blogspot.in/2015/06/sitecore-8-wffm-data-aggregation-error.html
I have applied the hotfix as instructed by George Tucker and increased the number of history workers as instructed by Chris Auer, in my case I have raised from 1 to 500. I'm getting much better speed now, around 1.500 items per minute! I have no idea if the hotfix had any role on this because I did both things before running the rebuild again.
Sitecore itself stores the raw analytics data in Mongo, then continually processes the data into a SQL database to make it easier to report on. You can do the same thing, depending on how fresh you need the data to be.
If it needs to be up to date all the time, consider adding a processor to your xDB Aggregation system. This piggy-backs on the built-in ...
Brief Problem Description
When data have been captured in the MongoDB, on session end, data will be aggregated to the reporting database through Aggregation Pipelines.
Your issue is with the following pipelines:
<processor type="Sitecore.WFFM.Analytics.Aggregation.Processors.FormSummary.FormSummaryProcessor, Sitecore.WFFM.Analytics" patch:...
That data is in the sitecore_analytics_index. It is not in the analytics model for you to pull from. You are going to have to make a call into the index to get that data for each of your contacts.
When you look at Experience Profile, the data you see if coming from an API call to /sitecore/api/ao/v1/aggregates/latest-visitors.
Tracking that back to the ...
The quick and dirty way that I do it in dev on a regular basis is to:
Replace your reporting database with a new DB from the sitecore zip file /databases.
Using robomongo, log into Mongo and delete your xDB databases. ([yoursite]_analytics, [yoursite]_tracking_contact, [yoursite]_tracking_live, [yoursite]_tracking_live).
When you visit the site for the ...
Tracked pages have an ItemId field that is saved to the Collection database. During the generation of reports, all information about the page will be fetched from the corresponding Sitecore item. In case there is no associated item in the content tree, [unknown page] will be shown.
This will become a problem when you are tracking page hits that don't have a ...
In the SQL based versions of Sitecore (i.e. 7.2 and lower) the Dropout reports were available from the WFFM Form Reports section.
Unfortunately on the xDB/Mongo verions of Sitecore (7.5 onwards) this report does not exist and there is no out of the box solution available to view this data, even in the latest version.
The form dropout data is captured, ...
Go to your Azure Sitecore Reporting instance and select "Application settings" under the Settings menu. Under "Application settings" on the right, add a new "APP SETTING NAME" called WEBSITE_LOAD_CERTIFICATES as shown in image below. The value will be your certificate thumbprint. It is still hazy why this needs to be done especially since other facet queries ...
You will want to use Fact_PageViews in the Reporting database, which should contain an Item Id, representing the page that someone has visited. Keeping in mind that this data will always be old and not real time, since data is collected by xDb and then aggregated into this data store.
Page Event Definitions
These are stored under /sitecore/system/Marketing Control Panel/Events
When you say "Custom Page Events" you would be talking about custom ones that exist here. There are several out of the box page events such as "Page View".
As with any item in the /sitecore/system/Marketing Control Panel area, these will only ...
Apparently the requests come from the sitecore_suggested_test_index. With the correct filter on the logs we could see that the start of the calls was always preceded by Job started: Index_Update_IndexName=sitecore_suggested_test_index.
Sitecore has a task that schedules the rebuild/update of the suggested test index that can be found in /sitecore/system/...
Content delivery should be unaffected, as you stated, unless you're doing something custom and accessing analytics data from front-end code. Reporting could be extremely slow, depending on the quantity of data in your DB.
Indexes are generally disposable; they aren't the canonical source of any data. Once you rebuild the index as you describe, the index ...
After spending sometime I have noticed that I made a mistake(tags were not closed properly) while updating "TimeToClearStorage" setting in Sitecore.Analytics.Processing.Aggregation.config which broke the config so "RebuildReportingDB.aspx" was throwing above error.
For rebuilding reporting database Sitecore recommends to create a fresh analytic DB (...
In terms of what we are supposed to do now, I'm not sure.
As for the Site Health, it's still there but it has been hidden. There is a tutorial on how to get it back.
And also, how to trigger the 404 reporting
I will be interesting what information @Dmytro and @pete-navarra have, they have a lot of knowledge xDB as well. But I have never found a concise resource for how to write analytics in Sitecore. I spend most of my time talking in the Sitecore Slack channel, decompiling Sitecore dlls and open source GitHub projects. We need someone to write a book or Sitecore ...
It may be a bit late for an answer but I have been having this type of issue recently.
To be able to fix the issue, I have proceed as follows
Check log if there are any errors. If data are not being entered, this may be because there is an error such as Exception when storing an aggregation result into reporting database. Item will be postponed and retried ...
Even though <untrackedPages> can be used to address your issue, I'd consider skipping the entire execution of request for *.js, *.map and fonts resources by using IgnoreURLPrefix in your web.config
<setting name="IgnoreUrlPrefixes" value="/sitecore/default.aspx|/trace.axd|/webresource.axd|/sitecore/shell/Controls/Rich Text Editor/Telerik.Web.UI....
Extracting the inputs from Chris Auer and Richard Hauer, consolidating below the best fit solution in our scenario.
As a temporary solution we have built MongoDB scripts on Interaction collection for all the data required from Mongo. Since using MongoChef as GUI tool we are also able to export the data in CSV format. Imported the CSV in a SQL table and ...