Abstract: A request to sign a provided payload is received, wherein the payload includes an automation script specified to execute on one or more management service instances. The automation script is validated, including by modifying the payload to add metadata data associated with the validation. An encrypted version of a digital signature private key that was received is sent to a credential system. An unencrypted version is received and used to sign the modified payload. The signed modified payload is provided in response to the request to sign the provided payload. The signed modified payload is configured to, in response to a request to execute the automation script on the one or more of the management service instances, be verified using a public key corresponding to the digital signature private key and allow a validation of the automation script at least in part by using the included added metadata.

Abstract: Persistent storage contains a parent table and one or more child tables, the parent table containing: a class field specifying types, and one or more filter fields. One or more processors may: receive a first request to read first information of a first type for a first entity; determine that, in a first entry of the parent table for the first entity, the first type is specified in the class field; obtain the first information from a child table associated with the first type; receive a second request to read second information of a second type for a second entity; determine that, in a second entry of the parent table for the second entity, the second type is indicated as present by a filter field that is associated with the second type; and obtain the second information from a set of additional fields in the second entry.

Abstract: Persistent storage contains a parent table and one or more child tables, the parent table containing: a class field specifying types, and one or more filter fields. One or more processors may: receive a first request to read first information of a first type for a first entity; determine that, in a first entry of the parent table for the first entity, the first type is specified in the class field; obtain the first information from a child table associated with the first type; receive a second request to read second information of a second type for a second entity; determine that, in a second entry of the parent table for the second entity, the second type is indicated as present by a filter field that is associated with the second type; and obtain the second information from a set of additional fields in the second entry.

Abstract: The present approach relates generally to systems and methods for outputting metric data from resources with a database accessible by a client instance. The client instance is hosted by one or more data centers and accessible by one or more remote client networks. In accordance with the present approach, a request to track metric data related to a resource is received. Further, a configuration item (CI) is retrieved from a database accessible by the client instance based at least in part on data associated with the request. Further, a type of CI is identified. Even further, a resource type associated with the type of the CI is identified based at least in part on a resource abstraction layer accessible by the client instance. Further still, the resource type is linked to the resource table and metric data associated with the resource is outputted.

Abstract: A server system may include one or more hardware processors that execute computer-readable instructions from a non-transitory memory that cause the processor to receive a time component associated with a query request and one or more relational identification tags associated with a subset of a plurality of data items stored in one or more databases. The processor may then query the one or more databases to identify one or more time series data items based on the time component and the relational identification tags. After querying the databases, the processor may transmit the one or more time series data items to a computing device configured to display the one or more time series data items.

Abstract: A request to sign a provided payload is received, wherein the payload includes an automation script specified to execute on one or more management service instances. The automation script is validated, including by modifying the payload to add metadata data associated with the validation. An encrypted version of a digital signature private key that was received is sent to a credential system. An unencrypted version is received and used to sign the modified payload. The signed modified payload is provided in response to the request to sign the provided payload. The signed modified payload is configured to, in response to a request to execute the automation script on the one or more of the management service instances, be verified using a public key corresponding to the digital signature private key and allow a validation of the automation script at least in part by using the included added metadata.

Abstract: Systems, methods, and media for connecting using aliases. During operation, such as an API, an operation is called that utilizes a connection to a remote device. When this operation is attempted, information may be requested to complete the connection. The information may include credentials or connection information about a target device for the connection. An appropriate alias is used to request the suitable information.

Abstract: A server system may include one or more hardware processors that execute computer-readable instructions from a non-transitory memory that cause the processor to receive a time component associated with a query request and one or more relational identification tags associated with a subset of a plurality of data items stored in one or more databases. The processor may then query the one or more databases to identify one or more time series data items based on the time component and the relational identification tags. After querying the databases, the processor may transmit the one or more time series data items to a computing device configured to display the one or more time series data items.

Abstract: A computing system may involve a time-series server device and computing devices. The time-series server device may be configured to: receive and store pre-defined trigger configurations; receive and store time-series data, wherein the pre-defined trigger configurations define states and/or state transitions for the received time-series data; apply, by way of a trigger engine, the pre-defined trigger configurations to the received time-series data to determine observed states and/or state transitions in the time-series data; and store, in transition storage, representations of the observed states and/or state transitions. One or more applications operating on computing devices may be configured to: transmit the pre-defined trigger configurations to the time-series server; transmit a stream of the time-series data to the time-series server; and repeatedly poll and receive, by way of a plurality of worker threads, the representations of the observed states and/or state transitions from the transition storage.

Abstract: A server system may include one or more hardware processors that execute computer-readable instructions from a non-transitory memory that cause the processor to receive a time component associated with a query request and one or more relational identification tags associated with a subset of a plurality of data items stored in one or more databases. The processor may then query the one or more databases to identify one or more time series data items based on the time component and the relational identification tags. After querying the databases, the processor may transmit the one or more time series data items to a computing device configured to display the one or more time series data items.

Abstract: A node of an application instance in a distributed computing environment can be selectively hibernated and the execution of the node selectively restarted by first detecting a condition of the node that satisfies a criterion for hibernating the node. The node may then be hibernated by suspending execution of the node on a server and initiating execution of a listener. The listener can use a network port that the node used before the execution of the node was suspended. At a later time, a request from a client to the application instance can be received by the listener. The request can be a request to restart execution of the node. Responsive to the request and a determination that the server has a predefined amount of resources for permitting execution of the node, the execution of the node on the server can be restarted.

