Linode#
Collects instance metrics, managed database metrics, NodeBalancer statistics and object storage usage using a Linode API token.
Create a read-only token#
- Sign in to the Linode Cloud Manager.
- Open My Profile → API Tokens → Create a Personal Access Token.
- Label it
observeiq-readonlyand set an expiry. - Grant Read Only on: Linodes, Databases, NodeBalancers, Object Storage, Volumes, Domains and Account. Leave everything else as None.
- Create the token and copy it. It is shown once.
Do not grant Read/Write. ObserveIQ only reads, and a read-write token in a third-party system is an unnecessary risk.
Add the integration#
Integrations → Linode → Add account, paste the token, save. The credentials are validated immediately.
What is collected#
| Resource | Metrics |
|---|---|
| Linode instances | CPU, memory, disk IO, network in and out, transfer quota used |
| Managed databases | Connections, CPU, memory, disk usage, replication state |
| NodeBalancers | Connections, throughput, backend health status |
| Object Storage | Bucket size, object count, transfer |
| Volumes | Size, attachment state |
Kubernetes on Linode#
LKE clusters appear as instances, which gives you node-level metrics. For pod and workload detail, also install the Kubernetes agent into the cluster. The two complement each other: the integration sees the infrastructure, the agent sees what runs on it.
Transfer quota#
Linode bills for network transfer above a monthly pool. The integration collects transfer used against the pool, which is worth alerting on before the month ends rather than discovering on the invoice.
Verify#
Open Cloud → Explorer and filter to Linode. Instances appear within one collection interval. If the list is empty, the token most likely lacks the Linodes read scope, or has expired.