{"id":966,"date":"2026-04-17T07:39:57","date_gmt":"2026-04-17T07:39:57","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-resource-analytics-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-observability-and-management\/"},"modified":"2026-04-17T07:39:57","modified_gmt":"2026-04-17T07:39:57","slug":"oracle-cloud-resource-analytics-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-observability-and-management","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-resource-analytics-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-observability-and-management\/","title":{"rendered":"Oracle Cloud Resource Analytics Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Observability and Management"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Observability and Management<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What this service is<\/h3>\n\n\n\n<p><strong>Resource Analytics<\/strong> in <strong>Oracle Cloud (OCI)<\/strong> is the analytics experience used to understand how your infrastructure resources are behaving over time\u2014especially utilization and capacity signals that answer questions like \u201cAre we sized correctly?\u201d and \u201cWhere are we wasting spend or risking saturation?\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Simple explanation (one paragraph)<\/h3>\n\n\n\n<p>If you run workloads on Oracle Cloud (and often also across hybrid environments), Resource Analytics helps you look beyond point-in-time metrics and instead analyze trends\u2014so you can spot underutilized resources, capacity risks, and growth patterns before they become incidents or unnecessary costs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Technical explanation (one paragraph)<\/h3>\n\n\n\n<p>In OCI, Resource Analytics is commonly surfaced as part of OCI\u2019s <strong>Observability and Management<\/strong> portfolio\u2014most often associated with <strong>Operations Insights<\/strong>-style workflows (for example, analyzing host and database resource usage trends). It relies on telemetry collected from your environments (OCI Compute and, depending on setup, other hosts\/databases), then provides filtering, aggregation, and drill-down analysis to support capacity planning and operational decision-making. <strong>Verify the exact product placement and current console navigation in official docs<\/strong>, because Oracle updates naming and navigation periodically.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What problem it solves<\/h3>\n\n\n\n<p>Resource Analytics helps solve:\n&#8211; <strong>Capacity planning<\/strong>: knowing when CPU, memory, or storage will become a bottleneck.\n&#8211; <strong>Rightsizing<\/strong>: identifying overprovisioned resources (cost waste) and underprovisioned resources (performance risk).\n&#8211; <strong>Operational visibility<\/strong>: giving engineering and operations teams a consistent view of utilization trends across fleets, compartments, and environments.\n&#8211; <strong>Decision support<\/strong>: providing data-driven evidence for scaling, migration, and architecture changes.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Resource Analytics?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p>In Oracle Cloud\u2019s <strong>Observability and Management<\/strong> context, <strong>Resource Analytics<\/strong> is intended to help you <strong>analyze resource utilization and capacity trends<\/strong> so you can plan, optimize, and operate cloud resources more effectively.<\/p>\n\n\n\n<p>Because Oracle documentation and console experiences can evolve, treat the following as the practical, commonly implemented scope:\n&#8211; Resource Analytics is typically a <strong>console-driven analytics capability<\/strong> built on top of collected resource telemetry.\n&#8211; It is often encountered alongside (or within) <strong>Operations Insights<\/strong> capabilities that focus on utilization and capacity planning.<br\/>\n<strong>Verify in official docs<\/strong> whether Oracle currently presents Resource Analytics as a standalone service entry, a sub-feature, or a set of pages under another service.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities<\/h3>\n\n\n\n<p>Resource Analytics commonly focuses on:\n&#8211; <strong>Trend analysis<\/strong> (not just real-time monitoring)\n&#8211; <strong>Fleet-level views<\/strong> across groups of resources\n&#8211; <strong>Filtering and segmentation<\/strong> (for example by compartment, tags, or resource type\u2014availability depends on your setup)\n&#8211; <strong>Drill-down<\/strong> from aggregated views into individual resources\n&#8211; <strong>Operational reporting<\/strong> for capacity and utilization<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (conceptual)<\/h3>\n\n\n\n<p>Depending on your exact OCI configuration, Resource Analytics usually involves:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Component<\/th>\n<th>What it does<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Data sources (OCI resources)<\/td>\n<td>Produce raw utilization signals (CPU, memory, storage, etc.)<\/td>\n<td>Signals can come from native OCI telemetry and\/or agents<\/td>\n<\/tr>\n<tr>\n<td>Data collection mechanism<\/td>\n<td>Collects\/ships telemetry for analysis<\/td>\n<td>Often involves agents for non-native targets; verify supported methods<\/td>\n<\/tr>\n<tr>\n<td>Analytics layer \/ dashboards<\/td>\n<td>Aggregates, trends, and visualizes utilization<\/td>\n<td>This is what users typically call \u201cResource Analytics\u201d<\/td>\n<\/tr>\n<tr>\n<td>IAM \/ Policies<\/td>\n<td>Controls who can view or administer analytics<\/td>\n<td>OCI IAM policies determine access<\/td>\n<\/tr>\n<tr>\n<td>Audit and governance<\/td>\n<td>Records relevant API\/console actions<\/td>\n<td>OCI Audit is commonly used for governance<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<p>Resource Analytics is best understood as a <strong>managed analytics capability<\/strong> within OCI\u2019s Observability and Management ecosystem. It is not \u201cjust charts\u201d; it is designed for <strong>planning and optimization<\/strong> using historical and trend-based views.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scope: regional vs global<\/h3>\n\n\n\n<p>OCI observability services are typically <strong>regional<\/strong> (you select a region in the OCI Console). Resource Analytics generally follows that model:\n&#8211; You view and operate Resource Analytics <strong>in a specific region<\/strong>\n&#8211; Data residency and visibility may be region-scoped\n&#8211; Cross-region aggregation may require separate setup or external tooling<br\/>\n<strong>Verify region\/tenancy scoping in the official Resource Analytics \/ Operations Insights docs for your OCI tenancy.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Oracle Cloud ecosystem<\/h3>\n\n\n\n<p>Resource Analytics complements:\n&#8211; <strong>Monitoring<\/strong>: for real-time metrics, alarms, and operational alerting\n&#8211; <strong>Logging \/ Logging Analytics<\/strong>: for log search, parsing, and log-derived insights\n&#8211; <strong>APM<\/strong>: for application-level tracing and performance\n&#8211; <strong>Operations Insights<\/strong> (commonly adjacent): for capacity planning, performance trends, and utilization analysis across hosts and databases<br\/>\nIn many organizations, Resource Analytics becomes the \u201ccapacity planning lens\u201d while Monitoring is the \u201creal-time alerting lens.\u201d<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Resource Analytics?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reduce cloud waste<\/strong> by identifying idle\/overprovisioned resources.<\/li>\n<li><strong>Avoid outages<\/strong> by detecting utilization trajectories that predict saturation.<\/li>\n<li><strong>Improve forecasting<\/strong> for budgeting and procurement planning.<\/li>\n<li><strong>Support FinOps<\/strong> by providing utilization evidence for rightsizing decisions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Trend-based analysis<\/strong> for CPU\/memory\/storage vs. relying on point-in-time metrics.<\/li>\n<li><strong>Fleet perspectives<\/strong>: see patterns across many resources rather than one-by-one inspection.<\/li>\n<li><strong>Data-driven scaling<\/strong>: choose vertical\/horizontal scaling based on historical evidence.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Helps SRE\/Operations teams answer:<\/li>\n<li>\u201cWhich hosts are trending toward CPU exhaustion?\u201d<\/li>\n<li>\u201cWhich environments are overallocated?\u201d<\/li>\n<li>\u201cWhat changed after a release window?\u201d<\/li>\n<li>Supports <strong>runbook improvements<\/strong> and proactive maintenance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security \/ compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Better governance when teams can <strong>prove<\/strong> resources are sized appropriately and monitored.<\/li>\n<li>When paired with OCI IAM and Audit, you can enforce:<\/li>\n<li>separation of duties<\/li>\n<li>least privilege access to analytics views<\/li>\n<li>traceability of administrative actions<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability \/ performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prevents \u201csilent\u201d performance degradation caused by sustained high utilization.<\/li>\n<li>Enables planning for growth (seasonality, campaigns, end-of-quarter spikes).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<p>Choose Resource Analytics when you need:\n&#8211; Capacity planning and rightsizing based on historical utilization\n&#8211; A standardized utilization analytics workflow for OCI resources\n&#8211; A complement to Monitoring that focuses on <strong>optimization and planning<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Resource Analytics may not be the best fit when:\n&#8211; You only need <strong>basic real-time metrics and alarms<\/strong> (Monitoring may be sufficient)\n&#8211; You need deep <strong>application tracing<\/strong> (APM is the correct tool)\n&#8211; You need complex cross-cloud analytics and custom KPIs (you may prefer a centralized observability data lake and BI tooling)\n&#8211; You cannot deploy required collectors\/agents for your environment (if applicable)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Resource Analytics used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SaaS and technology platforms (capacity planning for multi-tenant systems)<\/li>\n<li>Financial services (predictable performance and compliance reporting)<\/li>\n<li>Healthcare (availability and performance planning for regulated systems)<\/li>\n<li>Retail\/e-commerce (seasonality and event-driven scaling)<\/li>\n<li>Media and gaming (spiky demand and performance-sensitive infrastructure)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud platform teams (standardization and governance)<\/li>\n<li>SRE and operations teams (proactive capacity planning)<\/li>\n<li>DevOps teams (release impact analysis and scaling validation)<\/li>\n<li>FinOps teams (rightsizing and spend optimization)<\/li>\n<li>Security teams (operational governance and audit readiness)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Compute fleets (web tiers, batch workers, CI runners)<\/li>\n<li>Stateful workloads (databases, caching layers) \u2014 scope depends on what telemetry you onboard<\/li>\n<li>Hybrid workloads (OCI + on-prem) \u2014 if supported by your telemetry collection approach<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Single-region apps needing capacity forecasting<\/li>\n<li>Multi-environment setups (dev\/test\/prod) with compartment segmentation<\/li>\n<li>Hub-and-spoke network models where teams manage separate compartments<\/li>\n<li>Shared services platforms where central Ops monitors many app teams<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: proactive planning, monthly capacity reviews, incident prevention<\/li>\n<li><strong>Dev\/test<\/strong>: identify underutilization, shut down or downsize, validate performance baselines after changes<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios for <strong>Resource Analytics<\/strong> in Oracle Cloud.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Rightsizing compute instances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Instances run at &lt;10% CPU most days but remain expensive.<\/li>\n<li><strong>Why Resource Analytics fits<\/strong>: Trend views show sustained low utilization and variability.<\/li>\n<li><strong>Example<\/strong>: A dev fleet of 80 instances shows &lt;5% CPU after business hours; downsize shapes or schedule stop\/start.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Forecasting CPU saturation for a service tier<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: CPU steadily increases week over week; risk of latency spikes.<\/li>\n<li><strong>Why it fits<\/strong>: Trend analysis supports growth projections and planning.<\/li>\n<li><strong>Example<\/strong>: API tier average CPU climbs from 35% to 65% over 6 weeks; scale out before next release.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Detecting memory pressure trends<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Frequent OOM events but unclear whether it\u2019s transient or sustained.<\/li>\n<li><strong>Why it fits<\/strong>: Historical memory trends reveal whether memory pressure is chronic.<\/li>\n<li><strong>Example<\/strong>: Batch workers show sustained 90% memory during nightly jobs; increase memory shape or optimize workload.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Identifying noisy neighbors or uneven fleet load<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Some hosts are hot while others are idle.<\/li>\n<li><strong>Why it fits<\/strong>: Fleet-level analytics highlight distribution and outliers.<\/li>\n<li><strong>Example<\/strong>: 10% of hosts consume 70% of CPU; rebalance workloads or adjust autoscaling policies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Validating post-migration performance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: After moving to OCI, performance is \u201cokay\u201d but not measured.<\/li>\n<li><strong>Why it fits<\/strong>: Before\/after comparisons using consistent metrics.<\/li>\n<li><strong>Example<\/strong>: Compare 30-day utilization trends pre- and post-migration to validate sizing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Capacity planning for seasonal spikes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: End-of-quarter spikes cause resource contention.<\/li>\n<li><strong>Why it fits<\/strong>: Trend + seasonality patterns inform reserved capacity planning.<\/li>\n<li><strong>Example<\/strong>: Retail traffic peaks monthly; plan shape changes or scaling rules ahead of peak windows.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Budget-driven optimization (FinOps)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Cloud bill rising; need evidence-based cuts.<\/li>\n<li><strong>Why it fits<\/strong>: Utilization evidence supports rightsizing without risking SLOs.<\/li>\n<li><strong>Example<\/strong>: Identify persistent underutilized instances in non-prod and enforce resizing policy.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Incident prevention through trend thresholds<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Alerts fire only when resources are already maxed.<\/li>\n<li><strong>Why it fits<\/strong>: Trend-based review finds \u201capproaching saturation\u201d resources.<\/li>\n<li><strong>Example<\/strong>: Weekly review flags resources with upward CPU trend; fix before incidents.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Executive reporting and KPI tracking<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Leadership asks, \u201cAre we using what we pay for?\u201d<\/li>\n<li><strong>Why it fits<\/strong>: Aggregated analytics can support utilization KPIs and reports.<\/li>\n<li><strong>Example<\/strong>: Monthly report: percent of fleet within target utilization band.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Environment hygiene (dev\/test)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Dev\/test resources left running idle.<\/li>\n<li><strong>Why it fits<\/strong>: Trend analytics expose idle periods.<\/li>\n<li><strong>Example<\/strong>: Identify instances idle for 14 days; automatically terminate or stop.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Planning storage growth<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Storage usage is creeping up; uncertain runway.<\/li>\n<li><strong>Why it fits<\/strong>: Growth curves help plan expansions and cleanup.<\/li>\n<li><strong>Example<\/strong>: Log volume growth predicts full capacity in 45 days; implement retention and archive.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Consolidation and platform standardization<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Too many custom shapes and inconsistent provisioning.<\/li>\n<li><strong>Why it fits<\/strong>: Shows utilization by shape\/class to guide standards.<\/li>\n<li><strong>Example<\/strong>: Standardize to fewer shapes that better match utilization profiles.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<blockquote>\n<p>Note: Oracle\u2019s exact feature list and naming can change. The items below reflect the <strong>common Resource Analytics capability set<\/strong> in OCI\u2019s Observability and Management ecosystem. <strong>Verify in official docs<\/strong> for the exact availability in your tenancy\/region and the service that hosts the Resource Analytics pages.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">1) Historical utilization analysis<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Provides time-windowed views (days\/weeks\/months) of utilization.<\/li>\n<li><strong>Why it matters<\/strong>: Point-in-time metrics can hide chronic issues.<\/li>\n<li><strong>Practical benefit<\/strong>: Confident rightsizing and capacity planning.<\/li>\n<li><strong>Caveats<\/strong>: Retention windows and granularity depend on service configuration and pricing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Aggregation across fleets<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Summarizes utilization across many resources (for example, a group of hosts).<\/li>\n<li><strong>Why it matters<\/strong>: Operations teams manage fleets, not one server.<\/li>\n<li><strong>Practical benefit<\/strong>: Faster identification of systemic inefficiency.<\/li>\n<li><strong>Caveats<\/strong>: Requires consistent onboarding and tagging\/compartment hygiene to be meaningful.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Filtering and segmentation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Filter by dimensions (commonly compartment, resource type, time range; sometimes tags).<\/li>\n<li><strong>Why it matters<\/strong>: Enables \u201cshow me prod only\u201d or \u201conly this application\u2019s resources\u201d.<\/li>\n<li><strong>Practical benefit<\/strong>: Reduced noise; better ownership.<\/li>\n<li><strong>Caveats<\/strong>: Tag-based filtering depends on consistent tag usage.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Drill-down into individual resources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Move from summary to individual charts and details.<\/li>\n<li><strong>Why it matters<\/strong>: You need both macro and micro views.<\/li>\n<li><strong>Practical benefit<\/strong>: Quickly isolate a problematic host from a fleet.<\/li>\n<li><strong>Caveats<\/strong>: Some signals may be unavailable if a resource wasn\u2019t onboarded during that period.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Consistent utilization KPIs (CPU, memory, storage, I\/O depending on target)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Presents common KPIs for resource planning.<\/li>\n<li><strong>Why it matters<\/strong>: Standard KPIs improve cross-team alignment.<\/li>\n<li><strong>Practical benefit<\/strong>: Shared language for planning (e.g., CPU headroom).<\/li>\n<li><strong>Caveats<\/strong>: Exact metrics vary by resource type and collection method.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Integration with OCI IAM (governance)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Access controlled via OCI IAM policies.<\/li>\n<li><strong>Why it matters<\/strong>: Prevents unauthorized access to operational data.<\/li>\n<li><strong>Practical benefit<\/strong>: Separation of duties between viewers and administrators.<\/li>\n<li><strong>Caveats<\/strong>: Overly broad policies (\u201cmanage all-resources\u201d) create risk.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Auditability (via OCI Audit)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Administrative actions can be audited through OCI\u2019s audit trail.<\/li>\n<li><strong>Why it matters<\/strong>: Compliance and incident investigations.<\/li>\n<li><strong>Practical benefit<\/strong>: Trace \u201cwho changed onboarding \/ settings\u201d.<\/li>\n<li><strong>Caveats<\/strong>: Audit coverage depends on which APIs are invoked; validate in OCI Audit.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Works alongside Monitoring\/Alarms<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Resource Analytics supports planning; Monitoring supports alerting.<\/li>\n<li><strong>Why it matters<\/strong>: You need both proactive planning and reactive detection.<\/li>\n<li><strong>Practical benefit<\/strong>: Use Resource Analytics trends to tune Monitoring alarm thresholds.<\/li>\n<li><strong>Caveats<\/strong>: Not all analytics signals automatically translate into alarms; you may need custom metrics\/alarms.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level architecture<\/h3>\n\n\n\n<p>At a high level, Resource Analytics relies on:\n1. <strong>Resources producing telemetry<\/strong> (OCI Compute and other supported targets)\n2. <strong>Collection\/ingestion<\/strong> into an OCI-managed analytics backend (exact mechanism depends on your configuration)\n3. <strong>Analytics views<\/strong> (dashboards, tables, trend charts) in the OCI Console\n4. <strong>Access controls<\/strong> through OCI IAM\n5. <strong>Governance<\/strong> via Audit, compartments, and tagging<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (conceptual)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Data path<\/strong>: resource \u2192 telemetry collection \u2192 analytics backend \u2192 console visualizations<\/li>\n<li><strong>Control path<\/strong>: admin enables onboarding and access policies \u2192 users query views and drill down<\/li>\n<li><strong>Security<\/strong>: IAM authorizes access; data is encrypted in transit\/at rest (per OCI platform standards)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services (typical)<\/h3>\n\n\n\n<p>Resource Analytics commonly coexists with:\n&#8211; <strong>OCI Monitoring<\/strong> for metrics and alarms\n&#8211; <strong>OCI Logging<\/strong> for logs (and troubleshooting)\n&#8211; <strong>OCI Notifications<\/strong> for alert delivery (if you implement alarms)\n&#8211; <strong>OCI Audit<\/strong> for governance and traceability\n&#8211; <strong>OCI Vault<\/strong> if secrets\/credentials are required for onboarding certain targets (depends on what you onboard)<\/p>\n\n\n\n<p>If you intend to export analytics or create cross-domain reports, you may integrate with:\n&#8211; <strong>Object Storage<\/strong> (for report exports or archives)\n&#8211; <strong>OCI Data Integration \/ Oracle Analytics<\/strong> (enterprise reporting)<br\/>\nThese export\/report patterns vary. <strong>Verify in official docs<\/strong> for supported export mechanisms.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<p>Common dependencies in a real deployment:\n&#8211; <strong>IAM (Identity Domains \/ OCI IAM)<\/strong>: users, groups, policies\n&#8211; <strong>Compartments<\/strong>: logical isolation and ownership boundaries\n&#8211; <strong>Network access<\/strong>: outbound connectivity from collectors\/agents if used\n&#8211; <strong>Agents \/ collectors<\/strong> (when required): installed on hosts or configured for targets<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>End users authenticate via OCI Console (SSO \/ IAM).<\/li>\n<li>Access is granted via <strong>policies<\/strong>.<\/li>\n<li>Service-to-service interactions (if any) typically use OCI service principals and tenancy-scoped authorization.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Console access is via HTTPS.<\/li>\n<li>If agent-based telemetry is used, the agent requires:<\/li>\n<li>outbound connectivity to OCI endpoints (public internet or private endpoints depending on your network design)<\/li>\n<li>proper DNS resolution and time sync<br\/>\n<strong>Verify required endpoints and ports<\/strong> for your region and collector type.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>Audit<\/strong> to track administrative actions.<\/li>\n<li>Use <strong>Logging<\/strong> for agent\/collector logs where available.<\/li>\n<li>Use consistent <strong>tagging<\/strong> to make analytics segmentation meaningful.<\/li>\n<li>Consider <strong>quotas<\/strong> and <strong>limits<\/strong> for the underlying service.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  U[Engineer \/ SRE] --&gt;|OCI Console| RA[Resource Analytics]\n  R1[OCI Compute Instance(s)] --&gt;|Telemetry| RA\n  IAM[OCI IAM Policies] --&gt; RA\n  AUD[OCI Audit] --&gt; RA\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Tenancy[OCI Tenancy]\n    subgraph Compartments[Compartments]\n      PROD[Prod Compartment]\n      NONPROD[Non-Prod Compartment]\n      SHARED[Shared Services Compartment]\n    end\n\n    subgraph Sources[Telemetry Sources]\n      C1[OCI Compute Fleet]\n      C2[Autoscaled Worker Fleet]\n      DB1[Database Targets\\n(if onboarded)]\n      HYB[On-prem \/ Hybrid Hosts\\n(if supported)]\n    end\n\n    subgraph Collect[Collection Layer]\n      AG[Collectors \/ Agents\\n(if required)]\n      NET[VCN \/ Routing \/ NAT\\nor Private Connectivity]\n    end\n\n    subgraph Obs[Observability and Management]\n      RA[Resource Analytics\\n(Analytics Views)]\n      MON[Monitoring \/ Alarms]\n      LOG[Logging \/ Logging Analytics]\n      NOTIF[Notifications]\n      AUD[Audit]\n    end\n\n    IAM[IAM: Users, Groups, Policies]\n  end\n\n  C1 --&gt; AG --&gt; RA\n  C2 --&gt; AG --&gt; RA\n  DB1 --&gt; AG --&gt; RA\n  HYB --&gt; AG --&gt; RA\n\n  RA --&gt; MON\n  MON --&gt; NOTIF\n  IAM --&gt; RA\n  AUD --&gt; RA\n  LOG --&gt; RA\n  NET --- AG\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tenancy requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Oracle Cloud<\/strong> tenancy.<\/li>\n<li>Access to the OCI region where you will use Resource Analytics.<\/li>\n<li>Compartment strategy (at least one compartment for the lab).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>You need permissions to:\n&#8211; create\/manage required resources in a compartment (compute\/network for lab)\n&#8211; access Resource Analytics views\n&#8211; onboard telemetry sources (if required)<\/p>\n\n\n\n<p>For a <strong>lab<\/strong>, the simplest (but overly broad) policy is:<\/p>\n\n\n\n<pre><code class=\"language-text\">Allow group &lt;YourGroupName&gt; to manage all-resources in compartment &lt;YourCompartmentName&gt;\n<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li>This is <strong>not<\/strong> least privilege.<\/li>\n<li>Use only for short-lived labs.<\/li>\n<li>For production, use service-specific policies from official documentation. <strong>Verify in official docs<\/strong> the exact policy \u201cverbs\u201d and \u201cresource-types\/service families\u201d required for Resource Analytics and any associated onboarding service.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You need a billing-enabled tenancy.<\/li>\n<li>Some Resource Analytics capabilities may incur charges depending on:<\/li>\n<li>retention<\/li>\n<li>number of monitored resources<\/li>\n<li>module enablement<br\/>\n<strong>Verify pricing<\/strong> for your exact configuration (see Pricing section).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console access<\/li>\n<li>SSH client (for compute instance access in the lab)<\/li>\n<li>Optional: OCI CLI (not required for this tutorial)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Availability varies by service and region.<br\/>\n<strong>Verify your region supports the Resource Analytics workflow<\/strong> you plan to use.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<p>Expect limits around:\n&#8211; number of onboarded resources\/targets\n&#8211; data retention\/granularity\n&#8211; API rate limits<br\/>\nCheck <strong>Service Limits<\/strong> in the OCI Console and the official docs for the underlying service exposing Resource Analytics.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (lab)<\/h3>\n\n\n\n<p>To keep the lab practical, we\u2019ll use:\n&#8211; <strong>OCI Compute<\/strong>\n&#8211; <strong>VCN networking<\/strong>\n&#8211; A telemetry onboarding path (commonly agent-based) if your Resource Analytics workflow requires it<br\/>\nIf your tenancy already has the necessary telemetry for Resource Analytics without additional onboarding, you can skip the agent portion.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<blockquote>\n<p>Important: Oracle pricing can be region-dependent and can change. Resource Analytics is often part of a larger Observability and Management service (commonly associated with Operations Insights-style capabilities). <strong>Do not rely on fixed numbers<\/strong> from third parties. Always validate in official Oracle pricing pages and the OCI cost estimator.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Current pricing model (how to think about it)<\/h3>\n\n\n\n<p>Because Resource Analytics is typically a capability layered on top of OCI\u2019s observability\/insights services, pricing commonly depends on:\n&#8211; <strong>Which module\/service<\/strong> actually provides Resource Analytics in your tenancy\n&#8211; <strong>How many resources\/targets<\/strong> you onboard (hosts, databases, etc.)\n&#8211; <strong>Data retention and granularity<\/strong>\n&#8211; <strong>Any required collectors\/agents<\/strong> and their supporting infrastructure (compute\/networking)<\/p>\n\n\n\n<p>In many observability platforms, cost dimensions often include:\n&#8211; number of monitored entities\n&#8211; data ingestion volume\n&#8211; retention duration\n&#8211; advanced analytics features<br\/>\n<strong>Verify in official docs\/pricing<\/strong> which of these apply specifically to Resource Analytics in OCI today.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<p>OCI offers an <strong>Always Free<\/strong> tier for some core infrastructure services. Whether Resource Analytics (or the associated insights module) has an always-free allowance can vary.<br\/>\n<strong>Verify free tier eligibility<\/strong> in official Oracle documentation and pricing pages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cost drivers<\/h3>\n\n\n\n<p>Direct drivers:\n&#8211; enabling a paid insights\/analytics module (if applicable)\n&#8211; number of onboarded resources and retention settings<\/p>\n\n\n\n<p>Indirect drivers:\n&#8211; compute instances used as telemetry collectors (if you deploy them)\n&#8211; outbound network traffic from hybrid sources (if applicable)\n&#8211; storage for exported reports (Object Storage)\n&#8211; additional observability services you pair with Resource Analytics (Logging Analytics, APM, etc.)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI generally charges for some types of data egress (especially internet egress).<br\/>\nIf you onboard hybrid sources sending telemetry to OCI, consider:<\/li>\n<li>private connectivity (FastConnect \/ VPN) vs public internet<\/li>\n<li>data volume and compression<\/li>\n<li>region selection to reduce cross-region traffic<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with <strong>a small scope<\/strong>: onboard only critical compartments\/resources.<\/li>\n<li>Use <strong>shorter retention<\/strong> for high-granularity data if supported.<\/li>\n<li>Enforce <strong>tagging<\/strong> so you can identify and decommission waste.<\/li>\n<li>Build a monthly cadence: rightsizing and cleanup based on trend insights.<\/li>\n<li>Use <strong>budgets<\/strong> and <strong>cost tracking tags<\/strong> to allocate costs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (model, not numbers)<\/h3>\n\n\n\n<p>A low-cost start typically means:\n&#8211; 1 Always Free compute instance (where eligible)\n&#8211; minimal telemetry onboarding\n&#8211; default retention<br\/>\nYour costs then come mostly from any paid analytics module if required. The best practice is to model your environment in the <strong>OCI Cost Estimator<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations (what to plan for)<\/h3>\n\n\n\n<p>In production, cost planning should include:\n&#8211; total number of resources onboarded across all compartments\n&#8211; staging vs production separation\n&#8211; retention policy aligned to compliance and operational needs\n&#8211; additional observability pipelines (alarms\/notifications\/logging)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official pricing and calculators<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Pricing overview: https:\/\/www.oracle.com\/cloud\/pricing\/<\/li>\n<li>OCI Cost Estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/li>\n<li>OCI price list (SKUs): https:\/\/www.oracle.com\/cloud\/price-list\/<\/li>\n<\/ul>\n\n\n\n<p>For the most accurate view, locate the Observability and Management section in the official price list and confirm where Resource Analytics is billed (standalone vs part of another service).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab is designed to be <strong>beginner-friendly<\/strong>, <strong>safe<\/strong>, and <strong>low-cost<\/strong> where possible. It focuses on getting a small environment in place and then using <strong>Resource Analytics<\/strong> to examine utilization trends.<\/p>\n\n\n\n<p>Because Oracle can present Resource Analytics within another service\u2019s console experience (often aligned with Operations Insights), the exact page names may differ by tenancy\/region. The workflow below sticks to OCI-native patterns and calls out places where you must follow the current console prompts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Deploy a small OCI Compute instance and view its resource utilization trends using <strong>Resource Analytics<\/strong> (as exposed in your OCI tenancy), validating that telemetry is being collected and that you can drill into host-level analytics.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Create a compartment and minimal lab network.\n2. Launch a small compute instance.\n3. Configure permissions for your user\/group (lab-safe approach).\n4. Onboard the instance into the Resource Analytics data pipeline (often via an OCI agent\/collector workflow).\n5. Explore Resource Analytics views and validate data.\n6. Clean up resources to avoid ongoing charges.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Create a compartment for the lab<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the <strong>OCI Console<\/strong>, open the navigation menu.<\/li>\n<li>Go to <strong>Identity &amp; Security<\/strong> \u2192 <strong>Compartments<\/strong>.<\/li>\n<li>Click <strong>Create Compartment<\/strong>.<\/li>\n<li>Name it: <code>ra-lab<\/code><\/li>\n<li>(Optional) Add a description: <code>Resource Analytics lab compartment<\/code><\/li>\n<li>Click <strong>Create Compartment<\/strong><\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a dedicated compartment <code>ra-lab<\/code> to isolate lab resources.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the Compartments list, open <code>ra-lab<\/code> and confirm it shows as <strong>Active<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create a group and add your user (if needed)<\/h3>\n\n\n\n<p>If you already have appropriate admin permissions, you can skip this step.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Identity &amp; Security<\/strong> \u2192 <strong>Groups<\/strong><\/li>\n<li>Click <strong>Create Group<\/strong><\/li>\n<li>Name: <code>ra-lab-admins<\/code><\/li>\n<li>Create the group<\/li>\n<li>Go to <strong>Users<\/strong>, open your user, and add it to <code>ra-lab-admins<\/code><\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Your user is in a group that you can assign policies to.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In your user details, confirm <code>ra-lab-admins<\/code> is listed under groups.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create a lab policy (broad permissions for short-lived lab)<\/h3>\n\n\n\n<p>In production you should write least-privilege policies. For a short lab, use a broad policy to reduce friction.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Identity &amp; Security<\/strong> \u2192 <strong>Policies<\/strong><\/li>\n<li>Ensure you are in the <strong>root compartment<\/strong> (policies are usually created there to reference child compartments).<\/li>\n<li>Click <strong>Create Policy<\/strong><\/li>\n<li>Name: <code>ra-lab-policy<\/code><\/li>\n<li>In the policy statements, add:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-text\">Allow group ra-lab-admins to manage all-resources in compartment ra-lab\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"6\">\n<li>Create the policy<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Your group can create\/manage resources in <code>ra-lab<\/code>.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Open the policy and confirm it is <strong>Active<\/strong>.<\/p>\n\n\n\n<p><strong>Common error<\/strong>\n&#8211; <em>You still cannot create resources in <code>ra-lab<\/code>.<\/em><br\/>\n  Fix: Confirm the policy is in the correct parent scope and references the correct compartment name.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Create a VCN (network) for the compute instance<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Switch to compartment: <strong>ra-lab<\/strong><\/li>\n<li>Go to <strong>Networking<\/strong> \u2192 <strong>Virtual Cloud Networks<\/strong><\/li>\n<li>Click <strong>Create VCN<\/strong><\/li>\n<li>Choose <strong>VCN with Internet Connectivity<\/strong> (wizard name may vary)<\/li>\n<li>Accept defaults for a simple lab (VCN + public subnet + internet gateway + route table)<\/li>\n<li>Create<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A VCN with a public subnet capable of outbound internet access.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the VCN details:\n  &#8211; Internet Gateway exists\n  &#8211; Route table has a default route <code>0.0.0.0\/0<\/code> to the Internet Gateway\n  &#8211; Public subnet exists<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Launch a small compute instance<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Compute<\/strong> \u2192 <strong>Instances<\/strong><\/li>\n<li>Click <strong>Create Instance<\/strong><\/li>\n<li>Name: <code>ra-lab-vm1<\/code><\/li>\n<li>Place it in:\n   &#8211; Compartment: <code>ra-lab<\/code>\n   &#8211; VCN\/subnet: your lab VCN public subnet<\/li>\n<li>Choose an image (for example, an Oracle Linux image).<\/li>\n<li>Choose a small shape (Always Free eligible if available in your tenancy\/region).<\/li>\n<li>Add an SSH public key (or use an existing one).<\/li>\n<li>Create the instance.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; Instance <code>ra-lab-vm1<\/code> is running with a public IP.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Instance state: <strong>Running<\/strong>\n&#8211; You can see a <strong>Public IPv4 address<\/strong> (if using a public subnet)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: SSH into the instance<\/h3>\n\n\n\n<p>From your local machine:<\/p>\n\n\n\n<pre><code class=\"language-bash\">ssh -i \/path\/to\/private_key opc@&lt;PUBLIC_IP&gt;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You have a shell on the VM.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Run:<\/p>\n\n\n\n<pre><code class=\"language-bash\">uname -a\n<\/code><\/pre>\n\n\n\n<p>You should see Linux kernel information.<\/p>\n\n\n\n<p><strong>Common errors<\/strong>\n&#8211; <em>Permission denied (publickey)<\/em>: wrong username (<code>opc<\/code> for Oracle Linux images is common), wrong key, or SSH key mismatch.\n&#8211; <em>Connection timed out<\/em>: security list\/NSG doesn\u2019t allow ingress on port 22 from your IP.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Onboard telemetry for Resource Analytics (agent\/collector workflow)<\/h3>\n\n\n\n<p>This is the step where environments differ most.<\/p>\n\n\n\n<p>In many OCI setups, Resource Analytics (especially if tied to Operations Insights-style features) requires an <strong>OCI agent\/collector<\/strong> to send host telemetry.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">7A) Locate the onboarding flow in the OCI Console<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In OCI Console, go to <strong>Observability &amp; Management<\/strong>.<\/li>\n<li>Look for the service that contains <strong>Resource Analytics<\/strong> in your tenancy (commonly adjacent to <strong>Operations Insights<\/strong>).<\/li>\n<li>Find an <strong>Onboarding<\/strong> \/ <strong>Add Host<\/strong> \/ <strong>Enable<\/strong> workflow.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You find a guided onboarding page that provides:\n  &#8211; prerequisites\n  &#8211; any required agent download\/install steps\n  &#8211; a way to register the host into analytics<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; The console provides a \u201chost registered \/ agent active\u201d style status indicator after onboarding.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">7B) Install the required agent (follow the console-provided command)<\/h4>\n\n\n\n<p>If the onboarding page provides a Linux install command, <strong>copy it exactly<\/strong> and run it on <code>ra-lab-vm1<\/code> via SSH.<\/p>\n\n\n\n<p>Example pattern (do not copy blindly; use the exact command from your console):<\/p>\n\n\n\n<pre><code class=\"language-bash\"># Example pattern only \u2014 VERIFY in OCI Console instructions\n# curl -L &lt;oracle-provided-installer-url&gt; | sudo bash\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The host is registered and begins sending telemetry.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In the relevant agent\/collector page (often under Observability &amp; Management), the agent status becomes <strong>Active<\/strong> (wording may vary).\n&#8211; In Resource Analytics, the host appears in the resource list (may take several minutes).<\/p>\n\n\n\n<p><strong>Common errors and fixes<\/strong>\n&#8211; <em>Agent shows \u201cInactive\u201d<\/em>:\n  &#8211; Confirm VM has outbound internet access (or required private endpoints)\n  &#8211; Confirm system time is correct (NTP)\n  &#8211; Confirm policies allow the service\/agent to register in the compartment\n&#8211; <em>No data in charts<\/em>:\n  &#8211; Wait 10\u201330 minutes depending on collection intervals and aggregation windows\n  &#8211; Confirm the correct time range is selected in the UI<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 8: Explore Resource Analytics and review utilization trends<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong>Observability &amp; Management<\/strong> \u2192 <strong>Resource Analytics<\/strong> (or the product area where Resource Analytics appears).<\/li>\n<li>Select your compartment <code>ra-lab<\/code>.<\/li>\n<li>Locate <code>ra-lab-vm1<\/code> in the resource list.<\/li>\n<li>Open the resource details and review charts for:\n   &#8211; CPU utilization trend\n   &#8211; Memory utilization trend (if available)\n   &#8211; Storage \/ filesystem trend (if available)<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can see time-series charts and at least one utilization metric for the instance.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Change the time window (last hour, last day) and confirm the charts update.\n&#8211; If you generate activity on the VM, you should see a corresponding change after data refresh.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 9: Generate a small workload to see utilization changes (optional)<\/h3>\n\n\n\n<p>On the VM, run a short CPU load (safe, short-lived). If <code>stress<\/code> is not installed, you can use a simple loop:<\/p>\n\n\n\n<pre><code class=\"language-bash\"># Simple CPU burn for ~60 seconds (adjust as needed)\nend=$((SECONDS+60))\nwhile [ $SECONDS -lt $end ]; do\n  : $((2**20))\ndone\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; CPU utilization increases briefly.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; In Resource Analytics, check the CPU trend around that time window (may take time to appear depending on aggregation).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this checklist:\n&#8211; [ ] Instance <code>ra-lab-vm1<\/code> is running\n&#8211; [ ] Telemetry onboarding shows agent\/collector is active (if required)\n&#8211; [ ] <code>ra-lab-vm1<\/code> appears in Resource Analytics\n&#8211; [ ] At least one utilization trend chart shows data\n&#8211; [ ] You can change time range and filter by compartment<\/p>\n\n\n\n<p>If one item fails, use the Troubleshooting section below.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Symptom<\/th>\n<th>Likely cause<\/th>\n<th>Fix<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>VM not reachable via SSH<\/td>\n<td>Security list\/NSG ingress missing<\/td>\n<td>Allow TCP\/22 from your public IP; confirm public IP<\/td>\n<\/tr>\n<tr>\n<td>Agent\/collector won\u2019t activate<\/td>\n<td>No outbound access \/ DNS \/ time drift<\/td>\n<td>Confirm route to IGW\/NAT, DNS, NTP<\/td>\n<\/tr>\n<tr>\n<td>Resource not visible in analytics<\/td>\n<td>Wrong compartment\/region<\/td>\n<td>Confirm region selector and compartment filter<\/td>\n<\/tr>\n<tr>\n<td>Charts are empty<\/td>\n<td>Data not yet aggregated<\/td>\n<td>Wait; widen time range (24h); confirm onboarding succeeded<\/td>\n<\/tr>\n<tr>\n<td>Access denied in console<\/td>\n<td>Missing IAM permission<\/td>\n<td>For lab, use the broad policy; for production, follow official least-privilege policies<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing charges:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Terminate the compute instance:\n   &#8211; Compute \u2192 Instances \u2192 <code>ra-lab-vm1<\/code> \u2192 <strong>Terminate<\/strong><\/li>\n<li>Delete VCN resources (or delete the VCN created by wizard).<\/li>\n<li>Delete any agents\/collector registrations created for the lab (where applicable).<\/li>\n<li>Remove the policy <code>ra-lab-policy<\/code> if you don\u2019t need it.<\/li>\n<li>(Optional) Delete the compartment <code>ra-lab<\/code> after all resources are removed.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; No billable resources remain from the lab.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Design Resource Analytics usage around <strong>ownership boundaries<\/strong>:<\/li>\n<li>compartments per application\/team\/environment<\/li>\n<li>tags for app, cost center, environment<\/li>\n<li>Use Resource Analytics for <strong>planning<\/strong> and Monitoring for <strong>alerting<\/strong>\u2014don\u2019t conflate the two.<\/li>\n<li>Standardize resource shapes and deployment patterns so utilization comparisons are meaningful.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Avoid <code>manage all-resources<\/code> outside of labs.<\/li>\n<li>Create separate groups:<\/li>\n<li><code>resource-analytics-viewers<\/code> (read-only)<\/li>\n<li><code>resource-analytics-admins<\/code> (onboarding\/config)<\/li>\n<li>Restrict access to sensitive compartments (prod) and enforce least privilege.<\/li>\n<li>Use MFA and identity governance processes for privileged roles.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Onboard only what you need first (prod critical paths), then expand.<\/li>\n<li>Right-size based on <strong>multi-week<\/strong> data, not a single day.<\/li>\n<li>Review utilization monthly; decommission idle resources.<\/li>\n<li>Coordinate with FinOps to track savings from rightsizing actions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Validate time windows and aggregation granularity when interpreting trends.<\/li>\n<li>Ensure telemetry sources are stable:<\/li>\n<li>good network connectivity<\/li>\n<li>stable agent versions (if used)<\/li>\n<li>Correlate utilization with workload patterns (deploy windows, batch schedules).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treat onboarding\/telemetry as a dependency:<\/li>\n<li>document it in runbooks<\/li>\n<li>monitor agent health (if supported)<\/li>\n<li>Use compartments and tagging to reduce accidental misconfiguration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Establish a recurring cadence:<\/li>\n<li>weekly: review top outliers and hot spots<\/li>\n<li>monthly: rightsizing and capacity forecast review<\/li>\n<li>Record decisions and outcomes (e.g., \u201cdownsized from shape X to Y based on 30-day data\u201d).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use consistent tags:<\/li>\n<li><code>Environment<\/code> = prod\/dev\/test<\/li>\n<li><code>Application<\/code> = app name<\/li>\n<li><code>Owner<\/code> = team\/email<\/li>\n<li><code>CostCenter<\/code> = finance code<\/li>\n<li>Naming:<\/li>\n<li>include env + app + function: <code>prod-orders-api-01<\/code><\/li>\n<li>Use tag defaults (where appropriate) at the compartment level to enforce consistency.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI IAM controls who can:<\/li>\n<li>view analytics<\/li>\n<li>onboard resources<\/li>\n<li>change configurations<\/li>\n<li>Prefer group-based access and avoid user-specific policies.<\/li>\n<li>Separate duties between onboarding\/admin and viewers\/auditors.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<p>OCI services typically provide:\n&#8211; encryption in transit (TLS)\n&#8211; encryption at rest for managed services<br\/>\nFor any data retention and telemetry storage specifics, <strong>verify in official docs<\/strong> for the service that underpins Resource Analytics in your tenancy.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Keep telemetry traffic private where possible:<\/li>\n<li>private subnets + NAT for outbound<\/li>\n<li>private connectivity for hybrid (VPN\/FastConnect)<\/li>\n<li>Restrict SSH access:<\/li>\n<li>limit inbound CIDR to your corporate IP<\/li>\n<li>prefer bastion patterns for production<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<p>If onboarding requires credentials (for example, database credentials in some setups):\n&#8211; Store secrets in <strong>OCI Vault<\/strong>\n&#8211; Rotate credentials\n&#8211; Use least privilege DB accounts\n&#8211; Avoid embedding secrets in scripts or instance metadata<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>OCI Audit<\/strong> to track changes:<\/li>\n<li>policy changes<\/li>\n<li>onboarding actions<\/li>\n<li>Centralize logs where possible and enforce retention policies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Define retention consistent with compliance requirements.<\/li>\n<li>Ensure compartment and IAM boundaries align with regulatory scopes (prod vs dev\/test).<\/li>\n<li>Maintain evidence: reports of utilization and rightsizing decisions can help demonstrate operational governance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Granting broad permissions permanently (e.g., <code>manage all-resources<\/code>)<\/li>\n<li>Onboarding production resources without validating data access boundaries<\/li>\n<li>Leaving SSH open to the internet (0.0.0.0\/0)<\/li>\n<li>Not tagging resources, making it hard to detect shadow IT or abandoned infrastructure<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use least privilege policies and dedicated admin groups.<\/li>\n<li>Use private subnets and controlled egress where feasible.<\/li>\n<li>Enable auditing and review logs regularly.<\/li>\n<li>Adopt standardized onboarding procedures with peer review.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<blockquote>\n<p>The exact limitations depend on the OCI service exposing Resource Analytics in your tenancy. Validate these points in official docs.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitations (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Region scoping<\/strong>: analytics views are often region-specific.<\/li>\n<li><strong>Data latency<\/strong>: analytics are not always real-time; aggregation can take minutes to hours.<\/li>\n<li><strong>Retention constraints<\/strong>: longer retention or finer granularity may cost more or require configuration.<\/li>\n<li><strong>Coverage gaps<\/strong>: if a host\/target isn\u2019t onboarded, it won\u2019t appear in analytics.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas and limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limits on number of onboarded entities\/targets (hosts, databases, etc.)<\/li>\n<li>API throttling limits<\/li>\n<li>Service limits per region\/tenancy<br\/>\nCheck in OCI Console: <strong>Governance &amp; Administration \u2192 Limits, Quotas and Usage<\/strong> (navigation may vary).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regional constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some advanced insights modules may not be available in all regions.<\/li>\n<li>Cross-region comparisons may require external aggregation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing surprises<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Costs can scale with:<\/li>\n<li>number of onboarded resources<\/li>\n<li>retention duration<\/li>\n<li>additional modules enabled<\/li>\n<li>Hybrid telemetry can increase network costs (egress or private connectivity).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compatibility issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If agents\/collectors are required, support may vary by:<\/li>\n<li>OS versions<\/li>\n<li>host types<\/li>\n<li>network restrictions (proxy requirements)<\/li>\n<li>Verify supported platforms in official docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational gotchas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Misleading conclusions from short time windows (use at least 2\u20134 weeks for rightsizing).<\/li>\n<li>Missing tags\/compartment hygiene reduces the value of segmentation.<\/li>\n<li>Over-alerting if you convert trend insights into aggressive Monitoring alarms.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>When migrating workloads into OCI, you may have incomplete history; plan a baseline period before making aggressive rightsizing decisions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Vendor-specific nuances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI compartment and policy model is powerful but can be complex\u2014incorrect scoping is a common root cause of access issues.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Resource Analytics overlaps with\u2014but is not identical to\u2014monitoring dashboards, recommendation engines, and capacity planning tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Resource Analytics (Oracle Cloud)<\/strong><\/td>\n<td>Capacity planning and utilization trend analysis inside OCI<\/td>\n<td>OCI-native governance (IAM\/compartments), operational planning workflows<\/td>\n<td>Exact capabilities depend on underlying OCI module; may require onboarding\/agents<\/td>\n<td>When you want OCI-aligned resource utilization analytics and planning<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Monitoring<\/strong><\/td>\n<td>Real-time metrics + alarms<\/td>\n<td>Native metrics, alarms, integrations with Notifications<\/td>\n<td>Not primarily designed for long-horizon capacity planning<\/td>\n<td>When you need alerting and near real-time visibility<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI Logging Analytics<\/strong><\/td>\n<td>Log-derived analytics and troubleshooting<\/td>\n<td>Powerful log search\/parse and analytics<\/td>\n<td>Focused on logs, not utilization planning<\/td>\n<td>When the problem is log insight and incident triage<\/td>\n<\/tr>\n<tr>\n<td><strong>OCI APM<\/strong><\/td>\n<td>Application tracing and performance<\/td>\n<td>Traces, spans, app-level latency breakdowns<\/td>\n<td>Doesn\u2019t replace infra capacity analytics<\/td>\n<td>When you need application-level observability<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Compute Optimizer<\/strong><\/td>\n<td>Rightsizing recommendations in AWS<\/td>\n<td>Recommendations with AWS context<\/td>\n<td>AWS-only; different governance model<\/td>\n<td>When your workloads are primarily on AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Advisor \/ Azure Monitor Insights<\/strong><\/td>\n<td>Recommendations + monitoring in Azure<\/td>\n<td>Integrated recommendations<\/td>\n<td>Azure-only<\/td>\n<td>When your workloads are primarily on Azure<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Cloud Recommender + Cloud Monitoring<\/strong><\/td>\n<td>GCP recommendations and monitoring<\/td>\n<td>Good GCP-native tools<\/td>\n<td>GCP-only<\/td>\n<td>When your workloads are primarily on GCP<\/td>\n<\/tr>\n<tr>\n<td><strong>Prometheus + Grafana (self-managed)<\/strong><\/td>\n<td>Custom metrics\/analytics anywhere<\/td>\n<td>Flexible, portable, highly customizable<\/td>\n<td>Ops overhead, scaling, retention cost complexity<\/td>\n<td>When you need cross-cloud\/hybrid custom observability and can run it reliably<\/td>\n<\/tr>\n<tr>\n<td><strong>Commercial AIOps platforms (various)<\/strong><\/td>\n<td>Cross-domain analytics and automation<\/td>\n<td>Correlation across metrics\/logs\/traces<\/td>\n<td>Can be expensive and complex<\/td>\n<td>When you need enterprise-wide observability across multiple clouds<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example (regulated industry)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A financial services company runs core APIs and batch processing on OCI. They face periodic performance issues during month-end close and struggle to justify capacity increases.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Compartments: <code>prod<\/code>, <code>nonprod<\/code>, <code>shared<\/code><\/li>\n<li>Standard tagging across all resources (<code>CostCenter<\/code>, <code>Application<\/code>, <code>Environment<\/code>)<\/li>\n<li>Resource Analytics used for monthly capacity review and rightsizing proposals<\/li>\n<li>OCI Monitoring alarms for near real-time saturation signals<\/li>\n<li>OCI Audit enabled and reviewed for governance<\/li>\n<li><strong>Why Resource Analytics was chosen<\/strong>:<\/li>\n<li>Need long-horizon utilization trends for evidence-based capacity planning<\/li>\n<li>Need governance aligned with OCI IAM and compartment model<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Reduced unplanned scaling events during month-end<\/li>\n<li>Clear audit trail for changes and capacity decisions<\/li>\n<li>Improved utilization efficiency without breaching SLOs<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A startup runs a small OCI footprint but sees costs creeping up as features ship. They suspect dev\/test is wasteful.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Simple compartments: <code>prod<\/code>, <code>dev<\/code><\/li>\n<li>Scheduled monthly Resource Analytics review:<ul>\n<li>identify idle instances<\/li>\n<li>downsize non-prod shapes<\/li>\n<\/ul>\n<\/li>\n<li>Lightweight Monitoring alarms for critical prod signals<\/li>\n<li><strong>Why Resource Analytics was chosen<\/strong>:<\/li>\n<li>Need quick, visual trend insight without building custom tooling<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Lower spend by removing idle resources<\/li>\n<li>More predictable performance due to proactive resizing<\/li>\n<li>Better operational discipline as the team grows<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1) Is Resource Analytics a standalone OCI service?<\/h3>\n\n\n\n<p>In many tenancies, Resource Analytics is presented as an analytics experience within OCI\u2019s Observability and Management portfolio, often associated with Operations Insights-style workflows. <strong>Verify the current Oracle Cloud console navigation and docs<\/strong> for how it is surfaced in your region.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Do I need to install an agent to use Resource Analytics?<\/h3>\n\n\n\n<p>Sometimes. Some analytics require agent\/collector onboarding for host or database telemetry\u2014especially for hybrid targets. For OCI-native resources, some signals may already exist. <strong>Follow the onboarding workflow in your console<\/strong> and verify in official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) How is Resource Analytics different from OCI Monitoring?<\/h3>\n\n\n\n<p>Monitoring focuses on real-time metrics and alarms. Resource Analytics focuses on <strong>historical trends and planning<\/strong>. Many teams use both.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Can Resource Analytics help reduce cloud costs?<\/h3>\n\n\n\n<p>Yes\u2014indirectly\u2014by providing utilization evidence for rightsizing and decommissioning. Cost savings still require you to take action (resize\/terminate\/scale policies).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) Does it support compartments and tagging?<\/h3>\n\n\n\n<p>OCI governance is built around compartments, and many analytics workflows support compartment scoping. Tag-based segmentation depends on the feature set you have enabled. <strong>Verify tag filtering support<\/strong> in your console.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6) How long does it take for data to appear?<\/h3>\n\n\n\n<p>Often minutes to tens of minutes depending on collection and aggregation. For some trend views, you may need hours\/days to see meaningful patterns.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7) Is Resource Analytics real-time?<\/h3>\n\n\n\n<p>Typically it is not \u201creal-time\u201d in the alerting sense. Use OCI Monitoring alarms for near real-time alerting.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8) What\u2019s a good time window for rightsizing decisions?<\/h3>\n\n\n\n<p>Use at least <strong>2\u20134 weeks<\/strong> of data, and include peak periods (month-end, batch windows, campaigns).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9) Can I use Resource Analytics for on-prem resources?<\/h3>\n\n\n\n<p>Potentially, depending on supported onboarding\/collectors. This is common in hybrid capacity planning tools. <strong>Verify supported targets<\/strong> in official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10) Can I export Resource Analytics reports?<\/h3>\n\n\n\n<p>Some OCI services provide export\/reporting mechanisms; others do not, or they vary by module. <strong>Verify export\/report capabilities<\/strong> in official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">11) What IAM pattern should I use?<\/h3>\n\n\n\n<p>Use separate roles:\n&#8211; viewers (read-only analytics)\n&#8211; admins (onboarding\/config)\nAvoid broad \u201cmanage all-resources\u201d outside of short-lived labs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">12) How do I troubleshoot missing resources?<\/h3>\n\n\n\n<p>Check:\n&#8211; region selector\n&#8211; compartment filter\n&#8211; onboarding\/agent health (if required)\n&#8211; IAM permissions<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">13) How does Resource Analytics affect performance on the host?<\/h3>\n\n\n\n<p>If an agent is used, it typically has some overhead. In production, validate overhead in a staging environment and follow Oracle\u2019s sizing guidance. <strong>Verify agent resource requirements<\/strong> in official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">14) Is Resource Analytics suitable for Kubernetes workloads?<\/h3>\n\n\n\n<p>It can be useful at the node\/compute layer or via whatever telemetry targets are onboarded. For pod-level metrics, Kubernetes-native monitoring stacks may be needed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">15) What\u2019s the best way to operationalize Resource Analytics?<\/h3>\n\n\n\n<p>Create a cadence:\n&#8211; weekly outlier review\n&#8211; monthly rightsizing\/capacity planning review\nTrack actions and outcomes to prove value.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">16) How do I avoid \u201canalysis without action\u201d?<\/h3>\n\n\n\n<p>Tie insights to runbooks:\n&#8211; If CPU &lt; 10% for 30 days \u2192 downsize candidate\n&#8211; If CPU &gt; 75% sustained \u2192 scale candidate\n&#8211; If storage growth predicts &lt;30 days runway \u2192 cleanup\/expand plan<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Resource Analytics<\/h2>\n\n\n\n<p>Because Resource Analytics may be surfaced within another OCI Observability and Management service, the most reliable learning path is through official OCI documentation for the related insights\/analytics modules.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI Documentation main hub: https:\/\/docs.oracle.com\/en-us\/iaas\/<\/td>\n<td>Entry point to all OCI service docs and updated navigation<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Observability &amp; Management docs (browse services from OCI docs hub)<\/td>\n<td>Helps locate the current service that exposes Resource Analytics in your tenancy<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>OCI Pricing overview: https:\/\/www.oracle.com\/cloud\/pricing\/<\/td>\n<td>Official pricing entry point<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>OCI Price List: https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<td>SKU-level detail for Observability and Management services<\/td>\n<\/tr>\n<tr>\n<td>Official calculator<\/td>\n<td>OCI Cost Estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<td>Model costs without guessing<\/td>\n<\/tr>\n<tr>\n<td>Official architecture<\/td>\n<td>OCI Architecture Center: https:\/\/docs.oracle.com\/en\/solutions\/<\/td>\n<td>Reference architectures and best practices<\/td>\n<\/tr>\n<tr>\n<td>Official governance docs<\/td>\n<td>OCI IAM Overview: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/overview.htm<\/td>\n<td>Authoritative guide to IAM, policies, compartments<\/td>\n<\/tr>\n<tr>\n<td>Official governance docs<\/td>\n<td>OCI Audit Overview: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Audit\/Concepts\/auditoverview.htm<\/td>\n<td>How to track actions for compliance and investigations<\/td>\n<\/tr>\n<tr>\n<td>Official learning<\/td>\n<td>Oracle Cloud Infrastructure Learning on Oracle University: https:\/\/education.oracle.com\/<\/td>\n<td>Structured training paths (availability varies)<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>Oracle Cloud Infrastructure YouTube channel: https:\/\/www.youtube.com\/@OracleCloudInfrastructure<\/td>\n<td>Product updates and demos (verify current playlists for insights\/analytics)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<p>The following training providers may offer DevOps\/Cloud\/SRE training that can complement learning Resource Analytics in Oracle Cloud. Details vary\u2014<strong>check each website<\/strong> for current course outlines and delivery modes.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, SREs, platform teams, beginners to advanced<\/td>\n<td>DevOps tooling, cloud operations, monitoring fundamentals<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Students, engineers learning SDLC\/DevOps<\/td>\n<td>SCM, CI\/CD, DevOps foundations<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud engineers, operations teams<\/td>\n<td>Cloud operations, monitoring\/observability practices<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, operations engineers<\/td>\n<td>SRE practices, reliability, incident management<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>SREs, ops leaders, engineers<\/td>\n<td>AIOps concepts, automation for operations<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>These sites may provide trainer-led support, materials, or services related to DevOps\/Cloud\/SRE learning. <strong>Verify offerings directly<\/strong> on each site.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/Cloud training and guidance<\/td>\n<td>Beginners to intermediate engineers<\/td>\n<td>https:\/\/www.rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training content<\/td>\n<td>DevOps engineers and students<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps support\/training<\/td>\n<td>Teams needing short-term help<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support services<\/td>\n<td>Ops\/DevOps teams needing troubleshooting help<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>These organizations may provide consulting services that can help design, implement, or operationalize Oracle Cloud observability practices (including Resource Analytics-aligned workflows). <strong>Confirm scope and references directly with the provider.<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting<\/td>\n<td>Architecture, automation, operational processes<\/td>\n<td>Observability rollout planning; compartment\/tag governance; onboarding strategy<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps and cloud consulting\/training<\/td>\n<td>Tooling selection, implementation, team enablement<\/td>\n<td>Build an observability operating model; create dashboards and runbooks<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting<\/td>\n<td>CI\/CD + operations improvements<\/td>\n<td>Standardize monitoring\/alerting; implement capacity review cadence<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Resource Analytics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI fundamentals:<\/li>\n<li>compartments, VCNs, instances<\/li>\n<li>IAM policies and groups<\/li>\n<li>Observability fundamentals:<\/li>\n<li>metrics vs logs vs traces<\/li>\n<li>SLI\/SLO basics<\/li>\n<li>Basic capacity concepts:<\/li>\n<li>CPU utilization vs CPU saturation<\/li>\n<li>memory pressure and swapping<\/li>\n<li>storage growth and IOPS<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Resource Analytics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Monitoring deep dive:<\/li>\n<li>custom metrics<\/li>\n<li>alarms and notifications<\/li>\n<li>Logging\/Logging Analytics for incident triage<\/li>\n<li>APM for application-layer performance<\/li>\n<li>FinOps practices:<\/li>\n<li>tagging strategy<\/li>\n<li>budgets and chargeback\/showback<\/li>\n<li>rightsizing automation<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Cloud Ops Engineer<\/li>\n<li>SRE \/ Reliability Engineer<\/li>\n<li>DevOps Engineer<\/li>\n<li>Platform Engineer<\/li>\n<li>Cloud Architect<\/li>\n<li>FinOps Analyst \/ Cloud Cost Engineer (in collaboration with engineering)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle\u2019s certification offerings evolve. Check Oracle University for current OCI certifications and learning paths:\n&#8211; https:\/\/education.oracle.com\/<br\/>\nResource Analytics is usually learned as part of broader OCI Observability\/Operations competencies rather than as a standalone certification topic.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Build a monthly rightsizing report for non-prod compartments.<\/li>\n<li>Create a capacity runway tracker (CPU and storage) for a critical service tier.<\/li>\n<li>Implement a governance policy requiring tags (<code>Owner<\/code>, <code>Environment<\/code>, <code>Application<\/code>) and measure improvement in analytics segmentation.<\/li>\n<li>Correlate release windows with utilization trends and document performance regressions.<\/li>\n<li>Build a \u201ctop 10 hot hosts\u201d and \u201ctop 10 idle hosts\u201d operational dashboard (where supported).<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Compartment (OCI)<\/strong>: A logical container for organizing and isolating OCI resources for access control and billing.<\/li>\n<li><strong>IAM Policy (OCI)<\/strong>: A rule that grants a group (or dynamic group) permission to perform actions on resources in a scope (tenancy or compartment).<\/li>\n<li><strong>Telemetry<\/strong>: Operational data emitted by systems, commonly metrics, logs, and traces.<\/li>\n<li><strong>Utilization<\/strong>: How much of a resource is used (CPU %, memory used, disk used).<\/li>\n<li><strong>Saturation<\/strong>: A state where demand approaches or exceeds capacity (e.g., CPU pegged, I\/O queueing).<\/li>\n<li><strong>Rightsizing<\/strong>: Adjusting resource size to better match demand to reduce cost and\/or improve performance.<\/li>\n<li><strong>Retention<\/strong>: How long historical telemetry data is kept for analysis.<\/li>\n<li><strong>Granularity<\/strong>: The resolution of data points (e.g., 1-minute vs 1-hour averages).<\/li>\n<li><strong>SRE<\/strong>: Site Reliability Engineering; discipline focused on reliability using engineering practices.<\/li>\n<li><strong>SLI\/SLO<\/strong>: Service Level Indicator \/ Objective; quantitative reliability\/performance targets.<\/li>\n<li><strong>Fleet view<\/strong>: An aggregated view across many resources (hosts, instances, targets).<\/li>\n<li><strong>Drill-down<\/strong>: Navigating from summary analytics into details for a specific resource.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p><strong>Resource Analytics (Oracle Cloud)<\/strong> is a utilization and capacity-focused analytics capability within OCI\u2019s <strong>Observability and Management<\/strong> ecosystem. It helps teams move from reactive monitoring to <strong>proactive planning<\/strong>, using historical trends to rightsize resources, forecast capacity needs, and reduce operational risk.<\/p>\n\n\n\n<p>Key takeaways:\n&#8211; Use Resource Analytics for <strong>trend analysis and capacity planning<\/strong>; use <strong>OCI Monitoring<\/strong> for <strong>real-time alerting<\/strong>.\n&#8211; Cost depends on which underlying OCI insights\/analytics module is used, how many resources you onboard, and retention\u2014<strong>verify pricing in official OCI pricing pages<\/strong>.\n&#8211; Secure it with <strong>least privilege IAM<\/strong>, compartment boundaries, strong tagging, and Audit governance.\n&#8211; Start small (one compartment, a few critical resources), validate data quality, then scale out with operational cadence and documented runbooks.<\/p>\n\n\n\n<p>Next step: validate where Resource Analytics is surfaced in your OCI Console for your region, then expand the lab into a production-ready onboarding plan with least-privilege policies and a monthly capacity review process.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Observability and Management<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[75,62],"tags":[],"class_list":["post-966","post","type-post","status-publish","format-standard","hentry","category-observability-and-management","category-oracle-cloud"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/966","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=966"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/966\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=966"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}