Storage system configuration change tracking for root cause/troubleshooting
Architectures and techniques are described that can monitor or track change to storage system configuration. Changes to the configuration that are determined to be statistically significant in potentially affecting and/or causing performance issues of the storage system can be specifically tracked. Such can be accomplished by generating a hash data of the configuration data and sorting that hash data to data buckets based on a similarity score to other hash data of other storage systems.
1. A system, comprising:
a processor; and
a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:
receiving configuration data comprising configuration parameters, of a storage system, that have been determined to be significant, according to a significance criterion, with respect to correcting a first previous storage system issue;
generating hash data comprising hashing the configuration data;
determining a similarity score associated with the hash data, wherein the similarity score represents a similarity to other hash data other than the hash data, that was hashed with respect to a second previous storage system issue; and
sorting the hash data into one of a group of data buckets based on the similarity score.
2. The system of claim 1 , wherein the configuration data is determined to be significant according to the significance criterion in response to an examination of a support request data store that stores information relating to issues, comprising the first previous storage system issue and the second previous storage system issue, that have arisen for a group of storages systems comprising the storage system.
3. The system of claim 2 , wherein the configuration data is determined to be significant according to the significance criterion in response to a chi-squared test procedure applied to the information of the support request data store.
4. The system of claim 1 , wherein the hashing of the configuration data comprises hashing the configuration data according to a min-hash function.
5. The system of claim 1 , wherein the generating of the hash data comprises generating multiple hash signatures comprising a hash signature for each of multiple columns of the configuration data.
6. The system of claim 5 , wherein the hash data is stored to a data structure comprising a time stamp column indicative of a time that the hash data was generated and a combined hash column indicative of a concatenation of the multiple hash signatures.
7. The system of claim 1 , wherein the sorting of the hash data into one of the group of data buckets comprises sorting the hash data according to a nearest neighbor algorithm.
8. The system of claim 1 , wherein the operations further comprise storing the hash data to a change tracking data store that comprises the group of data buckets, wherein the change tracking data store comprises multiple records of the hash data, and wherein a first record of the multiple records describes the configuration parameters of the storage system at a first time and a second record of the multiple records describes the configuration parameters of the storage system at a second time, different than the first time.
9. The system of claim 8 , wherein the operations further comprise training a predictive model from the hash data stored in the change tracking data store, and wherein the predictive model is configured to identify a substantial change to a parameter of the configuration parameters of the storage system between the first time and the second time.
10. The system of claim 9 , wherein the predictive model is further configured to determine the substantial change to the parameter is a cause of an issue regarding the storage system in response to an examination of a previous support request associated with a different storage system having different hash data that has been sorted to a same data bucket, of the group of data buckets, as the hash data of the storage system.
11. The system of claim 10 , wherein the operations further comprise:
determining that a support request has been received in connection with the storage system, wherein the support request indicates an issue associated with operation of the storage system; and
presenting an indication of the previous support request.
12. The system of claim 10 , wherein the operations further comprise:
determining that a support request has been received in connection with the storage system, wherein the support request indicates an issue associated with operation of the storage system;
determining that the substantial change to the parameter of the storage system that is identified by the predictive model has resulted in the hash data associated with the storage system being sorted to a different one of the group of buckets than previously sorted; and
presenting an indication of the substantial change.
13. A non-transitory computer-readable medium comprising instructions that, in response to execution, cause a system comprising a processor to perform operations, comprising:
receiving configuration data that has been determined to be significant with respect to a first storage system issue that has previously arisen, wherein the configuration data is indicative of a configuration of a storage system;
generating hash data as a result of hashing the configuration data;
determining a similarity score for the hash data, wherein the similarity score represents a similarity to other hash data that was hashed with respect to a second storage system issue that arose; and
sorting the hash data into one of a group of data buckets based on the similarity score.
14. The non-transitory computer-readable medium of claim 13 , wherein the configuration data is determined to be significant in response to an examination of a support request data store that stores information relating to issues, comprising that first storage system issue and the second storage system issue, that have arisen for a group of storages systems comprising the storage system.
15. The non-transitory computer-readable medium of claim 13 , wherein the configuration data is determined to be significant in response to a chi squared test procedure applied to the information of the support request data store.
16. The non-transitory computer-readable medium of claim 13 , wherein the hashing the configuration data comprises hashing the configuration data according to a min-hash function.
17. A method, comprising:
receiving, by a device comprising a processor, configuration data that has been determined to be significant with respect to a first storage system issue that has arisen, wherein the configuration data is indicative of a configuration of a storage system;
generating, by the device, hash data in response to hashing the configuration data;
determining, by the device, a similarity score of the hash data, wherein the similarity score represents a similarity to other hash data, that was hashed with respect to a second storage system issue that has arisen; and
sorting, by the device, the hash data into one of a group of data buckets based on the similarity score.
18. The method of claim 17 , further comprising storing, by the device, the hash data to a change tracking data store that comprises the group of data buckets, wherein the change tracking data store comprises multiple records of the hash data, and wherein a first record of the multiple records describes the configuration of the storage system at a first time and a second record of the multiple records describes the configuration of the storage system at a second time, different than the first time.
19. The method of claim 17 , further comprising training, by the device, a predictive model from the hash data stored in the change tracking data store, wherein the predictive model is configured to identify a significant change to the configuration of the storage system between the first time and the second time.
20. The method of claim 17 , further comprising determining, by the device, the significant change to the configuration is a cause of an issue regarding the storage system in response to an examination of a previous support request associated with a different storage system having different hash data that has been sorted to a same data bucket, of the group of data buckets, as the hash data of the storage system.