Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
MAZEEM2 opened this issue Nov 22, 2024 · 1 comment

Comments

@MAZEEM2
Copy link

MAZEEM2 commented Nov 22, 2024

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
Copy link

you can raise as PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants