# US 2019/0379576 A1 · Providing dynamic serviceability for software-defined data centers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0379576 A1
- Document ID: US20190379576A1
- Status: Published application
- Kind: A1
- Application number: 16/102,772
- Filed: 2018-08-14
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: VMware, Inc.
- Applicants: Vmware, Inc.
- Inventors: PRABHAKARA RAO NARNAKAJE VENUGOPALA; Shubham Verma; Sindhu Hanji Basavaraju
- Web page: https://patentgrep.com/patent/US20190379576A1

## CPC

- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/0266: using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
- H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L 41/0654: using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437)
- H04L 41/142: using statistical or mathematical methods
- H04L 41/16: using machine learning or artificial intelligence
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 43/028: by filtering
- H04L 43/103: with adaptive polling, i.e. dynamically adapting the polling rate
- H04L 43/06: Generation of reports
- H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Examples described herein include systems and methods for providing dynamic serviceability for a software-defined data center (“SDDC”). An example method can include collecting data-center metrics from a management service that monitors the SDDC, filtering the data-center information based on a predetermined list of metrics provided by a partner entity, and translating the filtered data-center information into a partner-specific format requested by the partner entity. The example method can also include generating metadata associated with the translated data-center information and transmitting the metadata and translated data-center information to a partner site associated with the partner entity. If the partner site is not available, the method can include transmitting the information to a partner-accessible storage location and, when the partner site becomes available, identifying the storage location and failed attempt to deliver the information.

## Claims

### Claim 1

A method for providing dynamic serviceability for a software-defined data center (SDDC) to a partner entity, comprising:
collecting data-center information from a management service that monitors at least a portion of the SDDC;
filtering the data-center information based on a stored list of metrics;
translating the filtered data-center information into a partner-specific format requested by the partner entity;
generating metadata associated with the translated data-center information; and
transmitting the metadata and translated data-center information to a partner site associated with the partner entity.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
in response to determining that the partner site is not available, forwarding the metadata and translated data-center information to a partner-accessible storage location; and
in response to determining that the partner site has recovered, generating an alert regarding downtime of the partner site and identifying the destination of the metadata and translated data-center information.

### Claim 3 (depends on 1)

The method of claim 1, wherein the stored list of metrics is provided by the partner entity through a configuration interface and stored in a configuration database.

### Claim 4 (depends on 1)

The method of claim 1, wherein the stages are performed based on at least one rule supplied by the partner entity through a configuration interface and enforced by an inference engine.

### Claim 5 (depends on 1)

The method of claim 1, wherein collecting data-center metrics is performed according to a poll time, and wherein the poll time is dynamically set by an inference engine based on settings provided by the partner entity.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving a response from the partner entity through a serviceability operations interface; and
implementing a solution at the SDDC, based on the received response, without manual intervention,
wherein the solution is implemented automatically based on the inference engine detecting the problem at the SDDC and executing one or more rules provided by the partner entity through the serviceability operations interface.

### Claim 7 (depends on 6)

The method of claim 6, wherein implementing the solution further comprises:
identifying a component that requires the solution; and
disabling the collecting of metrics from the component until the solution is implemented.

### Claim 8

A non-transitory, computer-readable medium comprising instructions that, when executed by a processor of a computing device, cause the processor to perform stages for providing dynamic serviceability for a software-defined data center (SDDC) to a partner entity, the stages comprising:
collecting data-center information from a management service that monitors at least a portion of the SDDC;
filtering the data-center information based on a stored list of metrics;
translating the filtered data-center information into a partner-specific format requested by the partner entity;
generating metadata associated with the translated data-center information; and
transmitting the metadata and translated data-center information to a partner site associated with the partner entity.

### Claim 9 (depends on 8)

The non-transitory, computer-readable medium of claim 8, the stages further comprising:
in response to determining that the partner site is not available, forwarding the metadata and translated data-center information to a partner-accessible storage location; and
in response to determining that the partner site has recovered, generating an alert regarding downtime of the partner site and identifying the destination of the metadata and translated data-center information.

### Claim 10 (depends on 8)

The non-transitory, computer-readable medium of claim 8, wherein the stored list of metrics is provided by the partner entity through a configuration interface and stored in a configuration database.

### Claim 11 (depends on 8)

The non-transitory, computer-readable medium of claim 8, wherein the stages are performed based on at least one rule supplied by the partner entity through a configuration interface and enforced by an inference engine.

### Claim 12 (depends on 8)

The non-transitory, computer-readable medium of claim 8, wherein collecting data-center metrics is performed according to a poll time, and wherein the poll time is dynamically set by an inference engine based on settings provided by the partner entity.

### Claim 13 (depends on 8)

The non-transitory, computer-readable medium of claim 8, the stages further comprising:
receiving a response from the partner entity through a serviceability operations interface; and
implementing a solution at the SDDC, based on the received response, without manual intervention,
wherein the solution is implemented automatically based on the inference engine detecting the problem at the SDDC and executing one or more rules provided by the partner entity through the serviceability operations interface.

### Claim 14 (depends on 13)

The non-transitory, computer-readable medium of claim 13, wherein implementing the solution further comprises:
identifying a component that requires the solution; and
disabling the collecting of metrics from the component while the solution is being implemented.

### Claim 15

A system for providing dynamic serviceability for a software-defined data center (SDDC) to a partner entity, comprising:
a memory storage including a non-transitory, computer-readable medium comprising instructions; and
a computing device including a processor that executes the instructions to carry out stages comprising:
collecting data-center information from a management service that monitors at least a portion of the SDDC;
filtering the data-center information based on a stored list of metrics;
translating the filtered data-center information into a partner-specific format requested by the partner entity;
generating metadata associated with the translated data-center information; and
transmitting the metadata and translated data-center information to a partner site associated with the partner entity.

### Claim 16 (depends on 15)

The system of claim 15, the stages further comprising:
in response to determining that the partner site is not available, forwarding the metadata and translated data-center information to a partner-accessible storage location; and
in response to determining that the partner site has recovered, generating an alert regarding downtime of the partner site and identifying the destination of the metadata and translated data-center information.

### Claim 17 (depends on 15)

The system of claim 15, wherein the stored list of metrics is provided by the partner entity through a configuration interface and stored in a configuration database.

### Claim 18 (depends on 15)

The system of claim 15, wherein the stages are performed based on at least one rule supplied by the partner entity through a configuration interface and enforced by an inference engine.

### Claim 19 (depends on 15)

The system of claim 15, wherein collecting data-center metrics is performed according to a poll time, and wherein the poll time is dynamically set by an inference engine based on settings provided by the partner entity.

### Claim 20 (depends on 15)

The system of claim 15, the stages further comprising:
receiving a response from the partner entity through a serviceability operations interface; and
implementing a solution at the SDDC, based on the received response, without manual intervention,
wherein the solution is implemented automatically based on the inference engine detecting the problem at the SDDC and executing one or more rules provided by the partner entity through the serviceability operations interface.
