OCI Tags help you organize resources according to your business needs. OCI Tags can be applied to Stack Monitoring resources during discovery, from within the resource homepages, and using the CLI. For details on adding/removing and updating tags using the CLI, see the documentation.

Prerequisites

There are two types of OCI tags, Freeform Tags and Defined Tags. In order to use Defined Tags with Stack Monitoring resources, the administrator should first create the Tag namespaces. Refer to Tags and Tag Namespace Concepts for details on creating and managing the Tag namespaces for Defined Tags.

Tag Propagation

When an OCI Tag is applied to a resource, the same tag will also be applied to related resources automatically. Within Stack Monitoring OCI Tag propagation is implemented asynchronously. As a result OCI Tags may not be displayed on a resource home page for several seconds. It is recommended to ensure the tags appear on resource homepages before completing any related tasks such as adding a new tag or updating and existing OCI Tag, etc.

Discovery Propagation

During discovery, OCI Tags are applied to all of the resources being discovered, and any related resources. For example when discovering an EBS application, any tag assigned will be applied to all resources created (EBS, Concurrent Manager, Notification Mailer, etc). If the database that contains the EBS schema has already been discovered, the OCI Tag will also be applied to the Oracle Database.

Home Page Propagation

Adding, deleting, and updating OCI Tags from a home page, will propagate to all related resources. For example when discovering an EBS application, any OCI Tag assigned will be applied to all resources created (EBS, Concurrent Manager, Notification Mailer, etc) and related members including the Oracle Database and host.

Tag Based Privileges

Administrators can control access to stack monitoring functionality and resources using policies defined based on tags. Administrator should have permission to create tag namespaces in the compartment. The following example policy assumes that user created a tag namespace called "adminTags" and also created a defined-tag called "category" in the "adminTags" namespace.