AWS vs Azure Anomaly Detector Process

Source: https://towardsdatascience.com/effective-approaches-for-time-series-anomaly-detection-9485b40077f1

Data flow

  1. Ingests data from the various stores that contain raw data to be monitored by Anomaly Detector.
  2. Aggregates, samples, and computes the raw data to generate the time series or calls the Anomaly Detector API directly if the time series is already prepared and responds with the detection results.
  3. Queue the anomaly-related metadata.
  4. The serverless app picks the message from the message queue based on the anomaly-related metadata and sends the alert about the anomaly.
  5. Stores the anomaly detection metadata.
  6. Visualize the results of the time series anomaly detection.

Components

Alternatives

  1. The Orchestrator (solution owner or DevOps engineer) launches the solution in the AWS account and selects the desired options (for example, using Amazon SageMaker Registry, or providing an existing S3 bucket).
  2. The Orchestrator uploads the required assets for the target pipeline (for example, model artifact, training data, and/or custom algorithm zip file) into the Assets S3 bucket. If Amazon SageMaker Model Registry is used, the Orchestrator (or an automated pipeline) must register the model with the Model Registry.
  3. A single account AWS CodePipeline instance is provisioned by either sending an API call to the API Gateway or by committing the mlopsconfig.json file to the Git repository. Depending on the pipeline type, the Orchestrator AWS Lambda function packages the target AWS CloudFormation template and its parameters/configurations using the body of the API call or the mlops-config.json file and uses it as the source stage for the AWS CodePipeline instance
  4. The DeployPipeline stage takes the packaged CloudFormation template and its parameters/configurations and deploys the target pipeline into the same account.
  5. After the target pipeline is provisioned, users can access its functionalities. An Amazon Simple Notification Service (Amazon SNS) notification is sent to the email provided in the solution’s launch parameters.

Components

--

--

--

Bigdata/Hadoop/Devops/AWS/AZURE

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Web Application Testing: A viewpoint Introduction A web application testing can be referred to…

LLVM — Writing Pass Instrumentations for the New PassManager

Ultimate Dashboard Pro v3.5.2 — Full Control Over Your WordPress Dashboard

ultimate dashboard hero

Get Your Microservices Reactive

Enter HackerLink Via Slope Wallet App to Vote for Hackathon

Pick a hosting company

NLU Chatbot Evaluation- 3 Common Errors and 5 Key Steps

The Future is All Purple

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Narendra Reddy

Narendra Reddy

Bigdata/Hadoop/Devops/AWS/AZURE

More from Medium

Notify Azure Cost to Slack Every Day from AWS Lambda with Python

How to succeed and twice fail for AWS Glue Developer Endpoint and Apache Zeppelin

Understand New Generation of file formats in 5 minutes — JSON vs. AVRO vs. PARQUET vs. ORC

Using AWS Systems Manager Parameter Store to Handle Credentials for Multiple Regions