Opsview 6.8.x End of Support
With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.
The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.
Cloud - AWS - Route53 CloudWatch Opspack
Amazon Route 53 is a scalable and highly available Domain Name System (DNS). The name is a reference to TCP or UDP port 53, where DNS server requests are addressed. In addition to being able to route users to various AWS services, including EC2 instances, Route 53 also enables AWS customers to route users to non-AWS infrastructure. Amazon Route 53 supports full, end-to-end DNS resolution over IPv6. Recursive DNS resolvers on IPv6 networks can use either IPv4 or IPv6 transport to send DNS queries to Amazon Route 53. Route 53’s servers are distributed throughout the world.
What You Can Monitor Copied
Opsview Monitor’s AWS Route 53 Opspack provides detailed monitoring with various metrics across your AWS cloud. Opsview Monitor health checks help you track the percentage of healthy checks, statuses, and connection times to give your team insight into problems that can affect your IT estate.
Note: This Opspack knows when it was last run, so when testing the results in the troubleshoot section, you will need to wait a couple minutes each time you recheck the results. The time frame that is searched for is based around the last time the Opspack ran, so running it too quickly will result in no data being found and the service check going into an unknown
Service Checks Copied
| Service Check | Description |
|---|---|
| AWS/Route53.ChildHealthCheckHealthyCount | The number of health checks that are healthy. |
| AWS/Route53.ConnectionTime | The average time in milliseconds that a connection was established. |
| AWS/Route53.HealthCheckPercentageHealthy | The percentage of healthy health checks. |
| AWS/Route53.HealthCheckStatus | Health check status data is viewed across all regions. |
| AWS/Route53.SSLHandshakeTime | The average time, in milliseconds, that it took health checkers to complete the SSL handshake. |
| AWS/Route53.TimeToFirstByte | The average time, in milliseconds, that it took health checkers to receive the first byte of the response to an HTTP or HTTPS request. |
Prerequisites Copied
Opsview Cloud
For Opsview Cloud customers, please contact ITRS Support for assistance with these steps, as they require Orchestrator access.
To be able to monitor AWS CloudWatch services you need to add your AWS credentials to your Opsview Monitor server.
We recommend adding your AWS Access Key ID and AWS Secret Key ID to the default location (/opt/opsview/monitoringscripts/etc/plugins/cloud-aws/aws_credentials.cfg) using the following command after creating your aws_credentials.cfg file:
/opt/opsview/orchestrator/bin/orchestratorimportscripts etc-plugins cloud-aws /path/to/aws_credentials.cfg
This will set up the correct permissions for use. On a multi-cluster system, you can then run sync_monitoringscripts to distribute to all collectors at the same file location.
This credentials file should be in the following format:
[default]
aws_access_key_id = "Your Access Key Id"
aws_secret_access_key = "Your Secret Key Id"
If you are not using the default path, you will then need to assign your path to the variable: AWS_CLOUDWATCH_AUTHENTICATION.
Setup and Configuration Copied
Add the Host Template Copied
Add the Cloud - AWS - Route53 CloudWatch Host Template to your Opsview Monitor host. If the resource you’re monitoring has no hostname or public IP, then open the Advanced settings pane and change Host Check Command to Always assumed to be UP.
Note
For more information, refer to the documentation on Adding Host Templates to Hosts.
Add and configure the variables for the host Copied
| Variable | Description |
|---|---|
| AWS_CLOUDWATCH_AUTHENTICATION | Authentication details for CloudWatch. The Value is not used and therefore can be set to anything. Either override the File Path with the location of your credentials file, or override the Access Key and Secret Key arguments (this approach is recommended as the values will be encrypted). Optionally, override the Region (default: eu-west-1) with the location of your instance if you are not using the default region. |
| AWS_CLOUDWATCH_ROLE_ARN | This optional variable is the Amazon Resource Name (ARN) of the role to be used for the service checks. Override the Access ARN with the ARN of the role. The account should have AssumeRole(STS) for this ARN. |
| AWS_ROUTE53_HEALTH_CHECK_ID | Health Check ID taken from AWS. |
Note
For more information, refer to the documentation on Adding Variables to Hosts.
Apply Changes and Route 53 will now be monitored Copied
