Out of box Analytics are not reflecting accurate numbers?

Jason_MeyerJason_Meyer Customer Adept IT Monkey ✭✭

So, trying to get value from the Analytics 'dashboard' that is out of box.  Is there any documentation on what these views are showing?   I look at "Top Affected Users" and am looking at "Top Affected Users with Most Incidents" and then I filter it to YESTERDAY.  And I get some information, but if I look at my data and pull all Incidents from yesterday and determine what user has the most, what is reported on the Analytics dashboard doesn't match up.

It only shows one "Affected User" who is showing three incidents.  They did have three incidents, but there were two other 'affected users' that I have INCIDENTS for that are not showing up in the Analytics dashboard.

Any existing documentation on this specifically or help or thoughts?

Answers

  • Tom_HendricksTom_Hendricks Customer Super IT Monkey ✭✭✭✭✭
    I believe there is a delay on when the CiresonAnalytics DB that some of them point to gets updated.  That might be the issue here.

    We use our own dashboards that point directly at the source data, for this reason and others.  I'm still trying to figure out the usefulness of the Analytics DB, frankly.  The dashboards themselves, on the other hand, are a wonderful addition when we have them pointing at better data.
  • Jason_MeyerJason_Meyer Customer Adept IT Monkey ✭✭
    Thanks Tom, any idea what the delay is?

    Cireson, do you have any documentation on the queries that create these graphs?
  • Jason_MeyerJason_Meyer Customer Adept IT Monkey ✭✭
    Just touching base on this one.   We do not create many work items over the weekends, so for "Top Affected Users" I looked at what YESTERDAY showed and the Analytics displays one 'affected user' as being the top 'affected user' from yesterday.  I don't find any work items CREATED, RESOLVED, or CLOSED for that user.

    What am I missing?   As is, I think this is a bug, is it?
  • Tom_HendricksTom_Hendricks Customer Super IT Monkey ✭✭✭✭✭
    As someone who has been largely ignoring this DB for a while, I'm going to defer to Cireson on both points, not just the docs.
  • Justin_WorkmanJustin_Workman Cireson Support Ninja IT Monkey ✭✭✭✭
    The data in the Analytics DB is populated from jobs that run once per day.  The schedule at which they run can vary pretty wildly and is dependent on what you set in the installer(or based on the install time if you left it default).  If you look in SSMS/SQL Server Agent/Jobs you can see the queries the jobs are running to populate the Analytics DB by scripting a 'DROP and CREATE'. (Note that you can view the queries without executing them if you click 'DROP and CREATE'.)

    To Tom's point, if you're wanting up-to-the-minute data, queries against ServiceManagement or ServiceManager tend to be better.

    The Analytics DB is to keep data long-term.  The WorkItem data will be groomed out of ServiceManager at some point as determined by your settings in the SCSM console.  At some point the work item data in the ServiceManagement will also likely be flushed out(though there isn't an automatic process for this).  The Analytics DB is to keep that WorkItem data preserved.  Of course this is also what the SCSM DW is for.  However, as many of us know, the DW frequently has issues and can be difficult to troubleshoot.  Analytics is meant to be a simple supplement to the available data moving around in SCSM.
  • Jason_MeyerJason_Meyer Customer Adept IT Monkey ✭✭

    Found this document on the out of box 'Dashboard': https://support.cireson.com/KnowledgeBase/View/1150#/

    Does anything like it exist for 'Analytics'?

  • Jason_MeyerJason_Meyer Customer Adept IT Monkey ✭✭
    @Justin_Workman is there any further documentation on the Analytics DB?  Name of the database, location of the SQL queries?  I have a SQL admin that can look at this but they don't know Cireson.

  • Justin_WorkmanJustin_Workman Cireson Support Ninja IT Monkey ✭✭✭✭
Sign In or Register to comment.