DX Unified Infrastructure Management

 View Only
Expand all | Collapse all

Historical SLA reports in 20.3.3

  • 1.  Historical SLA reports in 20.3.3

    Posted Mar 25, 2021 12:20 PM
    Can anyone else open historical SLA reports after upgrading to 20.3.3?

    It's been an issue in all 20.x releases, I was hoping this would have been resolved in 20.3.3....

    All 2020 SLA reports are missing still, and if I recreate an SLA report (it runs successfully in the sla_engine log), but doesn't appear in the SLA history window..

    ------------------------------
    CA - UIM administrator
    ------------------------------


  • 2.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Mar 25, 2021 12:27 PM


    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 3.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Mar 25, 2021 12:31 PM
    Edited by Stephen Danseglio Mar 25, 2021 12:32 PM


    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 4.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Mar 25, 2021 12:34 PM
    Hi Sam,

    Are you referring to a different view?

    Steve

    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 5.  RE: Historical SLA reports in 20.3.3

    Posted Mar 25, 2021 12:38 PM
    Hi Steve,

    That's the right area yes, but I'm unable to load/view the full SLA reports.

    ------------------------------
    CA - UIM administrator
    ------------------------------



  • 6.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Mar 25, 2021 01:17 PM
    Hi Sam,

    What do you get or see, no SLAs listed in the left side of the OC page, an empty page, or something else?

    Steve

    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 7.  RE: Historical SLA reports in 20.3.3

    Posted Mar 25, 2021 01:52 PM
    Hi Steve,

    I see this.  As you can see, the 2nd to latest SLA report is showing as Jan - Feb 2020.. the rest of 2020 is missing, and I'm unable to open/export to PDF to see the full report.



    ------------------------------
    CA - UIM administrator
    ------------------------------



  • 8.  RE: Historical SLA reports in 20.3.3

    Posted Mar 25, 2021 03:21 PM
    If my understanding is correct, the ability to generate historical reports did not make it into 20.3.3 and the expectation is a hotfix will be released to provide this functionality.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 9.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Mar 25, 2021 03:24 PM
    Either 20.3.4 patch release or the next major release will include this fix. We may go direct to a 21.x release, still TBD. ETA Q3 CY21.

    Steve

    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 10.  RE: Historical SLA reports in 20.3.3

    Posted Mar 26, 2021 05:54 AM
    Thanks Stephen

    ------------------------------
    CA - UIM administrator
    ------------------------------



  • 11.  RE: Historical SLA reports in 20.3.3

    Posted Jun 30, 2021 01:05 PM

    Greetings,

    I want to bring up this topic again as we have the following change in Operator Console 20.3.3 June 2021 Patch (https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU01588&os=MULTI-PLATFORM) :

    But I can only see the SLA Reports that were scheduled in the past:


    As far I can see, there is no possibility to really create historical SLA Reports cause you just gain access to SLA Reports that were already generated in the past.

    So far so bad.

    I have the following problem with this:
    Broadcom entirely left out the SLA Report Schedules function in 20.3.0.

    So aside from the fact that they brought the function in with a later patch, and the fact that you can now access the "historical SLA Reports" everything between is lost.
    I do not have the SLA Reports from January to sth. like April/March, when the function were brought in again.

    Does someone have the same issue?

    Our customers are still waiting for the SLA Reports for early 2021, when the function was not present at all.




  • 12.  RE: Historical SLA reports in 20.3.3

    Posted Jul 07, 2021 01:40 PM
    I will share what I did to get through this for now.  I schedule all of my SLA reports in the report scheduler to run between 11:30pm and 11:55pm on the last day of the month.  I then get a report that covers all but the last 30 minutes of the month.


  • 13.  RE: Historical SLA reports in 20.3.3

    Posted Jul 13, 2021 09:54 AM
    @KEVIN MARTIN- A word of warning that it looks like uim_reportscheduler 20.33hf3 (which might not be widely available yet) changes the behavior and would probably ​generate an SLA report for the previous month rather than the current month even when running on the last day of the month. We got that hotfix to address the issue of SLA reports that run on the 1st day of the month not showing the results for the previous month, even though that was the original behavior. I noticed that they also ended up changing the behavior on the last day of the month (and everything in between as well).

    If you install that hotfix, you shouldn't end up missing out on any SLA reports, but you'd get them a month later...


  • 14.  RE: Historical SLA reports in 20.3.3

    Posted Jul 14, 2021 03:50 AM
    Hi @ahd ahd

    I recognized this issue two days ago after upgrading a client system from 9.x to 20.3.3. But it was even more drastic. I were seeing periods from 2014 to 2016, then the big gap and then the current period. 

    After some investigation yesterday, I was able to isolate the problem as follows:
    The used REST service 'slahistory' returns only 30 historical and the current period. Unfortunately, it is the 30 oldest periods and not the 30 most recent. Probably there is a SQL query like this: 'SELECT TOP 30 sla_id, period_begin, period_end FROM H_SLA_COMPLIANCE WHERE sla_id=? ORDER BY period_begin'
    This will select and return the oldest 30 periods. Maybe it had to be limited to 30 periods due to GUI restrictions. But anyway -  development can easily fix it by querying the 30 most recent periods - for that they need only 'ORDER BY period_begin DESC'.

    Data-destructive workaround (at your own risk, DB backup required): In coordination with the customer, we deleted all 2019 and older periods from the H_SLA_COMPLIANCE, H_SLO_COMPLIANCE, H_QOS_COMPLIANCE tables to ensure that fewer than 30 historical periods remain. After that the periods are displayed correctly again and you can look at the values of the previous months.

    I'll open a support case for this later today.

    Hope this helps,


  • 15.  RE: Historical SLA reports in 20.3.3

    Posted Jul 15, 2021 07:35 AM
    The first SLAs I got in our database were from 2013 belonging to SLA IDs we currently not use anymore.
    But for the newer ones I can confirm that we have the same behaviour @Olaf Pape mentioned.
    Thanks for the great work.



  • 16.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Jul 15, 2021 07:35 AM
    Hi Olaf,

    This issue will be addressed in the July hotfix which is planned for release next week.

    Steve


    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 17.  RE: Historical SLA reports in 20.3.3

    Posted Jul 16, 2021 04:06 AM
    Hi Steve,

    thanks for this information. I am looking forward and will then import and test the Patch as soon as possible.



  • 18.  RE: Historical SLA reports in 20.3.3

    Posted Jul 20, 2021 03:23 PM
    Great to see this finally getting patched.

    PS, new profile as I've moved companies since reporting this issue.

    ------------------------------
    Monitoring & Event Management Team Lead
    Riverside
    ------------------------------



  • 19.  RE: Historical SLA reports in 20.3.3

    Posted Jul 20, 2021 03:23 PM
    Great news, thanks Stephen.  Good to know it'll finally be resolved!

    PS, new account as I've moved companies since reporting this issue.

    ------------------------------
    Monitoring & Event Management Team Lead
    Riverside
    ------------------------------



  • 20.  RE: Historical SLA reports in 20.3.3

    Posted Jul 26, 2021 08:19 AM
    Hi @Stephen Danseglio,

    are there any news about the update you mentioned to release last week?

    Best Regards
    ​​


  • 21.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Jul 26, 2021 08:43 AM
    QA is in progress... The release should become available for download by the end of this week, Friday, July 30th.

    Steve

    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 22.  RE: Historical SLA reports in 20.3.3

    Posted Jul 26, 2021 10:25 AM
    Looking forward to it....

    Well to be honest, I am fascinated what new bugs will in it, with fixing that problem
    But...*crossing fingers*

    cheers
    Matthias


  • 23.  RE: Historical SLA reports in 20.3.3

    Broadcom Employee
    Posted Aug 17, 2021 01:53 PM
    Edited by Stephen Danseglio Aug 17, 2021 01:57 PM

    Operator Console 20.3.3 July 2021 Patch resolves the issue.

    https://support.broadcom.com/download-center/solution-detail.html?aparNo=LU02219&os=MULTI-PLATFORM

    One caveat-> the current design only supports the last 30 periods. It was designed with consideration for the best performance.
    ------------------------------
    Support Engineer
    Broadcom
    US
    ------------------------------



  • 24.  RE: Historical SLA reports in 20.3.3

    Posted Aug 18, 2021 07:31 AM
    Hi Stephen,

    I've applied the patch but still unable to open historical SLA reports...

    They are showing in the history window, but do nothing when clicked on / selected.

    Thanks,
    Sam