A valid statement about creating an alarm query in OCI Monitoring is that you must specify a resource group. A resource group is an optional feature that allows you to group metrics by certain attributes or tags. By specifying a resource group in your alarm query, you can filter out the metrics that belong to different resource groups and focus on the ones that are relevant for your alarm condition.

Two examples of a Stack Monitoring deployment model are:

• Resources running on OCI compute instances. Stack Monitoring can monitor resources that are running on OCI compute instances, such as web servers, containers, or functions. Stack Monitoring can discover these resources using Management Agents or Functions Discovery Service.
• Resources running on-premises. Stack Monitoring can also monitor resources that are running on-premises, such as databases or applications. Stack Monitoring can discover these resources using Enterprise Manager Bridge or Management Agents.

The correct logging CLI syntax for the log search with a query for REST call responses having status code 400, within the web Log Group and the application Log is oci logging-search search-logs --search-query ‘search “ocidl.compartment.ocl…aaaaaaaawqegmjifhni77bqm625cxioavoq775jckfn2syxqtmglabcccdxyz/web/application” I where data.statusCode = 400’–time-start 2022-02-06T00:00:002 --time-end 2022-02-07T00:00:002. This syntax will search for log records that match the following criteria:

• The log records belong to the compartment with OCID ocidl.compartment.ocl…aaaaaaaawqegmjifhni77bqm625cxioavoq775jckfn2syxqtmglabcccdxyz
• The log records belong to the web Log Group and the application Log
• The log records have a field called data.statusCode with a value of 400
• The log records are within the time range from 2022-02-06T00:00:002 to 2022-02-07T00:00:002