Servicenow, Inc.

Swapnesh Patel

Sridhar Chandrashekar

Viral Shah

Kiran Kumar Bushireddy

Ravindra Bansal

Michael Steven Ludwig

Benny Van De Sompele

Anurag Garg

Anjali Chablani

Brian James Waplington

Kanwaldeep Kaur Dang

Anand Nikhil Mehta

Hyung Kim

Naga Padmaja Vattikuti

Anand Vitthal Karandikar

Manish P Gupta

Bnayahu Makovsky

Kurt Joseph Zettel, Ii

Rao Subrahmanyeswara Surapaneni

Joshua J Goldstein

Tal Kapon

Navindra Sharma

Scott Michael Stone

Jude Ian McQuaid

Krishna Chaitanya Thota

Satish Babu Krishnamoorthy

Rukshan Felix Perera

Filip Deryckere

Sonam Gupta

Mark Jason Harun

Alessandro Buzzatti

An embodiment may involve, in response to determining that a software service satisfies a degradation criterion, generating an alert that indicates the software service and a change request specifying that configuration data used by the software service was changed in a current snapshot of the configuration data; based on the change request, determining a set of configuration changes between the current snapshot and a previous snapshot of the configuration data; and providing a representation of the set of configuration changes indicating one or more parameters that were changed in the current snapshot and one or more paths in a tree-based arrangement of the configuration data that lead to the one or more parameters that were changed in the current snapshot.

Centralized configuration and change tracking for a computing platform

Systems and methods are provided for dynamic selection of anomaly detection options for particular metric data. Metric data corresponding to one or more configuration items of an information technology (IT) infrastructure is collected. A selected anomaly detection action option that applies to the metric data is identified. An action is performed using the metric data, based upon the selected anomaly detection action option. A dashboard graphical user interface (GUI) display results of the action.

Dynamic anomaly reporting

Persistent storage may be arranged to store sets of configuration data respectively corresponding to applications. One or more processors of a computational instance may be configured to: receive, from a data source, a set of configuration data corresponding to an application deployable on a network related to the computational instance, wherein the set of configuration data defines components, packages, and environments, wherein the packages include one or more of the components, and wherein the environments include one or more of the packages; write, to the persistent storage, a representation of the set of configuration data; look up one or more policies applicable to the set of configuration data; and validate, by a policy engine, the set of configuration data by applying the one or more policies to the set of configuration data.

Centralized configuration data management and control

Information technology discovery data items are received from a plurality of different discovery sources. The received information technology discovery data items are stored in a multisource data store. The received information technology discovery data items from the plurality of different discovery sources are reconciled to determine an attribute value of a configuration item. The determined attribute value of the configuration item is stored in a configuration management database (CMDB).

Configuration item determination based on information technology discovery data items from multiple sources

Transformation configuration data is set for a consumer replication set on a consumer instance to replicate on the consumer instance data of a source table included in a producer replication set on a producer instance. The transformation configuration data includes configuration data of at least one of: (i) a target table from among a plurality of tables on the consumer instance that is specified in the consumer replication set as a table for loading on the consumer instance, incoming data from the source table; and (ii) a specified mapping of incoming fields of the source table with respective fields of the target table. Replication event data of a data modification event associated with a record on the source table is received. The received replication event data is transformed based on the set transformation configuration data, and loaded on the target table.

Transformation configuration in instance data replication with bi-directional replication support

A failure resistant distributed computing system includes primary and secondary datacenters each comprising a plurality of computerized servers. A control center selects orchestrations from a predefined list and transmits the orchestrations to the datacenters. Transmitted orchestrations include less than all machine-readable actions necessary to execute the orchestrations. The datacenters execute each received orchestration by referencing a full set of actions corresponding to the received orchestration as previously stored or programmed into the computerized server and executing the referenced full set of actions. At least one of the orchestrations comprises a failover operation from the primary datacenter to the secondary datacenter. Failover shifts performance of task from a set of processing nodes of the primary datacenter to a set of processing nodes of the secondary datacenter, such tasks including managing storage accessible by one or more remote clients and running programs on behalf of remote clients.

Failure resistant distributed computing system

A method for replicating instance data includes: detecting, based on producer instance replication configuration data, a data modification event associated with a record of a replication target table included in a replication set of the producer instance; generating replication event data of the data modification event when the data modification event is determined to be eligible for replication based on predetermined criteria included in the producer replication configuration data; placing the encrypted replication event data on an outbound replication queue to transport the replication event data to a logging infrastructure for replication; reading, at a consumer instance subscribing to the replication set of the producer instance, the replication event data from the logging infrastructure based on consumer instance replication configuration data; and loading a record onto a replication destination table of the consumer instance based on the read replication event data.

Instance data replication

Growing community of inventors

Bothell, WA, United States of America

Swapnesh Patel