Better Stack Oracle Cloud integration

This Terraform stack sends metrics and logs from an Oracle Cloud Infrastructure tenancy to Better Stack.

How it works

The stack runs in OCI Resource Manager inside your tenancy. Connector Hub reads metrics from OCI Monitoring and logs from OCI Logging. It sends them in batches to a forwarder Function. The Function compresses each batch and sends it to Better Stack over HTTPS.

Better Stack never connects to your tenancy. Data leaves your tenancy only through the Function. The only secret that the stack keeps in your tenancy is the Better Stack source token, in the configuration of the Function.

Quick start

Before you start, sign in to the home region of your tenancy. Use a user who can create compartments and policies in the root compartment, and read service limits (inspect limits in tenancy). Administrators can do both.

1. Create an Oracle Cloud source in Better Stack.
2. On the Ingest tab of the source, click Deploy to Oracle Cloud.
3. Accept the Oracle Terms of Use and click Next.
4. The Ingesting host and Source token are already filled in. Click Next.
5. Make sure that Run apply is selected, then click Create.

The stack creates a compartment with the name betterstack. If your tenancy already has a compartment with this name, remove or rename it first.

The stack sends metrics and logs from the home region only.

What the stack creates

• A betterstack compartment for all the resources below.
• A Function application for the forwarder. It runs in a VCN with a private subnet. A NAT gateway lets the Function reach Better Stack.
• One Connector Hub for logs, and one or more Connector Hubs for metrics. Each Connector Hub takes up to 5 compartments and 50 metric namespaces, so it covers 2 compartments with the 25 default namespaces, and 5 with 10 or fewer. If your region's Connector Hub limit is too low, Plan stops before anything changes, but it doesn't count Connector Hubs you already use elsewhere in the region. Deselect namespaces, list the compartments to forward metrics from, or request a limit increase.
• A policy that lets the Connector Hubs read metrics and logs, and call the Function.

Every selected namespace is forwarded from each compartment: the ones you list, or every compartment that exists when you apply. Services you start using later are forwarded without running Apply again. After you add compartments, apply the stack again.

Upgrade

1. Go to Developer Services → Resource Manager → Stacks and select the Better Stack stack.
2. Click Edit, upload betterstack-oci.zip from the latest release, and save.
3. Click Apply.

Since v0.1.3, each compartment takes a place on a Connector Hub, even when it has no metrics yet. An upgrade from v0.1.2 can need more Connector Hubs than before. For example, the root compartment and 2 empty subcompartments need 3 on a limit of 2. If Plan stops, deselect namespaces to 10 or fewer, list the compartments to forward metrics from, or request a limit increase.

Uninstall

1. Go to Developer Services → Resource Manager → Stacks and select the Better Stack stack.
2. Click Destroy.

This takes about 15 minutes. Most of this time goes to removing the betterstack compartment.

License

MIT