Abstract: Techniques are directed to detecting an abnormal event while data storage equipment is in transit. Such techniques involve receiving a series of sensor signals from a set of sensors affixed to the data storage equipment. The series of sensor signals identifies a series of positional integrity measurements for the data storage equipment while the data storage equipment is in transit. Such techniques further involve performing a series of comparison operations that compares the series of positional integrity measurements to a set of range. Such techniques further involve, based on the series of comparison operations, providing an abnormal event signal in response to a particular positional integrity measurement falling outside a corresponding range of the set of ranges.

Abstract: Techniques are provided for enabling cross-process coordination between multiple instances of given microservice in a cloud computing system. A method includes running a plurality of active instances of a given microservice of a computing system comprising a distributed microservices architecture. A first active instance of the plurality of active instances executes a portion of program code of the given microservice to perform a job. The portion of the program code of the given microservice includes an instance synchronization element which is configured to enable cross-process coordination between the plurality of active instances of the given microservice with the support of a collaboration service.

Abstract: Techniques are provided for tracking application programming interface (API) requests in a cloud computing environment. For example, a method for tracking API requests is implemented by an API gateway. The API gateway receives an API request which comprises a given API endpoint to access a target service of a computing system. The API gateway determines if the received API request is valid. In response to determining that the received API request is valid, the API gateway accesses at least one API counter associated with the given API endpoint of the received API request, wherein the at least one API counter is configured to count a number of times that the given API endpoint is accessed. The API gateway increments a count of the at least one API counter by one, and the API gateway routes the API request to the target service for execution.

Abstract: Techniques are provided to implement distributed application programming interface (API) whitelisting for access control of a computing system. For example, an API gateway receives a client API request to access an application comprising a distributed microservices architecture. The API gateway initiates a whitelisting validation operation determine if the client API request is permitted. The whitelisting validation operation includes comparing an API endpoint of the client API request to a whitelist of permitted API endpoints of registered microservices of the application to determine whether the API endpoint of the client API request comprises a permitted API endpoint in the whitelist. The API gateway routes the client API request to a target microservice of the application, in response to the whitelisting validation operation determining that the client API request is permitted.

Abstract: Techniques are provided to implement application programming interface (API) security validation testing for system integration testing (SIT) in a continuous integration environment. For example, a SIT tool detects a change in master code associated with an application comprising a plurality of microservices and an API gateway to route client API requests to the microservices of the application. The SIT tool obtains a listing of API endpoints exposed by the microservices of the application. The SIT tool performs an automated API security test validation process to determine whether an API security test file has been created for each API endpoint in the listing of API endpoints. The SIT tool fails the API security test validation process in response to determining that an API security test file has not be created for one or more API endpoints in the listing of API endpoints.

Abstract: Techniques are provided for enabling cross-process coordination between multiple instances of given microservice in a cloud computing system. A method includes running a plurality of active instances of a given microservice of a computing system comprising a distributed microservices architecture. A first active instance of the plurality of active instances executes a portion of program code of the given microservice to perform a job. The portion of the program code of the given microservice includes an instance synchronization element which is configured to enable cross-process coordination between the plurality of active instances of the given microservice with the support of a collaboration service.

Abstract: Techniques are provided for tracking application programming interface (API) requests in a cloud computing environment. For example, a method for tracking API requests is implemented by an API gateway. The API gateway receives an API request which comprises a given API endpoint to access a target service of a computing system. The API gateway determines if the received API request is valid. In response to determining that the received API request is valid, the API gateway accesses at least one API counter associated with the given API endpoint of the received API request, wherein the at least one API counter is configured to count a number of times that the given API endpoint is accessed. The API gateway increments a count of the at least one API counter by one, and the API gateway routes the API request to the target service for execution.

Abstract: Techniques are provided for automatically testing and verifying the functionality of push notification services of a cloud computing system. For example, a computing system performs an automated push notification test to test a push notification service of the computing system. The computing system sends a test push message over a communications network to a plurality of test devices that are located in different geolocations. The test devices are configured to automatically generate a response message in response to receiving the test push message. The computing system determines if a response message is received from each test device within a predefined response timeout period associated with the test device. The computing system determines that the push notification test fails in response to determining that a response message is not received from at least one test device within the predefined response timeout period associated with the at least one test device.

Abstract: Techniques are provided to implement intelligent test case management for system integration testing in a continuous development and integration environment. For example, a system integration testing (SIT) tool obtains feature information regarding features within a feature space of a computing system and an operational status of the features. The SIT tool obtains a plurality of test cases associated with a given feature of the computing system, wherein each test case is mapped to a set of one or more features within the feature space, which are utilized by the test case to execute a test procedure to test the given feature. The SIT tool selects each test case among the plurality of test cases, which is mapped to features that have an active operational status. The SIT tool executes the selected test cases to test the given feature.

Abstract: Techniques are provided for automatically testing and verifying the functionality of push notification services of a cloud computing system. For example, a computing system performs an automated push notification test to test a push notification service of the computing system. The computing system sends a test push message over a communications network to a plurality of test devices that are located in different geolocations. The test devices are configured to automatically generate a response message in response to receiving the test push message. The computing system determines if a response message is received from each test device within a predefined response timeout period associated with the test device. The computing system determines that the push notification test fails in response to determining that a response message is not received from at least one test device within the predefined response timeout period associated with the at least one test device.

