Release Notes 2.8 (June 2nd, 2016)

Viakoo Release Notes 2.8

(June 2nd, 2016)

Viakoo Release 2.8 is an update and an incremental step forward for the Viakoo Service. The most significant improvements are associated with giving users control over the time delays used to open tickets on normal devices. Additionally, there are some performance enhancements to some specific reports and administrative views.

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

Time-Delay Parameter for Tickets

Back in Release 2.6, we introduced a time-delay in opening tickets for NORMAL priority devices. This was because some of our customers were experiencing a significant number of tickets which open and then resolve themselves before responsible individuals could even respond. To mitigate a significant amount of these kinds of tickets, the system now waits for the specified Time Delay (default of 40 minutes) before opening a ticket on the troubled device. In this way, the tickets open after this delay more reliably represent devices that are not going to recover.

Note: The Time Delay does not affect devices set to CRITICAL priority. Devices and video streams set to CRITICAL priority will open tickets immediately when a problem is detected.

Additionally, Uptime (VPU) and Quality (VSDI) trending measures will be affected immediately, regardless of the Time Delay. This can give visibility to the situation where cameras might have periods of being knocked offline, even if a ticket wasn’t opened.

New in Release 2.8, site administrators now have the option of to modify this Time Delay value. The default is still 40 minutes, but administrators can now select any value between 0 (i.e., no time delay) and 1440 minutes (i.e., 24-hours). In this way, users can adjust the opening of tickets at their site to fit the needs of their infrastructure, as well as how urgently they need to be notified about problems.

Setting the Time Delay Parameter

To set the Time Delay parameter for a site, navigate to a site’s Admin tab. You must have “Site Administration” privileges to see this tab (I.e., you have the role of “ADMIN” or “STAFF”).

 

Choose the “TICKET SETTINGS” subtab.

From here, you should see a “Ticket Throttling” section which gives you a field for changing the “Time Delay” value. Enter in your desired value and click “Save” to have your changes take affect.

If you enter an illegal value, the perimeter of the box will turn red and you won’t be allowed to save your entered value. If you aren’t sure why the box has turned red, hover your mouse over the box and, after a moment, a text message will display telling you why. The value must be in whole number of minutes and must be greater than or equal to 0 (zero) minutes (i.e., no delay at all) and  less than or equal to 1440 minutes (24-hours).

Support for SNMP Cameras

With Release 2.8, in addition to information we are already collecting, we now can collect and display SNMP data from properly enabled cameras. This most prominently shows up in some additional performance types for those cameras as well as some additional fields. If you have cameras which support the MIB II  standard, then we can automatically capture and render this information.

To get the MIB II data from your camera, contact Viakoo Support to make sure you are running the proper version of Viakoo Agents. Next, enable SNMP for each device you would like us to collect SNMP data (see your camera’s owner manual for details). Also, you need to give the agent the public (read) community strings if you are changing them from the default.

The agent can then automatically detect that the camera device is enabled for SNMP and will start collecting the camera’s SNMP data.

Specific measures:

    • CAMERA: Sampled bitrate” - This performance type is the bitrate the camera itself believes it is transmitting which distinquishes it from the “CAMERA: 10 second avg bitrate” which is the bitrate received by the server from the selected camera(s).

 

  • “CAMERA: Uptime” - This performance type is the measured time since the camera last booted (or rebooted). This is a useful measure to determine whether a time of service interruption was associated with the camera restarting or some other reason such as network disruption, et cetera.

 

  • Camera Description - This is a string of up to 255 characters which contains useful information such as model and firmware information. It is not being displayed in the camera table as the column can be extremely wide. However, it is included when you “Export CSV” the camera table or in the camera “Overview” display. To get to the camera’s “Overview” display, merely click on the camera’s name field in the camera table.  

Miscellaneous Fixes

  • User Administration pane off the main menu now renders significantly faster.  
  • Additionally, User Administration table now only specifies the single “Location” Site, Region, Company or Realm associated with the user’s permission invitation.
  • Sometimes, when displaying server performance values from the context of a server (i.e., a server was selected in the navigation pane versus the context being at a site level), the performance values being charted could incorrectly display values for the wrong server if you navigated between different servers at the same site.  This problem has been corrected.
  • When restoring performance graphs from a URL or “Back” operation on the browser, though the correct performance type was plotted, the first performance type was being displayed in the selector. This is now fixed.
  • Modifying a site, either to change its name, change its primary contact, or change its site address, is now done in the “Edit Site” subtab of the Admin Tab. With proper permissions, you can also remove an unwanted site or enter/exit “Maintenance Mode” for the site.
  • Ticket time references are now specific times in most cases as opposed to relative times from now. Specifically, if a ticket was open at 11:52am PDT on May 30th, 2016 and you were displaying it at 12:00noon on June 2nd, Release 2.8 will now say “Date Opened: 05/30/2016 at 11:52 AM” whereas in Release 2.7 it would have said  “Date Opened: Last Monday at 11:52am” in the ticket table and “Created 4 days ago” in the ticket overview display.
  • Operations Reports now only have a single label for the KPI graphs.
  • In the Performance Tab, when you add or remove devices from the selection without changing the type of device, the selected Performance Type remembers and displays the new selection with the already selected Performance Type.
  • In device tables, the hotlink to bring up a device’s console in a new browser tab is now a glyph to the right or below the IP address of the associated device instead of being a hotlink on the IP address itself.
  • For certain Level-1 supported VMS’s, the system use to erroneously detected cameras that were within the network but not recording to the current server as having failed streams. This no longer occurs.
  • Sites that only consist of Viewing Stations no longer display erroneous cameras that are not recording.
  • 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