Rigor will occasionally need to make non-trivial changes to our underlying check-running platforms. The changes that warrant a designation of “platform upgrade” can range from switching to a new code library to upgrading hardware to revamping the infrastructure completely – anything that will fundamentally change the way that we process checks on the back-end.
- Benchmark checks
- Content checks
- Real Browser checks
- Uptime checks
How will a platform upgrade affect me?
Before we release a platform upgrade, we monitor and analyze the new platform to ensure that it will not negatively affect existing checks. However, we still feel that it’s best to provide a cutover grace period, giving customers the ability to opt-in for a certain period of time. While we don’t anticipate negative effects, no amount of simulation testing can fully prepare for a production release.
Note that we release our platform upgrades on an account-by-account basis – by the time you see a notice to upgrade, several other accounts have probably already upgraded their checks without issues.
How do I upgrade my checks to the new platform?
We will notify you via a callout at the top of every page within the monitoring.rigor.com application. You will be able to upgrade all checks at once or on a check-by-check basis.
You will be given several weeks’ lead-time to switch your applicable checks to the new platform yourself. If you don’t manually upgrade your checks by the deadline, they will be automatically upgraded for you.
Should I wait?
If you choose to wait and let our system automatically upgrade your checks for you, please make sure you have read the section below and contact support if you have any questions.
How will this affect my checks’ run histories and statistics?
When you upgrade checks yourself or allow our system to automatically upgrade them at the deadline, the checks will be switched to the new platform “in-place” – meaning their existing runs will remain intact and their future runs and statistics will be based on the new platform.
With any new platform, we expect some customers to see changes in check run data, such as response timings. Considerations must be made during transition periods, since averages taken across a platform change may be skewed.
In general, platform updates are driven by technological changes involving multiple updates and moving parts, making it impossible to pin down exactly why a timing is higher or lower. However, we expect timing data from new platforms to be accurate and consistent overall.
If you’d prefer to keep your current run histories and stats separate from those generated under the new platform, please contact support and we’d be happy to assist with that.