Servers hosted here

Linking a server

On the server's Settings tab, choose a project under Monitoring and press Link, or add the server on the project's Settings tab. Then restart the server. The panel makes a key just for that server, which does not count towards your keys, and puts it in the environment as SILLYDEV_MONITORING_KEY, with SILLYDEV_MONITORING_SERVICE set to server- and the server's identifier, and SILLYDEV_MONITORING_ENVIRONMENT set to sillydev.

So monitoring.init() with no arguments is all your code needs. Unlinking removes the key on the next restart.

Container metrics

A linked server's CPU, memory, memory limit and network, measured from outside the container every minute, show in the project as container.* metrics, with its crashes and out-of-memory kills as events. They count towards the project's series limit like any other metric, a few series for each linked server.

Server history

Every server, linked or not, has a History section on its console page: CPU, memory against its limit, and network, for the last hour to the last 30 days, with crashes and out-of-memory kills marked. It needs no project and no code.