Monitoring your services
See traffic, logs and resource use without adding another tool.
Analytics
Analytics, in the sidebar's Observability menu, measures your sites from the web server's own logs, so there's no script to add. You get visitors, pages, referrersThe sites visitors came from, like a search engine or a link on social media., countries, devices and browsers.
Visitors are counted with a hashA one-way code made from the visitor's IP address, browser and your site, mixed with a value that changes daily. It tells visits apart but can't be traced back to anyone. that changes daily. Visitor IP addresses aren't kept by default. An admin can change what's kept under SettingsObservability.
Connections
A service with public TCP or UDP ports has a Connections card on its Overview, for the ports that go through Pyo Gateway. It shows connections, clients and data over time. Each connection shows its country, bytes, duration and outcome: ok, blocked, limited or unreachable. Blocked means the firewall or a port's IP rule stopped it.
A TCP connection is counted when it closes. A UDP exchange is counted once it's been quiet for a minute, and its duration includes that minute. Ports that skip the gateway aren't counted.
Logs
Logs, in the sidebar's Observability menu, shows the web server's log of every request your sites served: the time, method, URL, status, response time and size, with the visitor's browser and country. Search and filter them to find a request. Sensitive values in query strings are hidden. Logs are kept for 180 days.
These are request logs, not your service's own output. For that, open its logs in the dashboard or use the CLI:
pyo logs --followMetrics
See CPU and memory for each server and service, and for Pyo Gateway, which handles all web traffic into each cluster. The gateway has no limit of its own, so its use is shown against the cluster's total capacity.
Turning it on or off
Analytics, Logs, connections, firewall and WAF history and metrics over time all need Pyo's observability, which stores what each cluster's servers send. It's on unless a new install's server has less than 3.5 GB of memory. There it starts off to save memory.
An admin turns it on or off under SettingsObservability, or with the CLI:
pyo observability offWhile it's off:
- Pyo stops collecting and frees the memory it used, about 150 MB on the server Pyo runs on and a little on each server.
- Analytics, Logs and the charts over time say it's off.
- What was stored is kept. Turn it back on to see it again, with a gap for the time it was off.
- Everything else keeps working: your services' own logs, current CPU and memory, deploys, the firewall and the WAF.
Pyo never turns it on or off by itself after the install. If the server's memory changes, SettingsObservability suggests turning it on or off.
Terminal
Open a shellA command line inside the running service, where you can type commands as you would on a server. in any running service from the dashboard, or from your terminal:
pyo execActivity
Activity, in the same menu, records who deployed or changed what, and when.