- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2022 02:38 AM
Hi team,
I want to understand the following items
- Does ServiceNow provide real-time reporting in their analytics?
- If yes, does this real-time reporting work for all the tables? or is it restricted to certain tables?
- if not, what's that syn time of the data in the service, not analytics?
-i.e. If a user creates a ticket in the tool, how much time would it take for the analytics module to reflect the data?
Solved! Go to Solution.
- Labels:
-
Reporting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2022 04:07 AM
Further information:
A senior support engineer informs me that only a few of the largest customers are using read replicas. So unless your tables are running well into the millions of active records each, you are unlikely to have it.
Even if you do have read replicas, if you were experiencing reporting lags because of them, this would be an issue and Support would attempt to resolve it.
As far as we know, no other table than a read replica can even potentially exist as an intermediary between the report and the backend. And in any case, no lag is expected.
So tl;dr: The report refers to the same live fact table in the backend.
Regarding historical data:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 06:27 AM
meher,
Regarding your original question, a developer writes:
If seeing the new number is critical then customer can use the record watcher functionality to update single score reports on the fly. This is almost immediate.
https://community.servicenow.com/community?id=community_question&sys_id=971f83e1dbdcdbc01dcaf3231f961927
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2022 04:07 AM
Further information:
A senior support engineer informs me that only a few of the largest customers are using read replicas. So unless your tables are running well into the millions of active records each, you are unlikely to have it.
Even if you do have read replicas, if you were experiencing reporting lags because of them, this would be an issue and Support would attempt to resolve it.
As far as we know, no other table than a read replica can even potentially exist as an intermediary between the report and the backend. And in any case, no lag is expected.
So tl;dr: The report refers to the same live fact table in the backend.
Regarding historical data:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2022 04:18 AM
Amazing piece of information - Thanks for helping me jeffrubinoff