Schema Considerations - 1 tag key instead of multiple field keys

Store
2

@Ivo_Andreev Can you share some more information about what kind of data is being collected? Is there any way to migrate to a newer collector that writes more standardized schema?

Also is there any way to normalize the data coming from the machines? Are there some common groupings between the different attributes being written (i.e. can you combine all of the pressure values)?

The second option you mention is a possible way to handle this case. Just so I understand you, the points in that case would look as follows?

legacy_data,machine=81423819190,tagID=temperature tagValueInt=1i,tagValueFloat=1,tagValueString="1" TS
legacy_data,machine=81423873104,tagID=pressure tagValueInt=1i,tagValueFloat=1,tagValueString="1" TS
legacy_data,machine=81423819190,tagID=partCounter tagValueInt=1i,tagValueFloat=1,tagValueString="1" TS
legacy_data,machine=81423873104,tagID=foo tagValueInt=1i,tagValueFloat=1,tagValueString="1" TS