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

chore(dm): add tracking plan stat per event level #2673

Closed

Conversation

abhimanyubabbar
Copy link
Contributor

Description of the change

Description here

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

Fix #1

Checklists

Development

  • Lint rules pass locally
  • The code changed/added as part of this pull request has been covered with tests
  • All tests related to the changed code pass in development

Code review

  • This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
  • "Ready for review" label attached to the PR and reviewers mentioned in a comment
  • Changes have been reviewed by at least one other engineer
  • Issue from task tracker has a link to this pull request

} catch (error) {
exception = true;

const errMessage = `Error occurred while validating : ${error}`;
logger.error(errMessage);
Copy link
Collaborator

Choose a reason for hiding this comment

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

add event name in logger to pin point where error happened

@codecov
Copy link

codecov bot commented Sep 29, 2023

Codecov Report

Attention: 15 lines in your changes are missing coverage. Please review.

Comparison is base (4d6c4b8) 87.01% compared to head (9beba0c) 87.02%.
Report is 4 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2673      +/-   ##
===========================================
+ Coverage    87.01%   87.02%   +0.01%     
===========================================
  Files          635      635              
  Lines        28296    28301       +5     
  Branches      6711     6717       +6     
===========================================
+ Hits         24621    24629       +8     
+ Misses        3341     3338       -3     
  Partials       334      334              
Files Coverage Δ
src/controllers/trackingPlan.ts 27.27% <0.00%> (ø)
src/services/trackingPlan.ts 16.66% <0.00%> (+0.87%) ⬆️

... and 7 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

workspaceId: event.metadata?.workspaceId,
trackingPlanId: event.metadata?.trackingPlanId,
status: errorReport?.status,
violationType: errorReport.violationType ? errorReport.violationType : '',
Copy link
Collaborator

Choose a reason for hiding this comment

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

one event can have multiple violations. We can stop capturing this info

@@ -8158,6 +8157,7 @@
},
"node_modules/available-typed-arrays": {
"version": "1.0.5",
"dev": true,
Copy link
Collaborator

Choose a reason for hiding this comment

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

remove changes from package-lock file

public static async validateTrackingPlan(events, requestSize, reqParams) {
/**
* validate takes in events as argument and iterates over the events
* validating them using the tracking
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
* validating them using the tracking
* validating them using the tracking plan

...metaTags,
});
}
const failure = await eventValidator.handleValidation(parsedEvent);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
const failure = await eventValidator.handleValidation(parsedEvent);
const validatedEvent = await eventValidator.handleValidation(parsedEvent);

@devops-github-rudderstack
Copy link
Contributor

This PR is considered to be stale. It has been open for 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.

@devops-github-rudderstack devops-github-rudderstack deleted the chore.add-tracking-plan-stat-per-event branch December 30, 2023 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants