OCI Cost And Usage Snapshot Analyzer

 


Description

I built the OCI Cost And Usage Snapshot Analyzer as a lightweight Python automation tool that captures a point in time snapshot of what is currently running in an OCI compartment. Instead of pulling billing data, it focuses on resource usage metadata by collecting Compute instances and Block Volumes, then generating timestamped JSON and Markdown reports that can be uploaded to OCI Object Storage for easy auditing and sharing. 


Codebase

GitHub Code: Click Here


Why This Is Useful

In many OCI environments, teams want a quick and repeatable way to answer: What resources exist right now in this compartment, what state are they in and how does the footprint change over time? A consistent snapshot is useful for operational reviews, governance checks and simple “before and after” comparisons when changes are made. This tool makes that easy by producing both a human readable Markdown report and a machine friendly JSON output in every run.


What The Tool Does

The tool performs a read-only inventory of two core resource types in a target compartment:

  • Compute instances: display name, lifecycle state, shape, OCID, availability domain

  • Block volumes: display name, size in GB, lifecycle state, OCID, availability domain

After collection, it writes:

  • A JSON snapshot (for diffing, automation, and extensions)

  • A Markdown snapshot (a simple table for quick review)

Finally, it uploads both artifacts to OCI Object Storage under a configurable prefix.


High Level Architecture

At a high level, the workflow is:

  1. Load environment variables and OCI SDK config from the default OCI config file.

  2. Collect compute and block volume inventory for a single compartment.

  3. Generate a UTC timestamp and write reports to a local reports/ folder.

  4. Upload the JSON and Markdown artifacts into Object Storage using the bucket name and prefix you provide.



Prerequisites

You will need:

  • Python 3.x

  • Dependencies: oci and python-dotenv

  • OCI credentials configured (standard OCI config file)

  • IAM permissions to list instances, list volumes and upload objects to your chosen Object Storage bucket (the bucket must already exist). 


Expected Output

Each run generates two timestamped files in reports/:

  • cost_snapshot_<timestamp>_UTC.json

  • cost_snapshot_<timestamp>_UTC.md

It then uploads those two objects to Object Storage under:
<OCI_OBJECT_PREFIX>/cost_snapshot_<timestamp>_UTC.*


Safety Notes

This tool is designed to be safe to run in production because it performs read only resource discovery (Compute and Block Volume listing). The only write activity is uploading the generated report files to Object Storage.



Comments

Post a Comment

Popular posts from this blog

Your Cloud Is Talking Are You Listening OCI Logging Events and Notifications

Image
  Your Cloud Is Talking Are You Listening OCI Logging Events and Notifications A practical, human guide to how Oracle Cloud Infrastructure can collect what is happening, spot what matters and alert the right people before small issues turn into big ones. The problem with modern cloud is not lack of data Cloud platforms produce a huge amount of signals. Logs, metrics, state changes, access activity and service health updates are happening all the time. The problem is not that nothing is visible. The problem is that everything is visible in too many places and when something goes wrong, you do not know where to look first. This is why good teams still get surprised. Not because they are careless, but because attention is limited. You can only watch so many dashboards. You can only skim so many notifications. And when an incident starts, the first five minutes matter most. The goal of observability is simple. Make it easier to answer three questions quickly. What happened. Where ...
Read more

OCI Network Exposure Scanner

Image
OCI Network Exposure Scanner Introduction Of A Python Tool That Scans OCI Security Lists And NSGs For Internet Exposed Ingress Rules And Risky Open Ports Description I built the OCI Network Exposure Scanner as a lightweight Python auditing tool to quickly identify internet exposed ingress rules in OCI. It scans Security Lists and Network Security Groups (NSGs) for inbound TCP rules that allow traffic from 0.0.0.0/0 on common ports like SSH (22), RDP (3389), HTTP (80), and HTTPS (443) , then generates timestamped JSON + Markdown reports and uploads them to OCI Object Storage so the results are easy to review, share, and keep as audit evidence.  Codebase GitHub Code: Click Here Why This Is Useful In most OCI environments, network rules evolve quickly as teams ship features, open temporary access for troubleshooting or create new subnets and services. Over time, it becomes easy to accidentally leave behind world open ingress rules , especially on ports like SSH and RDP. This ...
Read more

When Your Apps Refuse to Talk Oracle Integration Cloud for the Rest of Us

Image
  When Your Apps Refuse to Talk Oracle Integration Cloud for the Rest of Us Oracle Integration Cloud is the Grown Up Way to Make Those Systems Cooperate. The quiet chaos of modern work Most companies do not run on one system. They run on a collection of tools that grew over time. Finance has one platform, sales has another, HR has its own portal and operations lives inside a mix of email, shared drives and service tickets. On paper, everything is digital. In reality, people still spend their days doing digital manual work. They export a spreadsheet, paste values into another system, forward approvals through email and hope everyone is looking at the latest version. It works until it does not. Then someone asks why the customer record is inconsistent, why invoices are delayed or why a new employee is not provisioned correctly. This is exactly the kind of problem Oracle Integration Cloud is meant to reduce. Oracle positions it as an integration service that helps connect applicati...
Read more