Support Environment
Before installing the agent, check that your target environment meets the following requirements.
Last updated: 2026-08-26
Service deployment models
You can use WhaTap Monitoring as a SaaS or on-premises (self-hosted) service. Whichever you choose, you use the same agents and the same monitoring features.
| Deployment | Support | Description |
|---|---|---|
| SaaS | ✅ | Connects to collection servers operated by WhaTap. See the firewall section for regional addresses |
| On-premises (self-hosted) | ✅ | Collection servers you build and operate yourself (air-gapped environments supported). Contact your sales representative for the scope |
You can also deploy WhaTap on-premises in air-gapped environments without internet connectivity.
Feature differences by deployment model
Whichever you choose, the monitoring features are the same. The mobile app is the only exception and is available on the service.whatap.io SaaS service only.
To use certain features on-premises, a separate agreement is required.
Application Monitoring
| Platform | Supported version |
|---|---|
| Java | Java 6 to Java 21 |
| Node.js | Node.js 17.0.0 or later |
| PHP | PHP 5.2 or later, 7.0 or later, 8.0 to 8.4 |
| Python | Python 3.7 to 3.13 |
| .NET | .NET Framework 4.6.1 to 4.8, .NET Core 6, 7, 8, 9 |
| Go | Go 1.18 or later |
Server Monitoring
| OS | Supported version |
|---|---|
| Linux | Debian 6.0 or later |
| Ubuntu 12.04 or later | |
| CentOS 5.0 or later | |
| Red Hat 5.0 or later | |
| Rocky Linux 8.6 or later | |
| All versions of Amazon Linux | |
| SUSE 10.1 or later | |
| Unix | FreeBSD 10 or later |
| AIX 6.1 or later | |
| HP-UX 11.31(IA64), HP-UX 11.23(IA64, PA-RISC) | |
| Solaris 10, Solaris 11.2, Solaris 11.3, Solaris 11.4 | |
| Windows | Windows 2008 R2 or later |
Database Monitoring
Agent minimum installation specifications
-
CPU: Approximately 20 agents can be installed per core (may differ depending on the DB server load).
-
Memory: 200 MB
-
Disk: 100 MB (Agent space of 50 MB + Log file generation space of 50 MB)
Minimum installation requirements based on the number of agents
| Number of installed agents | CPU | Memory | Disk |
|---|---|---|---|
| 10 | 1-core | 2 GB | 1 GB |
| 20 | 1-core | 4 GB | 2 GB |
| 40 | 2-core | 8 GB | 4 GB |
Agent operation method
The DB agent basically operates in the following way:
-
Execution cycle: 5 secs (default)
-
Number of queries performed: 5 to 6
-
Speed: It terminates within 1 second when the server load is normal.
-
Up to 2 sessions (5-second collection session, other information collection session)
When a timeout occurs during collection query, the DB agent operates in the following way to minimize the load.
-
Do not run a new collection query until the previous collection query has finished.
-
If the timeout exceeds 12 seconds (exceeds 2 refresh cycles), the session is reconnected after termination.
-
If timeout occurs 3 times or more, wait 10 seconds and try again.
Depending on the load status of the DB server, it may take a long time or a timeout may occur until the result of a collection query appears on the WhaTap monitoring service screen.
Supported versions by database type
| Database | Supported version |
|---|---|
| Oracle | Oracle 10g or later |
| Tibero | Tibero 5.x or later |
| CUBRID | CUBRID 9 or later |
| MS-SQL | SQL Server 2005 or later |
| MySQL | MySQL 5.5 or later |
| MariaDB | MariaDB 5.5 or later |
| Altibase | Altibase 6 or later |
| Redis | Redis 3.2 or later |
| MongoDB | MongoDB 4.2 or later |
| PostgreSQL | PostgreSQL 9.2 or later (e.g. EDB, Tmax OpenSQL) |
-
With DB Monitoring, a monitoring account with DB metadata (Dictionary, performance_schema) inquiry role is required.
-
The XOS agent can be applied to only the OS environment running on the x86 architecture.
-
For more information about supported features for each database platform, see the following.
V2 support versions by platform
The following describes the DBX agent versions that support the V2 project for each platform.
| Platform | Agent Version |
|---|---|
| PostgreSQL | v1.6.7 |
| MySQL | v1.6.8 |
| Oracle | v1.9.0 |
| Oracle Pro | DMX agent is separately provided. |
| MongoDB | v1.7.0 |
| Redis | v1.7.0 |
| Altibase | v2.0.0 |
| CUBRID | v2.1.0 |
| SQL Server | 2.2.0 (TBA) |
Kubernetes Monitoring
WhaTap Kubernetes supports standard Kubernetes version 1.16 or later and the equivalent Kubernetes environments.
| Platform | Managed service |
|---|---|
| EKS | Amazon Elastic Kubernetes Service |
| AKS | Azure Kubernetes Service |
| GKE | Google Kubernetes Engine |
| OKE | Oracle Container Engine for Kubernetes |
| Naver Cloud | Naver Cloud Kubernetes Service |
| NHN | NHN Kubernetes Service (NKS) |
| Kakao i Cloud | Kakao i Cloud |
| Openshift | Red Hat OpenShift (3.x / 4.x) |
| Cocktail | Cocktail |
| Accordion | Accordion |
| PaaS-TA | PaaS-TA |
| Rancher | Rancher |
Supporting the NVIDIA GPU
AI Agent Observability
| Language | Supported models |
|---|---|
| Python | OpenAI, Anthropic |
| Java | JDK 21 or later, Spring Boot 4.0 or later, Spring AI 2.0.0-M1 ~ M3 |
NMS (Network Management System)
| Platform | Supported version |
|---|---|
| Python | 3.9 to 3.12 |
| Linux | Ubuntu 22.04, 23.04, 24.04 |
| Rocky 8.10, 9.4 | |
| Redhat 8.10 |
Cloud Monitoring
See the following 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
Log Monitoring
Logs can be collected from Java, PHP, Python, and Server applications. For the supported agents, check the following:
| Platform | Agent version |
|---|---|
| Java | Java Agent 2.1.0 or later |
| PHP | PHP Agent 2.3.2 or later |
| Python | Python Agent 1.2.2 or later |
| Server | Server Agent 2.1.2 or later |
Browser Monitoring
The data that WhaTap browser agent can collect may differ depending on the browser and its version.
| Collected data | Chrome | Edge | Safari | Firefox | Opera | Chrome Android | Safari iOS | Samsung Internet |
|---|---|---|---|---|---|---|---|---|
| Page Load | > 6 | > 12 | > 8 | > 7 | > 15 | 107 | > 9 | > 4 |
| Resources for page load | > 28 | > 12 | > 11 | > 35 | > 15 | 107 | > 11 | > 4 |
| Resources | > 52 | > 79 | > 11 | > 57 | > 39 | 107 | > 11 | > 6.2 |
| AJAX | > 4 | > 12 | > 3.1 | > 2 | > 10 | 107 | > 3.2 | > 4 |
| Core Web Vitals | > 77 | > 79 | fid only | fid only | > 64 | 107 | fid only | > 12 |
| Switching to the SPA page | > 4 | > 12 | > 3.1 | > 2 | > 10 | 107 | > 3.2 | > 4 |
| console error | > 4 | > 12 | > 3.1 | > 4 | > 11.5 | 107 | > 3.2 | > 4 |
| Exception unhandled promise error | > 49 | > 79 | > 11 | > 69 | > 36 | 107 | > 11.3 | > 5 |
| Exception unhandled Java script error | > 10 | > 12 | > 5.1 | > 6 | > 15 | 107 | > 5 | > 4 |
| Session Replay | > 47 | > 79 | > 8 * | > 6 | > 55 | > 47 | > 9 * | > 5 |
To avoid overheads during session replay data collection, data is collected in idle time of the main thread. For this purpose, use the requestIdleCallback API.
The requestIdleCallback API is designed to perform a callback when the browser is idle, making sure that it does not interfere with the main tasks while collecting the session replay data. For more information, see the following link.
Safari and Safari iOS do not support the requestIdleCallback API, so session replay data is not collected by default. Setting the sessionReplayCollectAllBrowser option to true enables session replay data collection on these browsers. However, in this case, data is collected without checking main thread idle time, which may impact performance. For more details on applying this option, refer to this link.
Extension Tool
Telegraf
| OS | Supported version |
|---|---|
| Linux | Red Hat 6.x x64 or later |
| Ubuntu 12.x x64 or later | |
| Unix | FreeBSD 10.x x64 or later |
| Telegraf | Telegraf 1.3 or later |
For Telegraf, the version that supports the socket_writer output plugin is allowed.
Focus
| OS | Supported version |
|---|---|
| Windows | Windows 2008R2 or later |
| Linux | Debian 7.0 or later |
| Ubuntu 12.04 or later | |
| CentOS, Red Hat 6.0 or later | |
| Amazon Linux 1.0 or later | |
| SUSE 12.1 or later | |
| Unix | FreeBSD 10 or later |
| OSX | Lion 10.7 or later |
| Raspberry Pi OS | 8 or later |
Supported browsers
WhaTap Monitoring is available in web browsers and mobile Apps.
| Browser | Recommended | Supported version |
|---|---|---|
| Google Chrome | ✅ | 111 or later |
| Mozilla FireFox | ❌ | Latest version |
| Edge | ❌ | Latest version |
| Safari | ❌ | Latest version |
Support guidance
- For browser compatibility and performance reasons, the latest version of Chrome is recommended.
- The user interface (UI) is implemented using HTML5 standard technologies, so Internet Explorer is not supported.
Limitations
WhaTap’s web interface does not support mobile browsers. To access WhaTap on a mobile device, install the WhaTap app for Android or iOS. The WhaTap mobile app is optimized for mobile environments. For more information about the WhaTap mobile app, see this document.
Firewall
The WhaTap agent must be able to access the collection server through TCP port 6600. Allow access to the collection server address that is closest to the monitored target.
Source: WhaTap agent
| Cloud | Destination | Destination IP | Port |
|---|---|---|---|
| AWS | WhaTap collection server (Seoul) | 13.124.11.223 / 13.209.172.35 | TCP 6600 |
| WhaTap collection server (Tokyo) | 52.68.36.166 / 52.193.60.176 | TCP 6600 | |
| WhaTap collection server (Singapore) | 18.138.0.93 / 18.139.67.236 | TCP 6600 | |
| WhaTap collection server (Jakarta) | 108.136.91.69 / 108.137.158.44 | TCP 6600 | |
| WhaTap collection server (Thailand) | 43.209.109.219 / 43.209.48.86 | TCP 6600 | |
| WhaTap collection server (Mumbai) | 13.127.125.69 / 13.235.15.118 | TCP 6600 | |
| WhaTap collection server (California) | 52.8.223.130 / 52.8.239.99 | TCP 6600 | |
| WhaTap collection server (Virginia) | 107.23.220.101 / 54.236.221.105 | TCP 6600 | |
| WhaTap collection server (Frankfurt) | 3.125.142.162 / 3.127.76.140 | TCP 6600 | |
| Azure | WhaTap collection server (Seoul) | 52.231.66.38 / 20.194.5.115 | TCP 6600 |
| WhaTap collection server (Tokyo) | 52.246.169.54 / 20.210.27.232 | TCP 6600 | |
| Kakao | WhaTap collection server (Seoul) | 61.109.237.237 / 61.109.238.166 | TCP 6600 |
If the agent cannot directly access the collection server, use the provided proxy module to access it.
Mobile app
The WhaTap mobile app supports both Android and iOS environments. You can install the WhaTap app by following the link or scanning the QR code. For detailed information about the mobile app, see the following.
| iOS | Android |
|---|---|
 iOS 12 or later |  Android 5.0 or later |
