feat(transform): Add Metric Freshness Transform #178
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
utility_metric_freshness
transform with an exampleMotivation and Context
This makes it possible to measure message / data freshness (commonly used to measure data processing systems). Unlike other metric transforms, this emits two metrics with unique attributes to differentiate them in the downstream monitoring platform. A freshness SLO can be calculated by turning these metrics into a percentage (e.g.,
SLO = success / (success + failure)
for a particular pipeline).It's up to the user to determine when to begin measuring freshness (as determined by the
object.source_key
timestamp value), but two examples are:time_now
transform)How Has This Been Tested?
Integration tested using the example config. End-to-end testing will come after this is merged to main (as part of testing the next release).
Types of changes
Checklist: