Invoke Anomaly Detection with OCI Streaming

Anomaly Detection is a synchronous REST API-based service that you can use to detect anomalies with the OCI Streaming service.

This combination allows you to input data into a Streaming service stream, then Anomaly Detection performs a detect call on this data stream, which results in the output data being put in another stream.

The OCI Service Connector Hub service is designed to connect different services together. When you use Service Connector Hub to connect Anomaly Detection, Functions, and Streaming, you can design a solution to detect the anomalies in your streaming data. The solution design is as follows:

  1. Specify an input stream using Streaming.

  2. Specify an output stream using Streaming.

  3. Create a Functions as a Service (FaaS) that invokes Anomaly Detection.

  4. Create another FaaS that returns the Anomaly Detection results as the output of the FaaS.

  5. Finally, use Service Connector Hub to put the FaaS output into the output stream.

Shows how to connect streams, function, and service connector hub to the anomaly detection service.

Detect Anomalies in Streaming Data with Anomaly Detection

Before you begin, you must have:

  • A trained model ready to use for this process. Change the following properties in the sample code to create your FaaS application.

    • endpoint

    • model_id

    • stream_id

    • message_endpoint

    • partition_id

  • Ensure that you have set up the Anomaly Detection service policies.

  • Set these polices so that the Functions service can call the Anomaly Detection service:

    1. Create a dynamic group for the function:

      All { = <compartment_id>, resource.type = 'fnfunc' }
    2. Add these permissions for the dynamic group:
      DEFINE dynamic-group AD_SERVICE_CALLING_FUNC as <function_dynamic_group>
      ALLOW dynamic-group AD_SERVICE_CALLING_FUNC to use ai-service-anomaly-detection-model in compartment <compartment_name>
Use this solution to detect anomalies in streaming data:
  1. Create both an input and an output stream in the Streaming service using one of the various methods.
  2. Create an application in the Functions service to use to create the FaaS.

    After the application is active, you can add a function to it.

  3. Click the application name from the list.
  4. Click Getting Started to begin creating your FaaS.
  5. Click Local Setup.
  6. Follow the instructions to set up your FaaS and use this to invoke it by replacing the environment values with your own.

    Ensure that the FaaS is active before continuing.

  7. (Optional) You have to enable logging if you want to use logs to help you debug your FaaS, click Logs, click the Actions icon, and then click Enable Log and specify:
      • Compartment: The compartment in which to create the log. By default, the current compartment.
      • Log Group: The log group in which to create the log. Select an existing log group, or select:
        • Auto-create a default log group to create a default log group with a default name, if one doesn't exist already.
        • Create a new log group to create a log group with a name and description that you provide.
      • Log Name: The name of the new log. By default, <application-name>_invoke.
      • Log Retention: The length of time to retain log data.
    1. Click Enable Log to create the log (and the new log group, if you specified one).
  8. Create a service connector in the Service Connector Hub service using the Use Manual Settings option to configure the task.

    If you don't have the required policies configured to create service connectors, this creation step helps you to configure them.

  9. Specify your input and output streams with the task being the FaaS that you created.
  10. Click Create to complete the setup.

Now, any messages that are sent to the input stream are passed on to the Anomaly Detection service. The results from the Anomaly Detection service are sent to the output stream.