Release Notes 2.11 (October 13th, 2016)

Viakoo Release Notes 2.11

(October 13th, 2016)

Viakoo Release 2.11 is an incremental step forward for the Viakoo Service. Improvements are made to Custom Performance Thresholds, we’ve created a new Retention Report, and we give users a mechanism for overriding the Retention Goals from their recorders to give them controls in Retention Compliance calculations.

Additionally, Release 2.11 includes more bug fixes and performance enhancements. For more information, please read below for details.

Improvements to Custom Performance Threshold Tickets

Release 2.11 improves the Custom Performance Threshold Tickets to improve usability by including relevant information from the threshold in the ticket itself in two ways:

  1. The Problem text in the tickets now include the measure, performance threshold and condition that was exceeded to cause the ticket to open.
  2. In the associated ticket overview of ticket, you can get back to the specific threshold that caused the ticket.

Threshold Problem Text Improvement

As of Release 2.11, the measure and the condition are explained in the problem (cause) string in the associated threshold ticket.

Ticket Overview Improvement

As of Release 2.11, threshold tickets will not only have the improvement to the ticket language, but also include a link to the specific threshold that precipitated the ticket.

Clicking on the threshold associated with the ticket, will take you to the Threshold Admin pane where you can find the associated threshold which caused the ticket.

Retention Report

New in Release 2.11 is the Retention Report. Use the Retention Report to get a summary of the Recorders across your infrastructure to answer some key questions:

  1. Are there any Recorders that are having trouble reaching their retention goals?
  2. How bad is it? For example, how many streams are under- or over-achieving their retention goals? How much storage is still available?
  3. Are there any Recorders that have capacity to accommodate some of the streams from overloaded Recorders? Specifically, of the Recorders achieving their goals at the same site, which have the most available storage capacity?

For Viakoo users who have “Reports” as part of their subscription, navigate to the Reports tab and click the radio button next to the “Retention Report” and click button.

A Retention Report has two sections:

  1. A Retention Graph 
  2. And a Retention Table

Retention Graph

The graph shows two bars per Recording Server, Video Retention Compliance (VRC%) and FreeSpace %. The dark blue bar is the Video Retention Compliance (VRC %) to see which servers are having trouble meeting their retention goals. The companion, light-blue bar is FreeSpace% and helps you see which servers have space available.

A server with a VRC% less than 100% and low free space is a server that needs some reconfiguration. A server with low VRC% and relatively high free space % probably has some new cameras that haven’t had the time to accumulate enough video data to be at their goals. Recorders with VRC at 100% and lots of free space are candidates to receive some video streams from recorders that might be saturated.

The Retention Graph shows you the top 10 items in the Retention Table. The Retention Table is sorted by the Video Retention Compliance (VRC) in ascending order by default. This has the effect of having the 10-worst servers in terms of Retention Compliance. Retention Table. By clicking on any of the column headers in the Retention Table, you can resort the table. The Retention Graph will change to reflect the top-10 items of the resorted table.

Retention Table

The lower part of the Retention Report is the Retention Table. Each Recording server (i.e, a server recording video camera streams) will be given a row in the Retention Table, providing useful data associated with recording your video streams on that server. StorStac and servers marked as “Viewing Stations” will not be included in a Retention Report.

Retention Table Columns

  • Status - Latest Status of the Server
  • Name - Name of Server
  • Priority - NORMAL or CRITICAL
  • VRC - Current Video Retention Compliance %
  • Free Space -Available Free Space as a % of available storage
  • Host Name - Host Name as defined within the server.
  • IP Address - IP Address(es) associated with the server
  • Serial Number - Server Serial Number
  • Streams - Total Number of Enabled Streams that are NORMAL or CRITICAL
  • Video Drives - Storage drives (drive letters) available for video storage
  • Used Video Capacity - Space consumed with data files
  • Total Video Capacity - Total available space
  • Average Retention - Average number of days of retained data for all the streams recording to this server
  • Max Retention - Number of days for video stream with the longest retained days of  data
  • Min Retention - Number of days for video stream  with the fewest retained days of data
  • Average Retention Goal - Average retention goal for all the streams associated with the server
  • Streams Above Goal - Total number of streams exceeding their retention goals
  • Streams At Goal - Total number of streams at their retention goal
  • Stream Below Goal - Total number of streams below their retention goal
  • Last Updated - Time of last update from the associated server
  • Site - Site associated with the recording server

Clicking on thebutton allows you to download a comma-separated values (CSV) file of the table so you can use the data in your favorite spreadsheet software.

Manually Changing the Retention Goal in the Cloud

Users have had the ability to set a Retention Day Goal for a video camera stream from the Viakoo Stream-Table interface. However, this feature was only useful when dealing with a VMS that didn’t have a way to set a retention goal explicitly.

Starting in Release 2.11, this manual setting of the retention goal will be used in the VRC calculation instead of the goal pulled from the VMS. This gives users a way of configuring their system to over-achieve the retention requirements of the user, to get to a desired level of retained data if possible. This is particularly useful for VMS’s that explicitly delete data that is beyond the retention goal, even if there is more space. Setting a higher goal than is needed in these VMSes or an ‘∞’ (infinity) setting, implying the system should save video data until all archive space is exhausted. Then users can get more video data than is required and have the compliance calculation demonstrate they are achieving or exceeding those requirements.

This information now appears in the stream table as both a “Retention Goal” (i.e., the goal used in the VRC calculation) and a “VMS Goal” (i.e., the goal setting in the VMS). For example,

By default, the Retention Goal equals the VMS Goal. To change the value used in the VRC calculation, click button in the upper right of the stream table. Among other things, this makes the Retention Goal field editable. Given that there was no manually set goal, the field will start off as blank.

Click in the Retention goal field and enter a value for the desired Retention Goal (e.g., “5”).

and then click in the upper right corner when you are done editing. The table will now reflect the new, manual set goal for Retention that is different than the VMS Goal. The manually set goal not only is a different value, the number is displayed in regular instead of italic font.

In this example, before the change, the first stream would have been getting a VRC score of 100%. After the change in setting, the same stream would get a VRC score of 7-days/5-days=140% of Retention Goal.

Reverting a Manually Set Retention Goal

To go back to the VMS Goal, which is the default setting, enter a “blank” or ‘0’ (zero) for the Retention Day goal. This will cause the system to remove the manually entered value and go back to the VMS setting as the goal to use in the Retention Compliance calculation for the associated string.

Color Improvement

Historically, Gray was used to indicate OKAY. This was done to help problems be the only thing that would have color, which would better draw your attention. However, this was something that hasn’t been intuitive to many users. Moreover, people like to see Green as well when things are okay.

Starting in Release 2.11, Green will now be used for the “OKAY” color. Though some of our users grew to like the original color scheme, we hope that this change makes the interface more naturally intuitive for all users. If you like or don't like the changes, please let us know at feedback@viakoo.com, through our "Talk to Experts" box on the user interface, or through our community board.

Miscellaneous Fixes and Improvements

  • When you click on a ticket in a ticket list, the navigation context implicitly goes to the site or system that is associated with the ticket. This means that clicking on another tab, such as Reports, Details or Performance, puts you are in the context of the ticket location. Using the “Back” button on the browser will get you back to the original context of the Ticket List before you clicked on to get to the Ticket Overview.

More information

If you have any questions, comments, bug reports, or suggestions, please reach out to us through the live-chat feature or contact us at feedback@viakoo.com.

We love hearing from you!

-Team Viakoo

1 (855) 585-3400

Have more questions? Submit a request

Comments

Powered by Zendesk