Appearance
Network & ports
From your servers (agent)
| Destination | Port | Purpose |
|---|---|---|
logcore.lsofito.com | 443/tcp (HTTPS) | Install script and binary download, logs, metrics, heartbeats, APM forwarding |
That's the only connection the agent needs. You don't need to open any inbound port on monitored servers.
On the server itself (local only)
| Address | Purpose | Default |
|---|---|---|
127.0.0.1:5280 | Status API for logcore-agent status | on (status_addr) |
127.0.0.1:4317 | OTLP/gRPC from local apps | off until apm.enabled |
127.0.0.1:4318 | OTLP/HTTP from local apps | off until apm.enabled |
From your apps (direct APM)
| Destination | Port | Protocol |
|---|---|---|
logcore.lsofito.com | 443 | OTLP/HTTP (recommended) |
logcore.lsofito.com | 4318 | OTLP/HTTP |
logcore.lsofito.com | 4317 | OTLP/gRPC (TLS) |
API endpoints used by the agent
These are for reference only, for example if you need to allow them in a proxy:
| Path | Purpose |
|---|---|
/install.sh, /install.ps1 | Installers |
/downloads/logcore-agent-* | Agent binaries and .sha256 checksums |
/api/v1/intake/* | Logs, metrics and heartbeats (API key in a header) |
/v1/traces, /v1/metrics, /v1/logs | OTLP/HTTP |
Proxies
The agent honours the standard HTTPS_PROXY, HTTP_PROXY and NO_PROXY environment variables. On Linux, set them with sudo systemctl edit logcore-agent:
ini
[Service]
Environment=HTTPS_PROXY=http://proxy.internal:3128On Windows, set them as machine-wide environment variables, then restart the service.