Skip to content

v5.2.0
Compare
Choose a tag to compare
@elrayle elrayle released this 12 Dec 17:16
v5.2.0
4eaa815
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Action Required

This is a minor release that is fully backward compatible.

New Features

Control when monitoring page regenerates

It is a very slow process to run all the monitoring tests. The monitor page is setup to run the monitoring tests only once a day. The rest of the time, it reports back the results from the last test run.

Previously the expiration of these tests was a set time. The first access after the expiration time causes the full set of monitoring tests to run. It can now be controlled by configurations.

QaServer.config.preferred_time_zone_name = 'Eastern Time (US & Canada)' (default)
QaServer.config.hour_offset_to_run_monitoring_tests = 3 (default)

The offset is calculated from midnight. With the default values, the monitoring tests will expire at 3am ET. This places the slowdown at midnight PT/3am ET. To use on the west coast, the values would be 'Pacific Time (US & Canada)' and 0 for midnight to have the slowdown at midnight PT/3am ET.

NOTE: You can use a cron job or monitoring to visit the monitoring page just after the expiration time and again a while later to check the status once the tests have completed. This will prevent the slowdown from occurring during normal business hours.

Cache performance data

Instead of updating the performance history in the database with each request, it will now only write once a day. This addresses an issue where writing with every request was causing connection pool timeouts.

Change Log

  • set monitoring to expire nightly at 3am ET by default
  • save performance data once a day when running monitoring tests
  • setup travis-ci to run
Assets 2
Loading