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

(Azure Stream Analytics) Multivariate support for time series anomaly detection #1696

Open
dubansal opened this issue Nov 21, 2018 · 1 comment
Assignees
Labels
need info This issue needs more info before triage P2 Priority of the issue for triage purpose: Needs to be fixed at some point.

Comments

@dubansal
Copy link

System information

  • OS version/distro: All
  • .NET Version (eg., dotnet --info): All

Issue

  • What did you do? Azure Stream Analytics is currently running a private preview of built-in Anomaly Detection ML models.

  • What happened? In our discussions with several customers in private preview, lack of support for multi-variate A/D is coming up as a blocker to have them fully operationalize their hot path pipelines with this core feature. The list of customers include:

  1. Azure IoT Central (IoT SaaS solution) which uses Stream Analytics under the covers and are expected to grow to supporting '000s of IoT deployment by mid 2019. They require support for upto 4 variables.
  2. Stanley Black and Decker
  3. ATOS - European SI's IoT practice that works with many customers to build end to end IoT solutions.
  • What did you expect? N/A

Source code / logs N/A

Please paste or attach the code or logs or traces that would be helpful to diagnose the issue you are reporting.

@codemzs codemzs self-assigned this Nov 21, 2018
@shmoradims
Copy link

shmoradims commented Nov 26, 2018

@codemzs is this issue ready for triage or needs more info? If it's ready, please remove the 'need info' label and add it to 0.9 project for triage. Thanks.

@shmoradims shmoradims added the need info This issue needs more info before triage label Nov 26, 2018
@codemzs codemzs added the P1 Priority of the issue for triage purpose: Needs to be fixed soon. label Jun 30, 2019
@ganik ganik added P2 Priority of the issue for triage purpose: Needs to be fixed at some point. and removed P1 Priority of the issue for triage purpose: Needs to be fixed soon. labels Jan 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need info This issue needs more info before triage P2 Priority of the issue for triage purpose: Needs to be fixed at some point.
Projects
None yet
Development

No branches or pull requests

5 participants