Session Layer For Monitoring Utility Application Traffic

1. A method comprising: at a network device of a plurality of network devices which routes utility application traffic, receiving control information indicating one or more thresholds for application specific flow metrics associated with utility application traffic streams, the control information configured to cause the network device to monitor utility application traffic messages that pass through the network device from a specific first utility device to a specific second utility device via a particular utility application traffic stream; monitoring the utility application traffic with respect to the one or more thresholds, by monitoring a header inserted into the utility application traffic messages, based on the received control information; and identifying the utility application traffic from the specific first utility device to the specific second utility device based on the header.

2. The method of claim 1 , wherein monitoring comprises monitoring metadata associated with the particular utility application traffic stream.

3. The method of claim 1 , wherein monitoring comprises evaluating a sequence number and a timestamp contained in the header of the utility application traffic messages.

4. The method of claim 1 , wherein monitoring comprises: collecting performance metrics for the particular utility application traffic stream specified by the control information; detecting a route change at the network device that affects an output interface at the network device through which the particular utility application traffic stream is routed; and associating the performance metrics collected for the particular utility application traffic stream after the route change.

5. The method of claim 1 , wherein monitoring comprises: collecting performance metrics for the particular utility application traffic stream; detecting at least one packet drop for the particular utility application traffic stream and a cause of the packet drop; and further comprising sending to a network management device a message containing information indicating the cause of the packet drop.

6. The method of claim 1 , wherein the control information is configured to cause the network device to automatically adjust monitoring parameters based on utility application traffic type, and further comprising automatically configuring one or more monitoring parameters for the utility application traffic based on the control information and the utility application traffic type.

7. The method of claim 1 , and further comprising generating an alert when the utility application traffic crosses loss, delay and/or jitter thresholds, and sending the alert from the network device to a network management device.

8. The method of claim 1 , wherein receiving comprises: receiving the control information to monitor utilization of processing and memory resources used for monitoring the utility application traffic; monitoring comprises monitoring processing and memory resource utilization with respect to a threshold; and denying a new request to monitor the utility application traffic or terminating lower priority monitoring tasks to be performed to allow for higher priority monitoring tasks when the processing and memory resource utilization crosses the threshold.

9. The method of claim 1 , wherein receiving comprises receiving the control information from a network management station.

10. An apparatus comprising: a network interface unit configured to enable communications over a network and to receive control information indicating one or more thresholds for application specific flow metrics associated with utility application traffic streams; switch hardware configured to route packets in the network; a processor coupled to the network interface unit and switch hardware, the processor configured to: monitor utility application traffic messages in the network from a specific first utility device to a specific second utility device via a particular utility application traffic stream in order to monitor utility application traffic with respect to the one or more thresholds contained in the control information, by monitoring a header inserted into the utility application traffic messages, based on the received control information; and identify the utility application traffic from the specific first utility device to the specific second utility device based on the header.

11. The apparatus of claim 10 , wherein the processor is configured to monitor metadata associated with the particular utility application traffic stream.

12. The apparatus of claim 10 , wherein the processor is configured to monitor the utility application traffic messages by evaluating a sequence number and a timestamp contained in the header of the utility application traffic messages.

13. The apparatus of claim 10 , wherein the processor is configured to cause the network device to automatically adjust monitoring parameters based on utility application traffic type, and to automatically configure one or more monitoring parameters for the utility application traffic based on the control information and the utility application traffic type.

14. The apparatus of claim 10 , wherein the processor is configured to generate an alert when the utility application traffic crosses loss, delay and/or jitter thresholds, and to send the alert to a network management device.

15. The apparatus of claim 10 , wherein the processor is configured to: obtain control information configured to monitor utilization of processing and memory resources used for monitoring the utility application traffic; monitor processing and memory resource utilization with respect to a threshold; and deny a new request to monitor the utility application traffic or terminate lower priority monitoring tasks to be performed to allow for higher priority monitoring tasks when the processing and memory resource utilization crosses the threshold.

16. One or more non-transitory computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to: obtain control information indicating one or more thresholds for application specific flow metrics associated with utility application traffic streams, the control information configured to cause a processor in a network device to monitor utility application traffic messages in a network from a specific first utility device to a specific second utility device via a particular utility application traffic stream; monitor utility application traffic with respect to the one or more thresholds contained in the control information, by monitoring a header inserted into the utility application traffic messages, based on the control information; and identify the utility application traffic from the specific first utility device to the specific second utility device based on the header.

17. The computer readable storage media of claim 16 , wherein the instructions that are operable to monitor comprise instructions that are operable to monitor the utility application traffic messages by evaluating a sequence number and a timestamp contained in the header of the utility application traffic messages.

18. The computer readable storage media of claim 16 , and further comprising instructions that are operable to cause the processor to automatically adjust monitoring parameters based on utility application traffic type, and to automatically configure one or more monitoring parameters for the utility application traffic based on the control information and the utility application traffic type.

19. The computer readable storage media of claim 16 , and further comprising instructions that are operable to generate an alert when the utility application traffic crosses loss, delay and/or jitter thresholds, and to send the alert from the network device to a network management device.

20. The computer readable storage media of claim 16 , and further comprising instructions that are operable to: obtain control information to monitor utilization of processing and memory resources used for monitoring the utility application traffic; monitor processing and memory resource utilization with respect to a threshold; and deny a new request to monitor the utility application traffic or terminate lower priority monitoring tasks to be performed to allow for higher priority monitoring tasks when the processing and memory resource utilization crosses the threshold.