Service Graph connector for Observability Dynatrace - Cleanse OS Transform is not cleansing the OSIssue When using ETL to pull test data, The Service Graph Connector for Observability Dynatrace is not cleansing the OS as expected during the ETL transform. For instance, the end result of "cleansed_osVersion" such as "Windows Server 2019 Datacenter 1809 Ver. 10.0.17763" literally contains the same value as the uncleansed data in the original osVersion (for example Windows Server 2019 Datacenter 1809, ver) Customers would expect the "cleansed_os" value to be similar to "Windows Server 2019 Datacenter" rather then the value of "Windows" ReleaseAllCauseThe integration will not return the same values as those returned by the Discovery Process.ServiceGraph connectors do not work in the same way as the discovery. The cleanse os operation is part of integration commons and uses the script include sn_cmdb_int_util.CmdbIntegrationOsUtil. This script was derived from the original SCCM integration. This script include does only rudimentary cleansing to normalise that SCCM frequently saw. The script itself is working as intended. Service Graph does not intend to pickup content and manage a content database for operating system normalisation. This is outside of the scope of Service Graph connectors as they are not intended to achieve that yet.ResolutionCustomers have to write their own cleansing scripts to handle their cases. This is a viable approach as the behaviour also depends on their business needs.