Cloud Monitoring
Cloud Monitoring Service End-of-Service Notice
The Cloud Monitoring service currently provided will end on December 31, 2026. Accordingly, existing Cloud Monitoring projects will be available until December 31, 2026, and metric collection through these projects will end starting January 1, 2027.
Afterward, you can switch to OpenMetrics. The migration may require installing an agent or changing configurations, and the collection method and billing criteria may change.
You can respond to failures in real time by checking cloud monitoring service metrics. When using cloud services, failures that affect operations can occur. For example, problems may arise with user asset status, the host machine (physical server computer), or the network.
It is also a good idea to check in advance whether there are any anomalies in the cloud namespace or region. This is a great help when responding to failures in the cloud infrastructure later.
WhaTap Cloud Monitoring connects to the cloud provider's APIs and collects all metrics and cloud events in real time. There are two main types of metrics:
- Metrics to determine whether your instances (virtual servers) are healthy
- Cloud service provider's own availability metrics
The metrics collection interval can be adjusted from real time (5-minute intervals) to 3 hours for cost optimization.
With WhaTap Cloud Monitoring, you can check the collected data on a Flex board. This allows you to analyze the causes of failures directly.
You can also set alerts by email, SMS, and messenger (Slack, Telegram, etc.).
Supported products
WhaTap supports the following five cloud environments. Check the installation and configuration in the documentation for the environment you use.
- Namespace is a way to group services for an application.
- A region in the cloud indicates a set of data centers that are installed to provide cloud services.
- If you select a region, the user data is stored in the data centers of the region.
- Select a project and then check the cloud monitoring in Management > Cloud Monitoring under the Project Menu.
Configuration
-
Create a user with the following permissions in the AWS account you want to monitor.
- CloudWatchReadOnlyAccess
- AmazonEC2ReadOnlyAccess
-
Enter the access key/secret key or Amazon resource name (ARN).
Supported list
The following is a list of AWS-supported namespaces.
- AWS ACMPrivateCA
- AWS AmazonMQ
- AWS ApplicationELB Monitoring
- AWS AppSync
- AWS Athena
- AWS AutoScaling
- AWS Elastic Beanstalk Health
- AWS Billing
- AWS Cassandra
- AWS Chatbot
- AWS Cloud Front
- AWS CloudHSM
- AWS CloudSearch
- AWS CodeBuild
- AWS CodeGuruProfiler
- AWS Cognito
- AWS Connect
- AWS ContainerInsights Monitoring
- AWS DataSync
- AWS DAX
- AWS DDoSProtection
- AWS DMS
- AWS DocDB
- AWS DX
- AWS Dynamo DB
- AWS Ebs Usage
- AWS EC2 Monitoring
- AWS EC2 Alert Config
- AWS EC2Spot
- AWS ECS
- AWS EFS
- AWS ElastiCache Usage
- AWS ElasticGPUs
- AWS ElasticInference
- AWS ElasticMapReduce
- AWS ElasticTranscoder
- AWS Classic ELB Monitoring
- AWS ES
- AWS Events
- AWS Firehose
- AWS FSx
- AWS GameLift
- AWS GatewayELB
- AWS Glue
- AWS GroundStation
- AWS Health
- AWS Inspector
- AWS IoT
- AWS IoTAnalytics
- AWS IoTSiteWise
- AWS IVS
- AWS Kafka
- AWS Kinesis
- AWS KinesisAnalytics
- AWS KinesisVideo
- AWS KMS
- AWS Lambda
- AWS Lex
- AWS Location
- AWS Logs
- AWS LookoutMetrics
- AWS MediaConnect
- AWS MediaConvert
- AWS MediaPackage
- AWS MediaStore
- AWS MediaTailor
- AWS ML
- AWS NATGateway
- AWS Neptune
- AWS NetworkELB
- AWS NetworkFirewall
- AWS OpsWorks
- AWS Polly
- AWS QLDB
- AWS RDS Monitoring
- AWS Redshift
- AWS Robomaker
- AWS Route53
- AWS S3
- AWS SageMaker
- AWS SDKMetrics
- AWS ServiceCatalog
- AWS SES
- AWS SNS
- AWS SQS
- AWS SQS Message
- AWS SSM-RunCommand
- AWS States
- AWS StorageGateway
- AWS SWF
- AWS Textract
- AWS ThingsGraph
- AWS Timestream
- AWS Transfer
- AWS TransitGateway
- AWS Translate
- AWS TrustedAdvisor
- AWS Api Usage
- AWS VPN Monitoring
- AWS WAF
- AWS WorkMail
- AWS WorkSpaces