Abstract: A method including receiving events from different data sources for a service automatically executing in an enterprise system. A first event is enriched by providing the first event with first metadata that associates the first event with a first application used by the service. The first event is assigned to a time slice associated with the first application. A second event is enriched in a similar manner. A correlation graph of nodes and edges is built using the enriched events, with nodes representing the events and edges indicating relationships between the edges. A third event indicating a fault in the first application associated with the first node is received. The source of the error for the third event is identified using the second updated correlation graph and the time slice. The source of error is then mitigated.

Abstract: A method including receiving events from different data sources for a service automatically executing in an enterprise system. A first event is enriched by providing the first event with first metadata that associates the first event with a first application used by the service. The first event is assigned to a time slice associated with the first application. A second event is enriched in a similar manner. A correlation graph of nodes and edges is built using the enriched events, with nodes representing the events and edges indicating relationships between the edges. A third event indicating a fault in the first application associated with the first node is received. The source of the error for the third event is identified using the second updated correlation graph and the time slice. The source of error is then mitigated.

Abstract: A system including a data repository storing metrics describing operational behavior of software programs executing in an enterprise system. The system also includes an application programming interface (API) gateway configured to receive the metrics. The system also includes an ingestion layer configured to ingest the metrics to form the ingested metrics. The system also includes a tumbling window processor configured to process the ingested metrics and the events into heat maps, sort the heat maps into the time slices, and populate the time slices with the ingested metrics.

Abstract: A method includes receiving first metrics describing first behaviors of applications having a fault, and second metrics describing second behaviors of an enterprise system in which the applications are executing. The first and second metrics are ingested. Ingesting includes assigning a first cardinality score to first metrics related to the fault. Ingesting also includes assigning a second, lower cardinality score to second metrics that are unrelated to the fault. Tumbling window processing is performed on the ingested metrics by sorting the first metrics and the second metrics into time slices. Each of the time slices includes a corresponding data structure for storing the data in the different time periods. Tumbling window processing is also performed on the ingested metrics by storing more data in the time slices for the first metrics having the first cardinality score relative to the second metrics having the second cardinality score.

Abstract: Certain aspects of the present disclosure provide techniques for maintaining an application through an execution platform. An example method generally includes receiving a first workflow definition of a plurality of workflow definitions associated with an application. The first workflow definition may be a workflow defining a build operation for building the application. The first workflow definition is executed to build the application by retrieving an executable binary from a binary repository, retrieving source code for the application binary from an application source code repository, building the application binary by executing the executable binary on the retrieved source code, and storing the application binary in the binary repository. A second workflow definition is received to execute the application. The second workflow is executed to execute the application by retrieving the application binary from the binary repository, and executing the retrieved application binary to run the application.

Abstract: A method includes receiving first metrics describing first behaviors of applications having a fault, and second metrics describing second behaviors of an enterprise system in which the applications are executing. The first and second metrics are ingested. Ingesting includes assigning a first cardinality score to first metrics related to the fault. Ingesting also includes assigning a second, lower cardinality score to second metrics that are unrelated to the fault. Tumbling window processing is performed on the ingested metrics by sorting the first metrics and the second metrics into time slices. Each of the time slices includes a corresponding data structure for storing the data in the different time periods. Tumbling window processing is also performed on the ingested metrics by storing more data in the time slices for the first metrics having the first cardinality score relative to the second metrics having the second cardinality score.

Abstract: A system including a data repository storing metrics describing operational behavior of software programs executing in an enterprise system. The system also includes an application programming interface (API) gateway configured to receive the metrics. The system also includes an ingestion layer configured to ingest the metrics to form the ingested metrics. The system also includes a tumbling window processor configured to process the ingested metrics and the events into heat maps, sort the heat maps into the time slices, and populate the time slices with the ingested metrics.

Abstract: A method including receiving events from different data sources for a service automatically executing in an enterprise system. A first event is enriched by providing the first event with first metadata that associates the first event with a first application used by the service. The first event is assigned to a time slice associated with the first application. A second event is enriched in a similar manner. A correlation graph of nodes and edges is built using the enriched events, with nodes representing the events and edges indicating relationships between the edges. A third event indicating a fault in the first application associated with the first node is received. The source of the error for the third event is identified using the second updated correlation graph and the time slice. The source of error is then mitigated.

