Rigor Product Suggestions

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Trigger alert by error rate

    Besides trigger alert by 2,3 consecutive failures, I think it will be nice to have something like triggering alert when the error rate is higher than 5% in the past 3 hours or so. The reason is that sometimes there ARE some issues, but those issues may not appear consecutively.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Provide Graphs in Emails

    Provide a graphical representation of performance trending in emails, similar to what is displayed in the monitoring dashboard.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. alert sends request and response of the call that triggered the failed assertion

    We are trying to automate our error reporting. In order to do this we need to start grouping failures by the call involved and the failure response provided. We hope to use hubot to sort through the errors and only forward new, unknown ones to our slack channel. So what we need is to have the alerts include the request and response that triggered the failed assertion so that we can sort through these efficiently.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  5. Conditional alerting

    The notification conditions could be broadened to include notify after x failures within y time units.

    It would also be useful to have an option at the end of the test to send an alert or not based on the content of the json response. Some of our alerts are time sensitive, some can be dealt with later.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  6. Adding a checkbox "Do not start next test until current test completes"

    Our backend is stateful and things get messed up if a test starts before the next test is finished. This is not ordinarily a problem but can cause issues when there are aws outages.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  7. Set Custom color legend thresholds on Dashboards

    In trying to set up an Executive Dashboard, the default thresholds for how the coloring (Green, Yellow, Red) is applied to the dashboard are looser than the thresholds our executives would like to see.

    Example: The executive dashboards default to showing any avg uptime of 98-100% as green, 90-97% as yellow, and <90% as red. But because our sites need to be highly available, we'd rather have those thresholds be 99.9-100% green, 99.5-99.9% yellow, and <99.5% red. Similarly we'd like to be able to set thresholds for Response times.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Add Threshold Monitors for Page Reporting metrics

    We should be able to have Threshold Monitors for all the metrics available until the Page Report

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  9. When a node is unavailable do not send failure response

    When a node goes down for maintenance or other reasons the response it sends when trying to make either a uptime or real browser check should not be a failure. Currently this will trigger false positives where the node is down yet the service or page it is monitoring is actually indeed working.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  10. Email Trends for Recurring Tests

    Weekly/bi-weekly emails showing trends for recurring tests. This is very helpful for leads/managers to stay on top of optimizations.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Add support for uploading certificates to use with API Checks

    Some services and APIs require a valid certificate to be passed through in order to configure monitoring. It would be great if you could upload and store a certificate in Rigor so that people could have more robust Monitoring for APIs that require certificates.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. ICMP Ping

    A simple (ICMP) ping would be nice for monitoring devices that don't have a web-frontend.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  13. Ability to Limit Access to Status Page to Internal IP

    I would like to be able to share the status page with our internal employees without them having to login. But I would like to keep the status page internal so people outside of the company can't see the page.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  14. Reduce SUCCESS text messages to match FAILURE text messaging settings.

    We have NON location based alerting setup via SMS / TEXT message for any of our Uptime monitoring configurations.

    We correctly get Failure AND Success messages for each respect service status; however, since we have non-location based we expect 1 SMS for failure and 1 SMS for success.

    It seems that FAILURE SMS abides by the checkbox - Alert on Location specific failures - but SUCCESS does not. If I uncheck the box altogether (as we currently have it) - I still get 1 SMS for Failure but I get 3 (for 3 locations) Success texts.

    Can we make them…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rigor Monitoring  ·  Admin →
  15. Add international locations for Optimization

    We would like to have different location to run the Optimization checks.

    We would like to monitor performance for a site in Germany. The site is hosted at an AWS site in Germany and most of the audience would be in country.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Integration with Bamboo for Rigor Optimization

    Rigor Optimization currently integrates with Jenkins CI allowing you to include performance testing as a part of your development workflow.

    Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Rigor+Optimization+Plugin

    Many companies use Bamboo (Atlassian) for continuous delivery and it would be great to see Rigor build a native integration.

    Bambo site: https://www.atlassian.com/software/bamboo

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Notifications: Ability to Test User Notification Groups

    I have heard from a couple of customers that the ability to test notification groups would be helpful in a non-live situation to 1) make sure that they are set-up properly, and 2) test them after making changes.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. http/2 vs. http/1.1 option & recommendations for site speed testing

    Hi – I'm curious about what your service is now, or plans to do, about http/2 with respect to speed testing and recomendations.
    I've been reading how a lot of optimizations for http/1.1 become essentially obsolete and even problematic if done on http/2, due to the fact that http/2 is a single “pipe” and network connection vs. how http/1.1 requires round trips to the server.
    It makes me wonder if perhaps it makes sense for the speed testing tool to have a drop down or radio button selector in the speed test set up process to choose if the site…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
  19. Notify on Check Status Change

    We'd like to not only send notification and escalations when a check fails, but notify a specific group when someone has taken ownership of the issue in the Rigor tool, and a separate group to receive a "back on" notification. This will help our stakeholders notified that there were issues, but emphasize that IT is either working on the resolution, or it has been resolved.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  20. Bulk "Run Now" functionality

    To assist post-deployment validation we would like to run a more specific set of checks at once. To do this, we'd like to be able to filter by tag and select to "run all selected checks"

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

    Given our push into testing earlier in the lifecycle, and our recent 1st class Jenkins Integration via a plugin we wrote for Jenkins, this makes a lot of sense

  • Don't see your idea?

Rigor Product Suggestions

Feedback and Knowledge Base