Reference for Resource Manager

This guide lists the predefined objects in OCI Resource Analytics for the Resource Manager service. You can find information about views, entity relationships, subject areas, and sample queries.

Views

This section provides information about views within OCI Resource Analytics Resource Manager and their columns, data types, keys, and the referred view and column names. The following views are available:

Resource Manager Views
Name Description
RESOURCE_MANAGER_CONFIGURATION_SOURCE_PROVIDER_DIM_V This view stores information about the properties that define a configuration source provider.
RESOURCE_MANAGER_JOB_DIM_V This view stores information about the properties of a job. A job performs the actions that are defined in your Terraform configuration.
RESOURCE_MANAGER_PRIVATE_ENDPOINT_DIM_V This view stores information about a private endpoint allowing Resource Manager to access nonpublic cloud resources.
RESOURCE_MANAGER_STACK_DIM_V This view stores information about the properties that define a stack. A stack is the collection of Oracle Cloud Infrastructure resources corresponding to a given Terraform configuration.
RESOURCE_MANAGER_TEMPLATE_DIM_V This view stores information about the properties that define a template. A template is a prebuilt Terraform configuration that provisions a set of resources used in a common scenario.
RESOURCE_MANAGER_JOB_FACT_V Fact table for Resource Manager jobs.

The suffixes in the view names designate the view type:

  • FACT_V: Fact
  • DIM_V: Dimension

The contents of each view and their relationships are listed in the following file: Resource Manager views.

Each tab in the Excel spreadsheet contains the details of a view.

Relationship Diagram

This section provides diagrams that define the logical relationship of a fact table with different dimension tables.

This diagram shows the relationship of the Resource Manager fact view with different dimension views.

RESOURCE_MANAGER_JOB_FACT_V
Relationship diagram showing the fact table, RESOURCE_MANAGER_JOB_FACT_V.

Relationships exist among dimensions. Dimensions can be joined directly to each other. This diagram shows the relationship between dimension views.

RESOURCE_MANAGER_CONFIGURATION_SOURCE_PROVIDER_DIM_V
Relationship diagram showing the dimension table, RESOURCE_MANAGER_CONFIGURATION_SOURCE_PROVIDER_DIM_V.

RESOURCE_MANAGER_PRIVATE_ENDPOINT_DIM_V
Relationship diagram showing the dimension table, RESOURCE_MANAGER_PRIVATE_ENDPOINT_DIM_V.

RESOURCE_MANAGER_TEMPLATE_DIM_V
Relationship diagram showing the dimension table, RESOURCE_MANAGER_TEMPLATE_DIM_V.

Sample Queries

Sample queries for Resource Manager.

List the number of jobs associated with each stack ID.
SELECT
    STACK_ID,
    COUNT(JOB_ID) AS JOB_COUNT
FROM OCIRA.RESOURCE_MANAGER_JOB_FACT_V F
GROUP BY STACK_ID;

Data Lineage

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for Resource Manager provides an end-to-end data lineage summary report for physical and logical relationships in your data.

For more information, see Data Lineage.

Subject Areas

This section provides information on the subject areas with data you maintain in Resource Manager. These subject areas, with their corresponding data, are available for you to use when creating and editing analyses and reports. The information for each subject area includes:

  • Description of the subject area.

  • Business questions that can be answered by data in the subject area, with a link to more detailed information about each business question.

  • Job-specific groups and duty roles that can be used to secure access to the subject area, with a link to more detailed information about each job role and duty role.

  • Primary navigation to the work area that's represented by the subject area.

  • Time reporting considerations in using the subject area, such as whether the subject area reports historical data or only the current data. Historical reporting refers to reporting on historical transactional data in a subject area. With a few exceptions, all dimensional data are current as of the primary transaction dates or system date.

  • The lowest grain of transactional data in a subject area. The lowest transactional data grain decides how data are joined in a report.

  • Special considerations, tips, and things to look out for in using the subject area to create analyses and reports.

The subject area is: