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
Lets add support for fields that use valuesDoublesSketch in Numalogic. Currently, we dont support this natively. This is a frequently asked/used feature and its better to have default Numalogic support out-of-the-box.
What change needs making?
I have created this branch and PR: (#409) which supports latency based anomaly for a particular use case but this needs to be generalized for wider adoption. Major changes include adding configuration/YAML support for postaggregations, aggregations, percentile on top of this PR. These fields should be config driven.
Use Cases
When would you use this?
We would use this when ever the input fields use Sketches(https://datasketches.apache.org/) to represent the value. This is used when we represent the "actual values" by "approximate values" trading accuracy for computation.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Summary
Lets add support for fields that use valuesDoublesSketch in Numalogic. Currently, we dont support this natively. This is a frequently asked/used feature and its better to have default Numalogic support out-of-the-box.
What change needs making?
I have created this branch and PR: (#409) which supports latency based anomaly for a particular use case but this needs to be generalized for wider adoption. Major changes include adding configuration/YAML support for postaggregations, aggregations, percentile on top of this PR. These fields should be config driven.
Use Cases
When would you use this?
We would use this when ever the input fields use Sketches(https://datasketches.apache.org/) to represent the value. This is used when we represent the "actual values" by "approximate values" trading accuracy for computation.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: