Stingray: Control and Flexibility with Stingray Traffic Manager

March 10, 2014 - by Paul Wallace, Riverbed

Guest Post by Paul Wallace from Riverbed

If you have missed the other posts in this series you can click here to review prior to diving into this one.

We have covered load balancing, health monitoring and some caching in my last blog, and now it’s time to look at why Stingray Traffic Manager really shines when you need to add more control your applications.

First, Stingray gives you closer control over services and users and transactions, and lets you decide how your applications are delivered. And second, is the range of flexibility that you have with a software-defined approach to configuration and deployment.

Control and Flexibility

Stingray Traffic Manager lets you define rules and policies to control application, and you can do this in THREE ways:

1) Our Rule Builder gives you a very simple graphical user interface to create simple rules and policies. Click and choose from drop-down menus to create simple conditions and actions.

   HTTP Response Header: "Content-Type" starts with "text/html"
   Set Response cache time: "1"

2) Stingray TrafficScript is a simple, yet powerful programming language which gives you full control over applications, and is embedded right within the kernel of Stingray Traffic Manager to run with the highest possible performance.

$path = http.getpath();
if ( string.startswith ( $path, "/products" ) ){
    http.redirect( "/services.html" );

3) And where you need something that goes a little bit further, you can use our Java extensions capability. You can write rules in any language that can target the JV app. Java, Python, Ruby, and many others. You can use third party libraries, and those rules can be invoked by a traffic manager against specific transactions.


You can use these rules to inspect and then conditionally route traffic to the most appropriate servers, to apply simple security policies, block or permit particular types of transactions, or mask sensitive data in web responses. Rules can control which features of Traffic Manager are used - compression, bandwidth, rate shaping or caching – but they can also control at a much closer level, right down to individual transactions. It's very easy to inspect and modify both requests and responses, to ensure that the right content is delivered to your end users at the best possible level of service.

Event Handling

You can have even more control with Stingray’s Event Handling mechanism. You can hook custom actions, whether they're SNMP traps or email alerts, or even custom scripts. You can watch for internal events, such as a bandwidth class or a service level class going outside its desired parameters, or it could be an external event. For example, if Stingray Traffic Manager notices that a server has failed and then it can invoke a custom event to either raise an alert to a monitoring system, or perhaps even to attempt to execute a shell on the server and restart the service.

Stingray can monitor a range of performance and activities, all of which can be accessed through the user interface, and through our various APIs such as REST, SOAP, SNMP or command line, so that you can interface your existing systems to Traffic Manager, and you can create closed-loop solutions that program how your infrastructure responds in the event of certain events happening or traffic levels meeting certain levels.

For more information on Riverbed Stingray – Click Here

For more information on using Stingray as a Content Delivery Cloud (alternative to CDN) – Click Here