You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have recent shipped new metric aggregation APIs.
However, standard metric extraction uses old internal APIs.
We need to
a) Change the extractor to use the new APIs
b) Remove the old APIs.
This will not affect any public APIs or any public configuration options. However, customers who used reflection to access V1 MetricManager APIs will be broken.
The text was updated successfully, but these errors were encountered:
Yes, V2 is public, V1 is internal.
There is not guidance to migrate since V1 was internal. The extractors using V1 are public but transitioning them to V2 should not have any publicly observable effect, except a small performance improvement.
We have recent shipped new metric aggregation APIs.
However, standard metric extraction uses old internal APIs.
We need to
a) Change the extractor to use the new APIs
b) Remove the old APIs.
This will not affect any public APIs or any public configuration options. However, customers who used reflection to access V1 MetricManager APIs will be broken.
The text was updated successfully, but these errors were encountered: