nanoStream Analytics API 2.29

Posted on by

Release Notes

The latest nanoStream Analytics update comes with a lot of improvements regarding our stream health monitoring system. We enhanced the overall detection algorithms to ensure that any anomaly within your streaming landscape can be observed transparently.  

This also affects the way alerts are now presented in either the Analytics Dashboard [AD] or API. We added multiple insights to alerts, most importantly the connection details, which can be indicators of where and how frequent ingest connections took place. Therefore, we also partially improved how alert data is displayed within our graphs, while applying additional bug fixes to our UI. 

Providing additional possibilities to request SPRS (Successful Playback Start Ratio) information allows a more practical approach to identifying issues of stream playbacks faster and more reliable. 

Regarding user experience, we decided to make the authentication process less tedious and more secure at the same time. 

Changelog 

🚀 NEW 

Added API routes for successful playback start ratio (SPSR) to get TOP 100 for streams 

  • /api/v2/playback/start/success/ratio/streams/top100 (ascending order) 
  • /api/v2/playback/start/errors/streams/top100 (descending order) 

New field properties available at alerting API routes 

  • name – each single alert/advice now has a name like DUPLICATED_INGEST 
  • servers – all hosts found for alert detection 
  • highestStreamElapsedTime – highest elapsed time found for the stream in the detection time range – gives an indication of how long the stream has been running when the alert was detected 

New alert: CONTINUOUS_RESTARTS_POOR_PERFORMANCE

  • (code: 22001), this alert indicates continuous restarts where the stream time ratio reflects a poor performance 

✏️ IMPROVED 

Changed behavior of alerting API routes 

  • /api/v2/alerting/ingest & /api/v2/alerting/ingest/custom
  • Reduced detection time range from 15 to 5 minutes to make detection more responsive 
  • streamDetails has been replaced by connectionsDetails
    • streamDetails only contained a summary of the most frequent values for all ingest connections, whereas connectionsDetails lists each ingest connection that occurred in the alert detection time range 
  • CONTINUOUS_RESTARTS with code 22001 is now code 22000 

Documentation

To support the latest updates, we’ve added specific pages and sections to our official documentation:

General Documentation
https://docs.nanocosmos.de/docs/cloud/analytics

nanoStream Analytics API Documentation
https://metrics.nanocosmos.de/api/doc

nanoStream Anayltics Dashboard Login
https://metrics.nanocosmos.de

More about available metrics within the Cloud Dashboard 
Metrics within the Cloud Dashboard 

Free Trial