Modeling Your Infrastructure as Entities

Why entities matter

Entities are the backbone of TG2G. They represent the things you care about: services, workloads, clusters, and critical third-party systems. Good entity modeling makes incidents easier to understand and billing more predictable.

Common modeling patterns

• One entity per externally-visible service (e.g. `api-gateway`, `checkout-api`).
• Separate entities for critical infrastructure components (e.g. `k8s-prod-cluster`).
• Entities for business-critical SaaS dependencies (e.g. payment providers).