Feat: Add support for json resources #633
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a json column for resources in logs and traces
fixes SigNoz/signoz#8199
We are just writing the string map data here.
So if the key is
"service.name" : "hello"
it will be stored as
{"service": {"name":"hello"}
but since we are unsuring that we are writing string map, values containing json won't be affected and will be stored as flattened one. And for resource attributes that will be rarely the case.
The QB changes are here SigNoz/signoz#8376 , but will need a plan to rollout i.e we can rollout directly for new users and then move the old ones later.