Same contextID for multipls tags can't be controlled via dlt-control command

[MAZEEM2]

In json file i have added the different keys for same tag.
{
"NAV-TomtomMessageProcessor": {
"tag": "NAV1",
"description": "firstTag"
},
"NAV-NavProviderInitiator": {
"tag": "NAV1",
"description": "SecondTag"
},
"c.t.n.s.c.NavAppClientImpl": {
"tag": "NAV1",
"description": "ThirdTag"
},
"ServiceIntentProvider": {
"tag": "NAV1",
"description": "FourthTag"
},
"ClientSDK": {
"tag": "NAV1",
"description": "FifthTag"
},
"c.t.n.s.a.c.d": {
"tag": "NAV1",
"description": "SixthTag"
},
}

And in dlt-logd-converter.cpp i have modified the values which will get read from the json.
string json_ctxID = (*iter)["tag"].asString();
string json_tag = iter.key().asString();

basically i swapped the key with tag and read it like this so that for different tags the context id should be same .
As of now in dlt-daemon 2.18.10 its only one-to-one mapping of tag with context id present
In my code i want to make it one-to-many means one contextid with many tags.
After doing this above changes i am able to see the context id is coming as NAV1 for all the tags in the dlt-viewer but for controlling its only controlling the single tag.

[AnandShastry]

you can raise as PR

[minminlittleshrimp]

Got it, it can be a new feature in dlt-logd-converter. You can raise PR and we can support merging.
Sorry for any late response.

[minminlittleshrimp]

Also, the dlt-logd-converter needs some refactoring due to not using the libjson APIs at all, but cumbersome with dummy things around handling unordered_map. This was developed long time ago based on logcat AOSP.