(Legacy) Configure IBM Cloud Functions Channel

You can send alert notifications to an IBM Cloud Functions Channel by setting up a notification channel.
Deprecation Notice

IBM has deprecated IBM Cloud Functions. As of 28 December 2023, you can’t create new Functions entities. Existing Functions entities are supported until October 2024. From that date, any remaining Functions entities were deleted.

For details, see Using Cloud Functions.

For the latest documentation on configuring an IBM Cloud Function Channel, see Extracting notifications from Monitoring to IBM Cloud Event Streams.

Support

IBM Cloud Function notification channels are supported for the following use cases in Sysdig Monitor:

  • Alerts

The following notification channel types are supported:

  • Public (with or without X-Require-Whisk-Auth header).

  • Private (using IAM token).

Configure an IBM Cloud Function Channel

To configure IBM Cloud Functions Channel:

  1. Log in to Sysdig Monitor.

  2. Click the user icon in the bottom left corner.

  3. Select Settings.

  4. Select Notification Channels.

  5. Click Add Notification Channel.

    The configuration page appears.

  6. Specify the channel URL.

    You can specify one of the following channel types.

    • Public: The public channels are of type IBM Web Action. They require no authentication and can be used to implement HTTP handlers that respond with headers, status code, and body content of different types.

      An example URL is <https://eu-gb.functions.cloud.ibm.com/api/v1/namespaces/13eeeeee-123b-1234-ba12-1234bcbfee7b/actions/hello-world/myaction>

    • Private: The private channels are of type IAM Secured action. These actions require IAM token-based authentication.

      URL: An example URL is <https://eu-gb.functions.cloud.ibm.com/api/v1/web/namespaces/12eeeeee-123b-1234-ba12-1234bcbfee7b/actions/hello-world/helloworld?param=true>

  7. Continue with one of the following:

Configure a Private Channel

Specify the following:

  • IAM API Key: The IBM Cloud Identity and Access Management (IAM) API keys associated with your account. See IBM API Keys.

  • Channel Name: A unique name to identify the channel.

  • Enable the channel and desired notification types:

    • Enabled: The toggle button to enable or disable the IBM channel.

    • Notify when Resolved: Send a new notification when the alert condition is no longer triggered. Enable or disable the notification toggle as appropriate.

    • Notify when Acknowledged: Send a new notification when the alert is manually acknowledged by a user. Enable or disable the notification toggle as appropriate.

    • Test notification: Send a notification when the changes are saved. Enable or disable the notification toggle as appropriate.

  • Shared With: Choose whether this channel can be used by All Teams or the Current Team you are logged in as.

  • Additional Parameters: Specify optional parameters to pass to the function. For example, name: jane is passed to the action as {name: "Jane"}.

Configure a Public Channel

Specify the following:

  • Whisk Auth Token (optional): Optionally provide the Whisk authentication token. If you specify one, the public channel (web action) can only be invoked by requests that provide appropriate authentication credentials. See Securing web actions for more details.

  • Channel Name: A unique name to identify the channel.

  • Enable the channel and desired notification types:

    • Enabled: The toggle button to enable or disable the IBM channel.

    • Notify when Resolved: Send a new notification when the alert condition is no longer triggered. Enable or disable the notification toggle as appropriate.

    • Notify when Acknowledged: Send a new notification when the alert is manually acknowledged by a user. Enable or disable the notification toggle as appropriate.

    • Test notification: Send a notification when the changes are saved. Enable or disable the notification toggle as appropriate.

  • Shared With: Choose whether this channel can be used by All Teams or the Current Team you are logged in as.

  • Additional Parameters: Specify optional parameters to pass to the function. For example, hostname: BLR is passed to the action as {hostname: "BLR"}. The URL would be /demo/hello.http?hostname=BLR.