Release Notes 2.5 (February 25th, 2016)


Viakoo Release Notes 2.5

(February 25th, 2016)

Viakoo Release 2.5 is an incremental step forward for the Viakoo Service. There are a few improvements to tickets, some bug fixes, and a few key features requested by customers. A couple of highlights worth reviewing are the new “Viewing Station” setting, the “Duplicate” option for performance graphs, and Status hover text improvements. Read further to understand these new capabilities.

New Ticket Categories

The following are new ticket categories in this release:

  • EXCESSIVE_FAILED_LOGINS* - "<server> has more than five failed logins in past hour."
  • PING_HANG - "Ping process on server <server> is hanging. Server needs to be rebooted."
  • VMS_PROCESS_RESTART - "<vms process> restarted."

Refer to full article on ticket categories for information on Ticket Categories and how to use them.

Viewing Station Setting

The Viakoo service automatically determines the configuration of servers that it is installed on and makes an assumption that every video stream it see’s should be considered “NORMAL” by default. This means when those streams stop sending data to the recorder, Viakoo will open a ticket. Raising a Stream’s priority to CRITICAL will cause failures on that stream to open CRITICAL priority tickets. You can also set a stream to “IGNORE,” in which case no tickets will be opened if that stream stops working.

This works well for normal operations on servers recording video, however, when a user wants to leverage Viakoo to manage other kinds of servers, Viewing Stations in particular, then this default behavior can cause streams viewed from that server to be mistaken for streams recording to that server. This means that viewing streams from these servers can open tickets when actually you want them to be IGNORED by default.

In Release 2.5, we’ve added a server “Type” field which can have two states:  Recorder(default) and Viewing Station which tells the service that all video streams that it detects coming into that server are configured at priority “IGNORE” by default. Administrators can use the “Edit” button in the “Details” tab on the server to change the value of this field.


After you select “Viewing Station” option, you then click “Save” to retain your changes.

“Duplicate” Graph Feature

In Release 2.5, we’ve added a “Duplicate” button to graphs in the Performance tab. This button allows you to create another copy of a graph with all the settings you’ve picked. This is useful in instances where you have selected a collection of devices, such as streams or switch ports, and would like to view multiple performance measures on the same set of selected devices.

Which then creates a new graph just below the current graph. Unlike the "Add Graph" button, this new graph has the identical selected devices or streams as well as performance types. 

Now you can select different performance measures to graph from the same collection.



Improvement to Hover Text on Status Icons

In prior releases, hovering your cursor over a status icon would display the name of the icon represented (i.e., FAILED, CRITICAL, DEGRADED and OKAY). New in Release 2.5, hovering your cursor over these icons will display a short description of the situation that caused the system to set change the status. This is particularly useful when looking through lists of Sites, Servers or Devices in the “Details” tab of the respective Company, Site or Server. Below are some examples:


Problems Corrected in Release 2.5

  • As an ongoing effort to improve the service, we’ve reduced the number of noisy server tickets that some of our customers have been experiencing. They come in two classes:
    1. Server not reachable: Some of these failures that are associated with latencies in routed networks and other issues have been reduced.
    2. Viakoo Agent not responding: Many of these scenarios are associated with problems with resources or software on customer servers. Though there is more work to be done, we’ve improved the service to more accurately identify the root cause.
  • In Release 2.4, some push notification end-points (handlers to talk to device Ids) were removed during the upgrade process. The implication is that some of our users stopped receiving push notifications to their phones. The bug has been fixed and users potentially affected by this problem have been notified. There is still a problem where users could choose push notifications from the cloud “My Profile” administration pane. Unfortunately, setting push-notifications this way may not work if there is no mobile device registered with the Viakoo service for that account.  Check the Viakoo KB article on troubleshooting push-notifications.

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

We love hearing from you!

-Team Viakoo

1 (855) 585-3400

Have more questions? Submit a request


Powered by Zendesk