The team has been hard at work over the last month. Check out our product updates for February. We’d love to hear any feedback about what we have been working on.
1. Monitoring from North American Azure and GCP regions
Recently, we added service monitors to provide better visibility into Azure and GCP platforms. This changed where Metrist service monitors originate. Previously, we originated all monitors from AWS. Now, AWS, Azure, and GCP monitors originate and run completely within vendors’ regions, (example: AWS service monitors for us-east-1 begin and complete all checks within the us-east-1 region, while an Azure service monitor will begin and check in the centralus region). This provides our users with clear visibility into how a specific region’s health and performance are doing.
The table below lists the 21 different AWS, Azure, and GCP regions that Metrist can now monitor.
| AWS | GCP | Azure |
| us-west-1 us-west-2 us-east-1 us-east-2 ca-central-1 |
northamerica-northeast1 northamerica-northeast2 us-central1 us-east1 us-east4 us-west1 us-west2 us-west3 us-west4 |
canadacentral centralus eastus eastus2 southcentralus westus westus2 |
2. Length-of-current-issue timer
To provide a better troubleshooting experience, we present how long a service monitor’s status has been degraded or down. This lets our users know if a monitor has been experiencing issues for hours, or if the status change just occurred.
What we are working on next
- Adding details to the service monitor user experience to support our users while troubleshooting a degraded or down third-party monitor:
- Updating the definition and criteria for what needs to be met for a service monitor to be considered down,
- Adding visibility into the current vendor status on the Metrist service monitor view, and,
- Adding more details to describe which calls are made by the checks within a service monitor.
That’s all for now. Please let us know what you think of these new features, and what other features you’d like to see.
