Last9 IOX exchange

Preface

<aside> 💡 What Terraform is to Cloud operations, IOX is to metrics.

</aside>

The thesis is, every component's observability has two parts to it:

• A "domain model" definition of it. What is the physical location, and what all Logical members can it serve.
• Observability data for all physical and logical members involved in this cycle.

Sometimes this data is available in multiple sources. For example, an Instance has both CPU and memory metrics. Data concerning CPU health is available in Cloudwatch. Inside the machine, metrics like memory are available in custom metrics via Custom Metrics in Cloudwatch or any other monitoring.

<aside> 💡 IOX makes this monitoring declarative.

</aside>

The syntax is very much Terraform-inspired (not copied :)), in fact, it uses the same HCL configuration syntax. And there are some JSONs for variable overrides.

Pictorial Thesis

Current-ways-of-Observing-an-Instance

With-IOX

A sample structure

Here's how we onboard a simple Load Balancer—one where we search via Tags and another where we provide ARNs as a file input.

Follow the Steps on this document to initialize a repository that is IOX powered.