DATACENTER BORDER-ISSUED ANALYTICS FOR MONITORING FEDERATED SERVICES

• US 20140317273A1
• Filed: 04/17/2013
• Published: 10/23/2014
• Est. Priority Date: 04/17/2013
• Status: Active Grant

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: Kruglick, Ezekiel
• Granted Patent: US 9,515,902 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

Abstract

Technologies are generally described for providing datacenter border-issued analytics for monitoring federated services. In some examples, a deployment manager, which manages placement of application deployment instances across a federation and thus already knows which datacenter each instance is in, may register a package trigger with a gateway at each datacenter when an application is placed in each datacenter. The datacenter gateway(s) may then search through data packets for registered package properties such as content of a packet header that indicates it is a monitoring packet, and inject additional data according to instructions from the deployment manager. For example, the deployment manager may instruct the gateway(s) to inject a datacenter identifier or a network location identifier to each monitoring data packet. The additional data may be customer-defined and the modified monitoring data including the additional data may be sent to a monitoring system to be analyzed.

Claims

1. A method to provide datacenter border-issued analytics for monitoring federated services, the method comprising:

receiving instructions associated with modifying monitoring data from a deployment manager;

receiving monitoring data from a portion of a deployment;

embedding modification data into monitoring data by injecting the modification data into monitoring data packets as the packets pass through one or more datacenter borders or gateways, wherein the modification data indicates one or more of a processor, a server, and a datacenter associated with the portion of the deployment; and

providing the modified monitoring data to a monitoring system.

3. The method of claim 1, further comprising:

enabling definition of the modification data embedding based on a user preference through the instructions.

6. The method of claim 1, further comprising:

enabling a security level design via definition of one or more of a type and an amount of deployment location data to be collected in the modified monitoring data.

7. The method of claim 1, further comprising:

implementing embedding of the modification data into the monitoring data at a single datacenter.

8. The method of claim 1, further comprising:

implementing embedding of the modification data into the monitoring data at different datacenters with one or more variations in implementation.

9. The method of claim 8, wherein the variations include one or more of:

different available data for embedding and different points in a packet flow while embedding of the modification data into the monitoring data remains transparent to an executed application and the monitoring system.

10. The method of claim 1, further comprising:

implementing embedding of the modification data into the monitoring data across a private cloud and multiple public clouds.

11. The method of claim 1, wherein the portion of the deployment is an instance of an executed application.

2. (canceled)

4-5. -5. (canceled)

12. A datacenter gateway operable to provide datacenter border-issued analytics to monitor federated services, the gateway comprising:

one or more of network processors, configured to;

receive instructions associated with modifying monitoring data from a deployment manager; and

receive monitoring data from an instance of a deployed application; and

a general processor, configured to;

embed modification data into the monitoring data by injecting one or more additional data fields to packet headers of monitoring data packets as the packets pass through one or more datacenter borders or gateways according to the instructions of the deployment manager, wherein the modification data indicates one or more of a processor, a server, and a datacenter associated with an instance of the deployed application; and

provide the modified monitoring data to a monitoring server.

13. The gateway of claim 12, wherein the gateway is further configured to analyze received data packets for registered package properties and determine monitoring data packets.

15. The gateway of claim 12, wherein the additional injected data fields include one or more of a datacenter identifier and a network location identifier.

16. The gateway of claim 12, wherein the gateway is further configured to map datacenter hardware to contents of packet headers of the monitoring data packets.

17. The gateway of claim 16, wherein the hardware includes one of a network processor and a data loss prevention system.

18. The gateway of claim 12, wherein the network processors include matching engines for rapidly matching patterns in monitoring data packets and/or monitoring data packet headers.

19. The gateway of claim 12, wherein the gateway is one of a session border controller, a border gateway, a session aware load balancer, a data loss prevention gateway, and a multiservice security gateway.

20. The gateway of claim 12, wherein the gateway is implemented at a software defined network (SDN) level.

14. (canceled)

21. A cloud-based datacenter operable to provide datacenter border-issued analytics to monitor federated services, the datacenter comprising:

a deployment manager server configured to;

manage placement of deployment instances across a federation of datacenters; and

register a package trigger with a gateway at each federated datacenter when an application instance is placed at each federated datacenter; and

the gateway configured to;

receive instructions associated with modifying monitoring data from the deployment manager server;

receive the monitoring data from the deployment instances;

analyze data packets in the received monitoring data for registered package properties and determine monitoring data packets; and

inject one or more additional data fields to a packet header of each monitoring data packet according to the instructions of the deployment manager server.

22. The datacenter of claim 21, wherein the gateway is further configured to forward the modified monitoring data to a monitoring server configured to:

receive the modified monitoring data from the gateway; and

analyze the modified monitoring data for information associated with one or more of;

a current deployment location, a provisioning status, service level agreement (SLA) data, a type of underlying hardware, and a proximity to one or more data repositories.

23. The datacenter of claim 21, wherein the deployment manager server is further configured to:

employ an application wrapper to provide instructions to the gateway.

24. The datacenter of claim 23, wherein the gateway is further configured to:

port in one or more of accelerators, software patches to be applied to virtual machines executing the accelerators, and a hardware map that maps different types of processors to the accelerators based on the received instructions.

27. The datacenter of claim 21, wherein registering the package trigger with the gateway at each federated datacenter when the application instance is placed at each federated datacenter comprises:

registering packet indicia to trigger modification of data packets by registering a packet header that indicates monitoring data based on a destination of a monitoring server and format indicators.

28. The datacenter of claim 27, wherein the registered packet indicia includes an addition of a string at a predetermined location in each data packet.

29. The datacenter of claim 28, wherein the predetermined location includes one of a data packet header and an end of a data packet.

25-26. -26. (canceled)

30. (canceled)