by Russ
In my previous post, I promised that I would get into some more details about how different APM instrumentation techniques work in an OpenFlow environment. Today I will discuss network appliances.
OpenFlow is a protocol for communicating forwarding policies to switches and routers. In most cases, OpenFlow does not
change the form of the application packets on the network at all. Each application packet is still the normal Ethernet/IP/TCP packet that we know and love. The fields are the same and the decodes are the same. For passive appliances, like AppResponse Xpert, the change to OpenFlow is completely transparent. Existing OPNET appliances will provide the same monitoring and analysis capability that they do today. In fact, OpenFlow may make it easier to direct application traffic to an appliance. More on this in a future post…..
Also - In my next post, I will cover other APM instrumentation techniques like agents, polling, and browser instrumentation.
Subscribe to:
Post Comments (Atom)
Posts
2 comments:
Regarding AppResponse Xpert, how Openflow is completely transparent? can you elaborate more or give me some sample example?
@Jack: The Openflow protocol itself can be seen as an alternative way to configure network devices, but from the outside, the network devices still perform the same functions as before, so monitoring network traffic from/to those devices can be done in the same way as in a traditional network.
Post a Comment