Abstract: A computing system may involve a time-series server device and computing devices. The time-series server device may be configured to: receive and store pre-defined trigger configurations; receive and store time-series data, wherein the pre-defined trigger configurations define states and/or state transitions for the received time-series data; apply, by way of a trigger engine, the pre-defined trigger configurations to the received time-series data to determine observed states and/or state transitions in the time-series data; and store, in transition storage, representations of the observed states and/or state transitions. One or more applications operating on computing devices may be configured to: transmit the pre-defined trigger configurations to the time-series server; transmit a stream of the time-series data to the time-series server; and repeatedly poll and receive, by way of a plurality of worker threads, the representations of the observed states and/or state transitions from the transition storage.

Abstract: The present approach relates generally to systems and methods for outputting metric data from resources with a database accessible by a client instance. The client instance is hosted by one or more data centers and accessible by one or more remote client networks. In accordance with the present approach, a request to track metric data related to a resource is received. Further, a configuration item (CI) is retrieved from a database accessible by the client instance based at least in part on data associated with the request. Further, a type of CI is identified. Even further, a resource type associated with the type of the CI is identified based at least in part on a resource abstraction layer accessible by the client instance. Further still, the resource type is linked to the resource table and metric data associated with the resource is outputted.

Abstract: A computing system may involve a time-series server device and computing devices. The time-series server device may be configured to: receive and store pre-defined trigger configurations; receive and store time-series data, wherein the pre-defined trigger configurations define states and/or state transitions for the received time-series data; apply, by way of a trigger engine, the pre-defined trigger configurations to the received time-series data to determine observed states and/or state transitions in the time-series data; and store, in transition storage, representations of the observed states and/or state transitions. One or more applications operating on computing devices may be configured to: transmit the pre-defined trigger configurations to the time-series server; transmit a stream of the time-series data to the time-series server; and repeatedly poll and receive, by way of a plurality of worker threads, the representations of the observed states and/or state transitions from the transition storage.

Abstract: An example embodiment may involve receiving, by a server device that stores a plurality of access credentials for computing devices that are disposed within a managed network, a request containing a label and an indication of an application service. The server device may be disposed within a remote network management platform that remotely manages the managed network. The example embodiment may further involve mapping, by the server device, the label and the application service to an endpoint identifier of a target computing device that is disposed within the managed network. The endpoint identifier may be associated with particular access credentials that are usable to access the application service executing on the target computing device. The example embodiment may further involve transmitting, by the server device, the endpoint identifier and the particular access credentials.

Abstract: A node of an application instance in a distributed computing environment can be selectively hibernated and the execution of the node selectively restarted by first detecting a condition of the node that satisfies a criterion for hibernating the node. The node may then be hibernated by suspending execution of the node on a server and initiating execution of a listener. The listener can use a network port that the node used before the execution of the node was suspended. At a later time, a request from a client to the application instance can be received by the listener. The request can be a request to restart execution of the node. Responsive to the request and a determination that the server has a predefined amount of resources for permitting execution of the node, the execution of the node on the server can be restarted.

Abstract: A distributed backup method includes defining a server group having a plurality of server computers, and providing each server computer with an identical backup policy and an identical storage policy. The method also includes transmitting, at each server computer of the server group to every other server computer of the server group, advertisement messages describing available storage space for storing backups, and receiving, at each server computer from the server, at least some of the advertisement messages. The method also includes identifying, at a first server computer using the backup policy, at least a first service to be backed up, selecting a second server computer using the received advertisement messages, transmitting, from the first server computer to the second server computer, a backup including information corresponding to the at least one service, and storing the backup, by the second server computer using the storage policy.

Abstract: Systems, methods, and media for connecting using aliases. During operation, such as an API, an operation is called that utilizes a connection to a remote device. When this operation is attempted, information may be requested to complete the connection. The information may include credentials or connection information about a target device for the connection. An appropriate alias is used to request the suitable information.

Abstract: A computing system may involve a time-series server device and computing devices. The time-series server device may be configured to: receive and store pre-defined trigger configurations; receive and store time-series data, wherein the pre-defined trigger configurations define states and/or state transitions for the received time-series data; apply, by way of a trigger engine, the pre-defined trigger configurations to the received time-series data to determine observed states and/or state transitions in the time-series data; and store, in transition storage, representations of the observed states and/or state transitions. One or more applications operating on computing devices may be configured to: transmit the pre-defined trigger configurations to the time-series server; transmit a stream of the time-series data to the time-series server; and repeatedly poll and receive, by way of a plurality of worker threads, the representations of the observed states and/or state transitions from the transition storage.

Abstract: A distributed backup method includes defining a server group having a plurality of server computers, and providing each server computer with an identical backup policy and an identical storage policy. The method also includes transmitting, at each server computer of the server group to every other server computer of the server group, advertisement messages describing available storage space for storing backups, and receiving, at each server computer from the server, at least some of the advertisement messages. The method also includes identifying, at a first server computer using the backup policy, at least a first service to be backed up, selecting a second server computer using the received advertisement messages, transmitting, from the first server computer to the second server computer, a backup including information corresponding to the at least one service, and storing the backup, by the second server computer using the storage policy.