Skip to main content

Support environment

Go agent support environment

Before installing the WhaTap Go monitoring agent, check the support environment.

Info

Last updated: 2026-01-26

Supported versions

LanguageSupported version
Go1.18 or later

Operating system

OSMinimum versionArchitecture
CentOS / Red Hat6.x64bit
Debian / Ubuntu12.0464bit
Amazon Linux-64bit
Alpine Linux-64bit
Linux-ARM64 (aarch64)

Library

CategoryLibrary
Web frameworknet/http, gin, chi, fiber, gorilla, echo, fasthttp
Databasedatabase/sql, gorm, redigo
Othersgrpc, sarama, k8s.io/client-go
Note

For framework or library application methods and examples, see the GitHub site.

Go monitoring data flow diagram

Go Monitoring

Communication structure

AgentOperation method
InboundRun as 127.0.0.1:6600 TCP server / Application → Agent (TCP 6600)
OutboundSend received data to WhaTap collection server / Agent → WhaTap server (Outbound 6600)
Note

Go applications only communicate with the local agent, and the agent is responsible for external transmission.

Common support environment

Browser support

WhaTap Monitoring is available in web browsers and mobile Apps.

BrowserRecommendedSupported version
Google Chrome84 or later
Mozilla FireFoxLatest version
EdgeLatest version
SafariLatest version
Note

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.
Caution

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

CloudDestinationDestination IPPort
AWSWhaTap collection server (Seoul)13.124.11.223 / 13.209.172.35TCP 6600
WhaTap collection server (Tokyo)52.68.36.166 / 52.193.60.176TCP 6600
WhaTap collection server (Singapore)18.138.0.93 / 18.139.67.236TCP 6600
WhaTap Jakarta collection server108.136.91.69 / 108.137.158.44TCP 6600
WhaTap collection server (Mumbai)13.127.125.69 / 13.235.15.118TCP 6600
WhaTap collection server (California)52.8.223.130 / 52.8.239.99TCP 6600
WhaTap Virginia collection server107.23.220.101 / 54.236.221.105TCP 6600
WhaTap collection server (Frankfurt)3.125.142.162 / 3.127.76.140TCP 6600
AzureWhaTap collection server (Seoul)52.231.66.38 / 20.194.5.115TCP 6600
WhaTap collection server (Tokyo)52.246.169.54 / 20.210.27.232TCP 6600
KakaoWhaTap collection server (Seoul)61.109.237.237 / 61.109.238.166TCP 6600

If the agent cannot directly access the collection server, use the provided proxy module to access it.

Proxy

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.

iOSAndroid
QR
iOS 12 or later
QR
Android 5.0 or later