Skip to content

feat: Add Plivo as an SMS and voice alert-notification provider #3271

Description

@sarveshpatil-plivo

What would you like to be added:

Plivo SMS and voice providers under alert/sender/provider/, so alerts can be delivered as a Plivo SMS or an outbound Plivo voice call, following the existing per-vendor provider pattern (Tencent, Aliyun).

Two providers: plivo_sms_provider.go (plivo-sms, POST …/Message/) and plivo_voice_provider.go (plivo-voice, POST …/Call/), registered in init.go with default templates in models/message_tpl.go.

They're config-driven like the existing providers (URL/method/body come from the notify-channel config). The code injects HTTP Basic auth (Auth ID + Auth Token) and treats 2xx as success (Plivo returns 202 for Message, 201 for Call). The scope is outbound only and the credentials are two secrets.

Why is this needed:

Nightingale ships built-in SMS/voice providers such as Tencent and Aliyun, but teams outside those regions have no SMS/voice alert channel and fall back to email or a generic webhook.

Plivo is a global CPaaS to send SMS and place calls, so it fills that gap as an alternative provider without introducing new concepts.

Implementation is drafted and I'm ready to open a PR.
Happy to adjust to your conventions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions