Do you use RunScope to test your API, and StatusPage to show it all off to your customers? Don't want to write bindings for both APIs? If yes, RunscopeStatuspage is perfect for you.
Add this line to your application's Gemfile:
gem 'runscope_statuspage'
And then execute:
$ bundle
Or install it yourself as:
$ gem install runscope_statuspage
In a nutshell, each call will grab metrics from RunScope then send them over to StatusPage, once per call. There is no scheduling done by this gem, it is left as an exercise for the reader. Ideally, you will want to use something such as Sidekiq or Resque to fire these jobs off every few minutes/hours. Keep in mind that StatusPage will rate-limit requests to its API, one request per minute.
from general to specific:
opts = {:status => "page status (either 'investigating|identified|monitoring|resolved')",
:twitter_update => 'do you want to post status to twitter (bool)',
:fail_on => 'number of failures to induce statuspage update (int, default 0)',
:no_sp => skip statuspage.io report and return data}
opts = {:bucket_names => 'list of names of buckets containing radars',
:status => "page status (either 'investigating|identified|monitoring|resolved')",
:twitter_update => 'do you want to post status to twitter (bool)',
:fail_on => 'number of failures to induce statuspage update (int, default 0)',
:no_sp => skip statuspage.io report and return data}
opts = {:bucket_name => 'name of bucket containing radars',
:status => "page status (either 'investigating|identified|monitoring|resolved')",
:twitter_update => 'do you want to post status to twitter (bool)',
:fail_on => 'number of failures to induce statuspage update (int, default 0)',
:no_sp => skip statuspage.io report and return data}
opts = {:bucket_name => 'name of bucket containing radars',
:radar_names => 'list of names of radars within bucket',
:status => "page status (either 'investigating|identified|monitoring|resolved')",
:twitter_update => 'do you want to post status to twitter (bool)',
:fail_on => 'number of failures to induce statuspage update (int, default 0)',
:no_sp => skip statuspage.io report and return data}
opts = {:bucket_name => 'name of bucket containing radars',
:radar_name => 'name of radar within bucket',
:status => "page status (either 'investigating|identified|monitoring|resolved')",
:twitter_update => 'do you want to post status to twitter (bool)',
:fail_on => 'number of failures to induce statuspage update (int, default 0)',
:no_sp => skip statuspage.io report and return data}
status must be either investigating|identified|monitoring|resolved.latest_radar_result in any of the above, it will not halt execution. This is to prevent breaking integrations when a new test is added and runscope_statuspage polls before it has the chance to run.Usage:
@client = RunscopeStatuspage::RunscopeAPI.new "token"
Usage:
@client = RunscopeStatuspage::StatspageAPI.new "token"
0.1.7
working. Alerts will no longer be fired for working tests; if failures occur they will be caught on next execution.0.1.6
0.1.5
:no_sp to available options so that data can be returned instead of posting to statuspage.io. Useful for SMS notifications.0.1.4
@rs and @sp.0.1.3
RunscopeStatuspage to use options = {} hash for better readability.opts[:fail_on] threshold parameter for greater granularity.StatuspageAPI.clear_metric_data0.1.2
0.1.1
0.1.0
After checking out the repo, run bin/setup to install dependencies. Then, run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release to create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.
git checkout -b my-new-feature)git commit -am 'Add some feature')git push origin my-new-feature)The MIT License (MIT)
Copyright (c) 2015 David Stancu
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Unknown package
We found that runscope_statuspage demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.