Reference for Application Dependency Management

This guide lists the predefined objects in OCI Resource Analytics for the Application Dependency Management 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 Application Dependency Management and their columns, data types, keys, and the referred view and column names. The following views are available:

Application Dependency Management Views
Name Description
APPLICATION_DEPENDENCY_MANAGEMENT_KNOWLEDGE_BASE_DIM_V This view stores information on knowledge base components of Application Dependency Management (ADM) service, which provide access to vulnerabilities.
APPLICATION_DEPENDENCY_MANAGEMENT_REMEDIATION_RECIPE_DIM_V This view stores information Application Dependency Management(ADM) remediation recipes, which contain the basic configuration and the details of each of the remediation stages (Detect, Recommend, Verify, and Apply).
APPLICATION_DEPENDENCY_MANAGEMENT_REMEDIATION_RECIPE_CONFIGURATION_DIM_V This view stores information on the configuration of an Application Dependency Management (ADM) remediation recipe.
APPLICATION_DEPENDENCY_MANAGEMENT_FACT_V Fact table for the Application Dependency Management service.

The suffixes in the view names specify the view type:

  • FACT_V: Fact
  • DIM_V: Dimension

Relationship Diagram

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

The contents of each view and their relationships are listed in the following file: Application Dependency Management views.

APPLICATION_DEPENDENCY_MANAGEMENT_FACT_V


Relationship diagram showing the fact table APPLICATION_DEPENDENCY_MANAGEMENT_FACT_V and its related dimension tables.

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

APPLICATION_DEPENDENCY_MANAGEMENT_REMEDIATION_RECIPE_DIM_V


Relationship diagram showing the dimension table APPLICATION_DEPENDENCY_MANAGEMENT_REMEDIATION_RECIPE_DIM_V and its relationship to COMPARTMENT_DIM_V.

Sample Queries

Sample queries for Application Dependency Management.

List the number of remediation recipes associated with a subnet.

SELECT
    D.DISPLAY_NAME AS SUBNET_NAME,
    COUNT(REMEDIATION_RECIPE_ID) AS REMEDIATION_RECIPE_COUNT
FROM OCIRA.APPLICATION_DEPENDENCY_MANAGEMENT_FACT_V F
LEFT JOIN OCIRA.VCN_SUBNET_DIM D
    ON F.NETWORK_CONFIGURATION_SUBNET_ID = D.ID
WHERE F.TIME_CREATED >= CURRENT_DATE - 30 AND F.LIFECYCLE_STATE <> 'TERMINATED'
GROUP BY D.DISPLAY_NAME;

Data Lineage

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for Application Dependency Management 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 Application Dependency Management. 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: