Datacenter border-issued analytics for monitoring federated services

• US 9,515,902 B2
• Filed: 04/17/2013
• Issued: 12/06/2016
• Est. Priority Date: 04/17/2013
• Status: Expired due to Fees

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: Kruglick, Ezekiel
• Primary Examiner(s): Hussain, Tauqir
• Assistant Examiner(s): Guzman, Javier O
• Application Number:
  US14/114,732
• Publication Number:
  US 20140317273A1
• Time in Patent Office: 1,329 Days
• Field of Search: 709/224
• US Class Current: 1/1
• 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 from a deployment manager, wherein the instructions include properties of package indicia registered by the deployment manager through an addition of a string that includes a datacenter identifier and a network location identifier field at a predetermined location of monitoring data packets comprising the monitoring data;

analyzing data packets received from the deployment for the properties of the package indicia to identify the monitoring data packets that comprise the monitoring data;

embedding modification data into the monitoring data by injecting the modification data into the 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 deployment;

mapping datacenter hardware to contents of the packet headers of the monitoring data packets into which the one or more additional data fields were injected such that a location and other data associated with the deployment are monitored spanning across a datacenter federation, wherein the datacenter hardware includes one of a network processor and a data loss prevention system; and

providing the modified monitoring data to a monitoring system.

2. The method of claim 1, further comprising:

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

3. 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.

4. The method of claim 1, further comprising:

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

5. 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.

6. The method of claim 5, 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.

7. 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.

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

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

one or more of network processors to;

receive instructions associated with modifying monitoring data from a deployment from a deployment manager, wherein the instructions include properties of package indicia registered by the deployment manager through an addition of a string that includes a datacenter identifier and a network location identifier field at a predetermined location of monitoring data packets comprising the monitoring data; and

analyze data packets received from an instance of a deployed application for the properties of the package indicia to identify the monitoring data packets that comprise the monitoring data; and

a general processor to;

embed modification data into the monitoring data by injecting one or more additional data fields to packet headers of the 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;

map datacenter hardware to contents of the packet headers of the monitoring data packets into which the one or more additional data fields were injected such that a location and other data associated with the instance of the deployed application are monitored spanning across a datacenter federation, wherein the datacenter hardware includes one of a network processor and a data loss prevention system; and

provide the modified monitoring data to a monitoring server.

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

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

12. The datacenter gateway of claim 9, 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.

13. The datacenter gateway of claim 9, wherein the gateway is implemented at a software defined network (SDN) level.

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

a deployment manager server 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 by registering packet indicia through an addition of a string that includes a datacenter identifier and a network location identifier field at a predetermined location of monitoring data packets comprising monitoring data; and

the gateway to;

receive instructions associated with modifying the monitoring data from the deployment, instances from the deployment manager server, wherein the instructions include properties of the package indicia registered by the deployment manager server;

analyze data packets received from the deployment instances for the properties of the package indicia to identify the monitoring data packets that comprise the monitoring data;

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; and

map datacenter hardware to contents of the packet header of each monitoring data packet into which the one or more additional data fields were injected such that a location and other data associated with the deployment instances are monitored spanning across a datacenter federation, wherein the datacenter hardware includes one of a network processor and a data loss prevention system.

15. The cloud-based datacenter of claim 14, wherein the gateway further forwards the modified monitoring data to a monitoring server 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.

16. The cloud-based datacenter of claim 14, wherein the gateway

further ports 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 die received instructions.

17. The cloud-based datacenter of claim 14, wherein registering the package trigger with the gateway at each federated datacenter when the application instance is placed at each federated datacenter by registering packet indicia comprises:

registering a packet header that indicates monitoring data based on a destination of a monitoring server and format indicators.

18. The cloud-based datacenter of claim 14, wherein the predetermined location includes one of a data packet header and an end of a data packet.