Centralized configuration and change tracking for a computing platform
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.
1 . A method comprising:
identifying a software service and a change request, wherein the change request specifies that configuration data used by the software service was changed in a snapshot of the configuration data;
based on the change request, determining a set of configuration changes between the snapshot and a previous snapshot of the configuration data; and
generating a representation of the set of configuration changes indicating one or more parameters that were changed in the snapshot.
2 . The method of claim 1 , wherein identifying the software service and the change request is in response to determining that the software service satisfies a degradation criterion.
3 . The method of claim 2 , wherein determining that the software service satisfies the degradation criterion comprises detecting one or more of: an outage impacting the software service, reduced performance of the software service, or processor or memory utilization relating to the software service exceeding a threshold value.
4 . The method of claim 1 , wherein the representation of the set of configuration changes also includes 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 snapshot.
5 . The method of claim 1 , wherein determining the set of configuration changes is in response to receiving a selection of the snapshot and the previous snapshot.
6 . The method of claim 1 , wherein the software service is associated with one or more software applications, and wherein the one or more parameters that were changed in the snapshot of the configuration data are used by the one or more software applications.
7 . The method of claim 1 , further comprising:
providing, to a client device by way of a graphical user interface, a further representation of an alert that specifies the software service and the change request.
8 . The method of claim 1 , wherein determining the set of configuration changes comprises:
providing, to a client device, an adjustable timeline of a plurality of snapshots including the snapshot and the previous snapshot of the configuration data;
receiving, from the client device, a selection of the snapshot and the previous snapshot; and
determining, as the one or more parameters, parameters that were changed between the previous snapshot and the snapshot.
9 . The method of claim 1 , wherein each of the one or more parameters that were changed in the snapshot of the configuration data is represented as a key-value pair comprising a key that uniquely identifies a respective parameter and a value of the respective parameter.
10 . The method of claim 1 , wherein each of the one or more parameters that were changed in the snapshot of the configuration data is marked as either being newly added to the configuration data, removed from the configuration data, or edited within the configuration data.
11 . The method of claim 1 , wherein the representation of the set of configuration changes also indicates additional parameters that were not changed in the snapshot of the configuration data.
12 . The method of claim 1 , wherein the snapshot of the configuration data is deployed in a production environment, and wherein the previous snapshot is of the configuration data that was most recently deployed in the production environment prior to deployment of the snapshot.
13 . The method of claim 1 , wherein the configuration data is stored in a relational database, and wherein each element of the configuration data is represented as a different row of a database table of the relational database.
14 . The method of claim 1 , wherein determining the set of configuration changes comprises storing or identifying the representation of the set of configuration changes in a file, wherein the file is disposed within non-volatile memory.
15 . The method of claim 14 , wherein generating the representation of the set of configuration changes comprises:
receiving a specification of the file and a block number of a block of data within the file;
identifying, based on a block size, the block of data within the file;
making a copy of the block from the non-volatile memory to volatile memory; and
from the copy of the block in the volatile memory, generating the representation as a graphical user interface including a set of entries within the block.
16 . A non-transitory computer-readable medium storing program instructions that, when executed by one or more processors of a computing system, cause the computing system to perform operations comprising:
identifying a software service and a change request, wherein the change request specifies that configuration data used by the software service was changed in a snapshot of the configuration data;
based on the change request, determining a set of configuration changes between the snapshot and a previous snapshot of the configuration data; and
generating a representation of the set of configuration changes indicating one or more parameters that were changed in the snapshot.
17 . The non-transitory computer-readable medium of claim 16 , wherein determining the set of configuration changes between the snapshot and the previous snapshot of the configuration data is in response to receiving a selection of the snapshot and the previous snapshot.
18 . The non-transitory computer-readable medium of claim 16 , wherein identifying the software service and the change request is in response to determining that the software service satisfies a degradation criterion, and wherein determining that the software service satisfies the degradation criterion comprises detecting one or more of: an outage impacting the software service, reduced performance of the software service, or processor or memory utilization relating to the software service exceeding a threshold value.
19 . The non-transitory computer-readable medium of claim 16 , wherein determining the set of configuration changes comprises:
providing, to a client device, an adjustable timeline of a plurality of snapshots including the snapshot and the previous snapshot of the configuration data;
receiving, from the client device, a selection of the snapshot and the previous snapshot; and
determining, as the one or more parameters, those that were changed between the previous snapshot and the snapshot.
20 . A computing system comprising:
one or more processors;
memory; and
program instructions, stored in the memory, that upon execution by the one or more processors cause the computing system to perform operations comprising:
identifying a software service and a change request, wherein the change request specifies that configuration data used by the software service was changed in a snapshot of the configuration data;
based on the change request, determining a set of configuration changes between the snapshot and a previous snapshot of the configuration data; and
generating a representation of the set of configuration changes indicating one or more parameters that were changed in the snapshot.