-
The mobile app supports the service.whatap.io service. The installed type service is unavailable.
-
Available product types are as follows. We will expand the scope of support through future updates.
- Application: Java, PHP, Python, Node.js, Go, .NET
- Server
- Database
- Kubernetes
- URL
- Browser
-
The mobile app does not support the project grouping feature.
Alert support environment
You can see the supported event types for each monitoring platform regarding alerts.
| Function | Receive upon event occurrence | Recurring alert (escalation) | Acknowledge (Acknowledge) | Event pause (Silent) | Additional notifications when the event state is resolved. (Recovered) |
|---|---|---|---|---|---|
| Metrics | ✅ | ✅ (1) | ✅ (2) | ✅ | ✅ |
| Log | ✅ | ❌ | ❌ | ✅ | ❌ |
| Anomaly Detection | ✅ | ❌ | ❌ | ❌ | ❌ |
| AI-powered hitmap pattern alerts | ✅ | ❌ | ❌ | ✅ | ❌ |
| Inactive Agent Alert | ✅ | ❌ | ❌ | ❌ | ✅ |
| Application | ✅ | ✅ | ❌ | ✅ | ✅ |
| Server | ✅ | ✅ | ✅ (2) | ❌ | ✅ |
| Server Process | ✅ | ✅ | ✅ (2) | ❌ | ✅ |
| Server log keyword | ✅ | ❌ | ❌ | ❌ | ❌ |
| DATABASE | ✅ | ✅ | ❌ | ✅ | ❌ |
| Container | ✅ | ✅ | ❌ | ✅ | ✅ |
| URL | ✅ | ❌ | ❌ | ❌ | ❌ |
-
The Recurring alert (escalation) function targets all events for Critical (or Fatal class). See the Level item set for adding an event.
-
(1): The repetitive notification of the metric works only when the Additional notifications when the event state is resolved. function is active.
-
(2): The Acknowledge function is available only for server projects. When you enter the processing details, the Recurring alert (escalation) function is paused.
If it is not included in the support environment, please contact us at support@whatap.io.