Package medianasms is an official library for working with mediana sms api.
Package smsactivate is a client for sms-activate.ru API.
Package sms provides the client and types for making API requests to AWS Server Migration Service. Amazon Server Migration Service automates the process of migrating servers to EC2. See https://docs.aws.amazon.com/goto/WebAPI/sms-2016-10-24 for more information on this service. See sms package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/sms/ To AWS Server Migration Service with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS Server Migration Service client SMS for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/sms/#New
A Go package that provides bindings to the Reach SMS REST API See https://www.reach-interactive.com/developers/api/
Banshee is a real-time anomalies(outliers) detection system for periodic metrics. We are using it to monitor our website and rpc services intefaces, including called frequency, response time and exception calls. Our services send statistics to statsd, statsd aggregates them every 10 seconds and broadcasts the results to its backends including banshee, banshee analyzes current metrics with history data, calculates the trending and alerts us if the trending behaves anomalous. For example, we have an api named get_user, this api's response time (in milliseconds) is reported to banshee from statsd every 10 seconds: Banshee will catch the latest metric 300 and report it as an anomaly. Why don't we just set a fixed threshold instead (i.e. 200ms)? This may also works but it is boring and hard to maintain a lot of thresholds. Banshee will analyze metric trendings automatically, it will find the "thresholds" automatically. 1. Designed for periodic metrics. Reality metrics are always with periodicity, banshee only peeks metrics with the same "phase" to detect. 2. Multiple alerting rule configuration options, to alert via fixed-thresholds or via anomalous trendings. 3. Coming with anomalies visualization webapp and alerting rules admin panels. 4. Require no extra storage services, banshee handles storage on disk by itself. 1. Go >= 1.4 and godep. 2. Node and gulp. 1. Clone the repo. 2. Build binary via `make`. 3. Build static files via `make static`. Usage: Flags: See package config. In order to forward metrics to banshee from statsd, we need to add the npm module statsd-banshee to statsd's banckends: 1. Install statsd-banshee on your statsd servers: 2. Add module statsd-banshee to statsd's backends in config.js: Require bell.js v2.0+ and banshee v0.0.7+: Banshee have 4 compontents and they are running in the same process: 1. Detector is to detect incoming metrics with history data and store the results. 2. Webapp is to visualize the detection results and provides panels to manage alerting rules, projects and users. 3. Alerter is to send sms and emails once anomalies are found. 4. Cleaner is to clean outdated metrics from storage. See package alerter and alerter/exampleCommand. 1. Detection algorithms, see package detector. 2. Detector input net protocol, see package detector. 3. Storage, see package storage. 4. Filter, see package filter. MIT (c) eleme, inc.
Banshee is a real-time anomalies(outliers) detection system for periodic metrics. We are using it to monitor our website and rpc services intefaces, including called frequency, response time and exception calls. Our services send statistics to statsd, statsd aggregates them every 10 seconds and broadcasts the results to its backends including banshee, banshee analyzes current metrics with history data, calculates the trending and alerts us if the trending behaves anomalous. For example, we have an api named get_user, this api's response time (in milliseconds) is reported to banshee from statsd every 10 seconds: Banshee will catch the latest metric 300 and report it as an anomaly. Why don't we just set a fixed threshold instead (i.e. 200ms)? This may also works but it is boring and hard to maintain a lot of thresholds. Banshee will analyze metric trendings automatically, it will find the "thresholds" automatically. 1. Designed for periodic metrics. Reality metrics are always with periodicity, banshee only peeks metrics with the same "phase" to detect. 2. Multiple alerting rule configuration options, to alert via fixed-thresholds or via anomalous trendings. 3. Coming with anomalies visualization webapp and alerting rules admin panels. 4. Require no extra storage services, banshee handles storage on disk by itself. 1. Go >= 1.4 and godep. 2. Node and gulp. 1. Clone the repo. 2. Build binary via `make`. 3. Build static files via `make static`. Usage: Flags: See package config. In order to forward metrics to banshee from statsd, we need to add the npm module statsd-banshee to statsd's banckends: 1. Install statsd-banshee on your statsd servers: 2. Add module statsd-banshee to statsd's backends in config.js: Require bell.js v2.0+ and banshee v0.0.7+: Banshee have 4 compontents and they are running in the same process: 1. Detector is to detect incoming metrics with history data and store the results. 2. Webapp is to visualize the detection results and provides panels to manage alerting rules, projects and users. 3. Alerter is to send sms and emails once anomalies are found. 4. Cleaner is to clean outdated metrics from storage. See package alerter and alerter/exampleCommand. 1. Detection algorithms, see package detector. 2. Detector input net protocol, see package detector. 3. Storage, see package storage. 4. Filter, see package filter. MIT (c) eleme, inc.
Package burner send sms over burner api Author: Z-M-Huang Repository: https://github.com/Z-M-Huang/go-burner License: MIT Note: Please do not abuse the Burner service!!!
HTTP API for sending SMS via SMPP.
Package ippanel is an official library for working with ippanel sms api.
Package ippanel is an official library for working with ippanel sms api.
Package ippanel is an official library for working with ippanel sms api.
HTTP API for sending SMS via SMPP.
Package ippanel is an official library for working with ippanel sms api.
Package onlinesim is a typed Go client for the OnlineSim SMS API (https://onlinesim.io) with support for temporary numbers, rent, free numbers, and webhooks.
Package ippanel is an official library for working with ippanel sms api.
Package africastalking is an unofficial AfricasTalking SDK providing SMS, Voice, Payment, Airtime, USSD API implementations Currently implemented services - SMS
Package adsefid is a client SDK for the adsefid.com SMS Web Service REST API.
Package ippanel is an official library for working with ippanel sms api.
Package smsgatewayhub is the official Go SDK for SMSGatewayHub: classic SMS API, CPaaS messages with channel fallback, OneTap Verify and Email Verification.
Package catzconnect is a secure, minimal SDK for sending encrypted communication requests — email, WhatsApp, push, SMS and phone calls — to the CatzConnect API, and for creating Voice & Video calls (see Calls).
Package goomzo is the Goomzo API for Go: send SMS and WhatsApp messages, send saved templates, keep customers in step, and check webhooks.