Abstract: Techniques are provided to implement intelligent test case management for system integration testing in a continuous development and integration environment. For example, a system integration testing (SIT) tool obtains feature information regarding features within a feature space of a computing system and an operational status of the features. The SIT tool obtains a plurality of test cases associated with a given feature of the computing system, wherein each test case is mapped to a set of one or more features within the feature space, which are utilized by the test case to execute a test procedure to test the given feature. The SIT tool selects each test case among the plurality of test cases, which is mapped to features that have an active operational status. The SIT tool executes the selected test cases to test the given feature.

Abstract: Techniques are provided to implement application programming interface (API) security validation testing for system integration testing (SIT) in a continuous integration environment. For example, a SIT tool detects a change in master code associated with an application comprising a plurality of microservices and an API gateway to route client API requests to the microservices of the application. The SIT tool obtains a listing of API endpoints exposed by the microservices of the application. The SIT tool performs an automated API security test validation process to determine whether an API security test file has been created for each API endpoint in the listing of API endpoints. The SIT tool fails the API security test validation process in response to determining that an API security test file has not be created for one or more API endpoints in the listing of API endpoints.

Abstract: Techniques are provided to implement distributed application programming interface (API) whitelisting for access control of a computing system. For example, an API gateway receives a client API request to access an application comprising a distributed microservices architecture. The API gateway initiates a whitelisting validation operation determine if the client API request is permitted. The whitelisting validation operation includes comparing an API endpoint of the client API request to a whitelist of permitted API endpoints of registered microservices of the application to determine whether the API endpoint of the client API request comprises a permitted API endpoint in the whitelist. The API gateway routes the client API request to a target microservice of the application, in response to the whitelisting validation operation determining that the client API request is permitted.

Abstract: Techniques are directed to detecting an abnormal event while data storage equipment is in transit. Such techniques involve receiving a series of sensor signals from a set of sensors affixed to the data storage equipment. The series of sensor signals identifies a series of positional integrity measurements for the data storage equipment while the data storage equipment is in transit. Such techniques further involve performing a series of comparison operations that compares the series of positional integrity measurements to a set of range. Such techniques further involve, based on the series of comparison operations, providing an abnormal event signal in response to a particular positional integrity measurement falling outside a corresponding range of the set of ranges.

Abstract: Techniques for determining a view state for a user interface element are described. A first value for a feature key associated with the user interface element is determined in accordance with feature level criteria and a current context. The first value denotes a first view state for the user interface element. A second value for a second view state for the user interface element is determined in accordance with user interface element level criteria and the current context. A final view state for the user interface element is determined in accordance with the first view state and the second view state. The user interface element is rendered in a user interface in accordance with the final view state.

Abstract: There is disclosed a method and system for use in managing data storage. A plurality of discrete management operations is recorded in connection with a data storage system. A management operation is received in connection with the data storage system. The plurality of discrete management operations is analyzed in connection with the data storage system. Based on the analysis, a sequence of management operations performed on a predetermined number of occasions in connection with the data storage system is identified. The received management operation is one of the management operations in the sequence. A graphical user interface wizard is generated such that a user can be guided through at least a portion of the sequence of discrete management operations in response to identifying the sequence.

Abstract: Described are techniques for customizing a help system. A help system may be received providing help for a product. A proficiency level for a user may be determined in accordance with one or more proficiency criteria including one or more previous interactions of the user with any of the help system and performing an operation using a non-help feature of the product. A customized help system for the user may be determined for the user in accordance with the proficiency level for the user, wherein the customized help system is a modified version of the help system.

Abstract: A technique is directed to transporting data storage equipment. The technique involves electronically activating monitoring circuitry which is co-located with the data storage equipment. The technique further involves, after the monitoring circuitry is electronically activated, receiving location data from the monitoring circuitry while the data storage equipment is en route from a first ground location to a second ground location. The technique further involves, based on the location data, performing a set of location evaluation operations to determine whether the data storage equipment is on course along a predefined route between the first ground location and the second ground location.

Abstract: Described are techniques for use in connection with providing data protection. A storage resource for which data protection is provided by a data protection service may be identified. One or more criteria may be specified denoting one or more trigger conditions for providing data protection by the data protection service, wherein, responsive to an occurrence of any of the one or more trigger conditions, first processing may be performed by the data protection service to protect the storage resource. The one or more criteria may include a first criterion identifying a first amount of data change that has to occur with respect to the storage resource. Notification may be received regarding an occurrence of a first of the one or more trigger conditions. Responsive to receiving the notification, the first processing may be performed by the data protection service.

Abstract: Described are techniques for processing a request. Data storage system configuration information is provided which is used by a simulator that simulates a data storage system configuration of a data storage system. A request is received to perform an operation with respect to the data storage system configuration being simulated. The request identifies an object included in the data storage system configuration information used to simulate the data storage system configuration. First processing is performed to simulate servicing the request using the data storage system configuration information and the first processing includes determining, at run time while processing the request, whether the object includes a first object property that is a reference to an embedded object.