Skip to content

Conversation

nick-Ag
Copy link
Contributor

@nick-Ag nick-Ag commented Aug 20, 2025

This PR adds new tags to the metrics tracked for Liquid Functions, including the projectId to narrow down metrics to users. This is a followup to #3024

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

Successfully tested in staging - the tags come back as expected:
Screenshot 2025-08-18 at 10 01 56 AM

  • Added unit tests for new functionality
  • Tested end-to-end using the local server
  • [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
  • [Segmenters] Tested in the staging environment
  • [Segmenters] [If applicable for this change] Tested for regression with Hadron.

@nick-Ag nick-Ag requested a review from a team as a code owner August 20, 2025 18:27
@nick-Ag nick-Ag changed the title [liquid metrics ] Adds items from Subscription object to tags [liquid metrics] Adds items from Subscription object to tags Aug 20, 2025
Copy link

codecov bot commented Aug 20, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.03%. Comparing base (bbc9237) to head (92abb05).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3189   +/-   ##
=======================================
  Coverage   80.03%   80.03%           
=======================================
  Files        1229     1229           
  Lines       24524    24524           
  Branches     5015     5020    +5     
=======================================
  Hits        19627    19627           
  Misses       4135     4135           
  Partials      762      762           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment on lines +731 to +736
`partnerAction:${subscription.partnerAction}`,
`actionId:${subscription.ActionID}`,
`configId:${subscription.ConfigID}`,
`projectId:${subscription.ProjectID}`,
`subscriptionName:${subscription.name}`,
`subscriptionSubscribe:${subscription.subscribe}`
Copy link
Contributor

Choose a reason for hiding this comment

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

@nick-Ag - this could be expensive. Do we really need this data? If so how long?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we should permanently collect these metrics to monitor any issues in this feature. Is there a way to project the cost impact of adding these tags?

Copy link
Contributor

Choose a reason for hiding this comment

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

all metrics included here are of high cardinaility. I would recommend reaching out in #help-datadog for getting latest metric costs and estimating them.

Copy link
Contributor

Choose a reason for hiding this comment

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

can we throw an error with unique erorr type and use our existing hc.metrics for capturing these metrics?

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

Successfully merging this pull request may close these issues.

3 participants