Abstract: A method including receiving events from different data sources for a service automatically executing in an enterprise system. A first event is enriched by providing the first event with first metadata that associates the first event with a first application used by the service. The first event is assigned to a time slice associated with the first application. A second event is enriched in a similar manner. A correlation graph of nodes and edges is built using the enriched events, with nodes representing the events and edges indicating relationships between the edges. A third event indicating a fault in the first application associated with the first node is received. The source of the error for the third event is identified using the second updated correlation graph and the time slice. The source of error is then mitigated.

Abstract: In one embodiment, a set of two or more workflow definitions is stored, wherein each workflow definition describes a workflow of an application. The set of two or more workflow definitions are used to implement a state machine of the application based at least in part on the two or more workflow definitions.

Abstract: Performing data synchronization is disclosed, including: receiving an indication to synchronize a container to a snapshot, wherein the container has a first data state and an identity, wherein the snapshot corresponds to a second data state; causing the container to have the second data state corresponding to the snapshot; and maintaining the identity of the container.

Abstract: Certain aspects of the present disclosure provide techniques for improved control of workflow execution. Embodiments include receiving, by an execution engine, a request from a user to execute a workflow that is stored in a repository. The workflow may be an operation that is associated with an operation privilege level, and a user privilege level of the user may be a lower privilege level than the operation privilege level. Embodiments include determining a repository privilege level associated with the repository by accessing repository privilege data in a file stored on the repository. Embodiments include escalating the user privilege level to the repository privilege level. Embodiments include executing the workflow, based on the request from the user, at the repository privilege level. Embodiments include restoring the user privilege level to the lower privilege level.

Abstract: Techniques to satisfy quality of service (QoS) requirements on a per virtual machine basis natively in a storage system are disclosed. In various embodiments, for each of a plurality of virtual machines a corresponding input/output (I/O) request queue is stored on the storage system. Requests are scheduled to be pulled from the respective request queues and added to a corresponding storage operation pipeline at the storage system in an order determined based at least in part on a per virtual machine quality of service parameter.

Abstract: Certain aspects of the present disclosure provide techniques for maintaining an application through an execution platform. An example method generally includes receiving a first workflow definition of a plurality of workflow definitions associated with an application. The first workflow definition may be a workflow defining a build operation for building the application. The first workflow definition is executed to build the application by retrieving an executable binary from a binary repository, retrieving source code for the application binary from an application source code repository, building the application binary by executing the executable binary on the retrieved source code, and storing the application binary in the binary repository. A second workflow definition is received to execute the application. The second workflow is executed to execute the application by retrieving the application binary from the binary repository, and executing the retrieved application binary to run the application.

Abstract: Storing data is disclosed, including: creating a clone of a snapshot comprising a first set of metadata associated with a source data, at least in part by generating for the clone a second set of metadata that includes an active index that is associated with the snapshot and is configured to store metadata associated with data values that are written to the clone; receiving a write operation to write a requested data value to the clone; and in response to the write operation, updating the active index based at least in part on the requested data value.

Abstract: Techniques to automatically allocate resources among storage system resource consumers are disclosed. In various embodiments, for each of a plurality of heterogeneous categories of resource consumer of the storage system a corresponding allocated portion of storage system resources to be available for use to perform operations associated with that category of resource consumer is determined. A storage system is configured automatically to provide access to resources of the storage system based at least in part on the respective portions of storage system resources allocated to each category of resource consumer, including by ensuring availability to workloads associated with each category at any given time at least a minimum amount of storage system resources corresponding to the portion of storage system resources allocated to that category.

Abstract: An execution platform comprising a workflow engine and an application engine is provided. A workflow definition associated with an application is received. The workflow definition is used to run an application workflow to perform an action with respect to the application, at least in part by causing an executable binary to be run by the application engine.

Abstract: In one embodiment, a set of two or more workflow definitions is stored, wherein each workflow definition describes a workflow of an application. The set of two or more workflow definitions are used to implement a state machine of the application based at least in part on the two or more workflow definitions.

Abstract: Performing replication of snapshots between storage systems is disclosed. A request to store at a destination system a snapshot data to represent at the destination system a state of a set of data at a first point-in-time is received. A first source system snapshot data that represents at a source system the state of the set of data at the first point-in-time depends on a second source system snapshot data that represents at the source system a state of the set of data at a second point-in-time. The snapshot data to represent at the destination system the state of the set of data at the first point-in-time is determined based on data comprising the first source system snapshot data and a destination system snapshot data that represents at the destination system a state of the set of data at a third point-in-time.

Abstract: A set of two or more workflow definitions is stored, wherein each workflow definition describes a workflow of an application. The set of two or more workflow definitions are used to implement a state machine of the application based at least in part on the two or more workflow definitions.