Service Connector Hub will read the logs and trigger Oracle Functions that create a custom message and call Syniverse API to send the SMS.
More
As you make your way through this tutorial, look out for this icon 
.
Whenever you see it, it's time for you to perform an action.
Before you proceed further, ensure you have followed all the steps outlined in the parent README file located in oci-notification-syniverse
Review the following files in the current folder:
- the code of the function, func.py
- its dependencies, requirements.txt
- the function metadata, func.yaml
In Cloud Shell, run the fn deploy command to build this function and its dependencies as a Docker image,
push the image to the specified Docker registry, and deploy this function to Oracle Functions
in the application created earlier:
fn -v deploy --app <app-name>
e.g.,
fn -v deploy --app myapp
In Cloud Shell, run the following fn invoke command to unit test this function:
fn invoke <app-name> <function-name> < test-logs.json
e.g.,
fn invoke myapp oci-logs-to-syniverse-python < test-logs.json
You should see the SMS notifications sent by Syniverse.
-
From the OCI Console navigation menu, select Logging, and then select Log Groups.
-
Click Create Log Group, select your compartment, add a Name and Description
-
Select Logs in the left menu, click Enable Service Log, select your compartment, select Log Category on Service and fill the rest of the fields appropriately.
-
From the navigation menu, select Logging, and then select Service Connectors.
-
Click Create Connector, add a Name, Description, select the compartment, select the source as Logging and Target as Functions.
-
On Configure Source connection, select the compartment, select the Log Group created earlier
-
On Configure Target connection, select the compartment and select the Function name. If prompted to create a policy for writing to Function, click Create.
Make sure you configure basic observability for your function and connector using metrics, alarms and email alerts: