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

How to set cV, ingest PartA extension, user#authId through SDK? #1181

Open
TedaLIEz opened this issue Jun 28, 2023 · 6 comments
Open

How to set cV, ingest PartA extension, user#authId through SDK? #1181

TedaLIEz opened this issue Jun 28, 2023 · 6 comments
Labels
question Further information is requested

Comments

@TedaLIEz
Copy link
Contributor

TedaLIEz commented Jun 28, 2023

Hello team,

I am trying to compare the telemetry data before and after migrating to the 1DS SDK. I have noticed that some properties are missing after the migration, specifically:

  1. Record#cV
  2. Record#ingest
  3. Record#user#authId

I am wondering if it is possible for the Android client to set these properties through the API. Although these properties are defined in the bond schema, I have not been able to assign them. Can you please provide me with some guidance on how to do this?

@TedaLIEz TedaLIEz added the question Further information is requested label Jun 28, 2023
@TedaLIEz
Copy link
Contributor Author

TedaLIEz commented Jun 29, 2023

@lalitb @anod friendly ping for this issue, could you please help?

@anod
Copy link
Member

anod commented Jul 2, 2023

We don't use OneCollector, I'm not familiar with its properties

@TedaLIEz
Copy link
Contributor Author

TedaLIEz commented Jul 3, 2023

@anod @lalitb I was wondering if you're familiar with the Common Schema. We're trying to align the data before and after using the 1DS SDK to minimize the impact.

Currently, we're using the old CLL library as our telemetry framework, which sends data to the Vortex in CS 2.1 format. We're planning to emit events via 1DS to the Aria in CS 4.0 format.

If you have any knowledge or resources related to this, please let me know. Thank you!

@lalitb
Copy link
Contributor

lalitb commented Jul 3, 2023

@TedaLIEz -

If you are trying to set the authId for the User part A extension - it should be accessible via custom decorator concept. Search API examples for "Decorator".

To set the cv value, you can use event_name.SetProperty(CorrelationVector::PropertyName, corr_vec_value);

@TedaLIEz
Copy link
Contributor Author

TedaLIEz commented Jul 4, 2023

@lalitb Yes, I've noticed this CorrelationVector::PropertyName and I tried to set this property with SetProperty in Kotlin wrapper API, but I failed to get the value in the Aria via OneCollector endpoint. I'll try to reach out to the Aria support team for confirmation.

Another topic here is I don't see any code related to the extIngest in the record structure, do you have the plan to support this extension?

@TedaLIEz
Copy link
Contributor Author

TedaLIEz commented Jul 4, 2023

And I don't find any API related to set authId in the EventProperties.

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

No branches or pull requests

3 participants