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

[DYN-6451] Analytics for ML DataPipeline. #14936

Merged
merged 4 commits into from
Feb 16, 2024

Conversation

reddyashish
Copy link
Contributor

Purpose

Task: https://jira.autodesk.com/browse/DYN-6451

This PR is to add Analytics to the ML DataPipeline workflow. Sending the following info:

  1. The collection id we are using for the FDX API calls
  2. The data exchange id (returned by the first API call that creates the data exchange)
  3. The Dynamo host application
  4. Size of the binary that is sent.

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated
  • This PR contains no files larger than 50 MB

Release Notes

Analytics for ML DataPipeline.

Reviewers

@QilongTang @zeusongit

@QilongTang QilongTang added this to the 3.0.4 milestone Feb 13, 2024
Copy link

github-actions bot commented Feb 13, 2024

UI Smoke Tests

Test: success. 2 passed, 0 failed.
TestComplete Test Result
Workflow Run: UI Smoke Tests
Check: UI Smoke Tests - net8.0

@zeusongit
Copy link
Contributor

Do we need another PR on the Analytics repo to add the Category in whitelist file?

@@ -78,6 +78,8 @@ public static string ConstructCreateAssetRequestBody(string schemaNamespaceId, s
parameterComponent.AddParameterFromSchema("<Add dynamo host>", hostSchema);
parameterComponent.AddParameterFromSchema("<Add dynamo version>", dynamoVersionSchema);

Analytics.TrackEvent(Actions.DynamoMLDataPipieline, Categories.DynamoMLDataPipelineOperations, "Host", Convert.ToInt32(hostSchema));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't host name already part of each data entry? Do we still need to send it separately?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean Dynamo already sends host info(during startup or after it) to analytics, so we don't need it here. I was thinking we might want to know which host is sending a request to the ML pipeline and thats why we need it here. What do you think? It was added in the JIRA task.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this.

@QilongTang QilongTang merged commit dd9c7af into DynamoDS:master Feb 16, 2024
22 checks passed
@QilongTang
Copy link
Contributor

Please also cherry-pick

reddyashish added a commit to reddyashish/Dynamo that referenced this pull request Feb 23, 2024
* ML DataPipeline analytics

* comments

* comments

* Update DynamoMLDataPipeline.cs

(cherry picked from commit dd9c7af)
QilongTang pushed a commit that referenced this pull request Feb 23, 2024
* ML DataPipeline analytics

* comments

* comments

* Update DynamoMLDataPipeline.cs

(cherry picked from commit dd9c7af)
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

Successfully merging this pull request may close these issues.

3 participants