You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `cloud_logs_existing_en_instances` input variable allows you to provide a list of existing Event Notification (EN) instances that will be integrated with the Cloud Logging service. For each EN instance, you need to specify its CRN (Cloud Resource Name). You can also optionally configure a integration name and control whether to skip the creation of an authentication policy for the instance.
* Type: A list of objects. Each object represents an EN instance.
18
+
* Default value: An empty list (`[]`).
19
19
20
20
### Options for cloud_logs_existing_en_instances
21
21
22
-
-`instance_crn` (required): The Cloud Resource Name (CRN) of the Event Notification instance.
23
-
-`integration_name` (optional): The name of the Event Notification integration that gets created. If a prefix input variable is passed, it is prefixed to the value in the `<prefix>-value` format. Defaults to `"cloud-logs-en-integration"`.
24
-
-`skip_en_auth_policy` (optional): A boolean flag to determine whether to skip the creation of an authentication policy that allows Cloud Logs 'Event Source Manager' role access in the existing event notification instance. Defaults to `false`.
22
+
*`instance_crn` (required): The Cloud Resource Name (CRN) of the Event Notification instance.
23
+
*`integration_name` (optional): The name of the Event Notification integration that gets created. If a prefix input variable is passed, it is prefixed to the value in the `<prefix>-value` format. Defaults to `"cloud-logs-en-integration"`.
24
+
*`skip_en_auth_policy` (optional): A boolean flag to determine whether to skip the creation of an authentication policy that allows Cloud Logs 'Event Source Manager' role access in the existing event notification instance. Defaults to `false`.
25
25
26
26
### Example Event Notification Instance Configuration
The `cloud_logs_policies` input variable allows you to provide a list of policies that will be configured in the Cloud Logs service. Refer [here](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-tco-optimizer) for more information.
49
50
50
-
- Variable name: `cloud_logs_policies`.
51
-
- Type: A list of objects. Each object represents a policy.
52
-
- Default value: An empty list (`[]`).
51
+
* Variable name: `cloud_logs_policies`.
52
+
* Type: A list of objects. Each object represents a policy.
53
+
* Default value: An empty list (`[]`).
53
54
54
55
### Options for cloud_logs_policies
55
56
56
-
-`logs_policy_name` (required): The unique policy name.
57
-
-`logs_policy_description` (optional): The description of the policy to create.
58
-
-`logs_policy_priority` (required): The priority to determine the pipeline for the logs. Allowed values are: type_unspecified, type_block, type_low, type_medium, type_high. High (priority value) sent to 'Priority insights' (TCO pipleine), Medium to 'Analyze and alert', Low to 'Store and search', Blocked are not sent to any pipeline.
59
-
-`application_rule` (optional): The rules to include in the policy configuration for matching applications.
60
-
-`subsystem_rule` (optional): The subsystem rules to include in the policy configuration for matching applications.
61
-
-`log_rules` (required): The log severities to include in the policy configuration.
*`logs_policy_name` (required): The unique policy name.
58
+
*`logs_policy_description` (optional): The description of the policy to create.
59
+
*`logs_policy_priority` (required): The priority to determine the pipeline for the logs. Allowed values are: type_unspecified, type_block, type_low, type_medium, type_high. High (priority value) sent to 'Priority insights' (TCO pipleine), Medium to 'Analyze and alert', Low to 'Store and search', Blocked are not sent to any pipeline.
60
+
*`application_rule` (optional): The rules to include in the policy configuration for matching applications.
61
+
*`subsystem_rule` (optional): The subsystem rules to include in the policy configuration for matching applications.
62
+
*`log_rules` (required): The log severities to include in the policy configuration.
The `metrics_router_routes` input variable allows you to provide a list of routes that will be configured in the IBM Cloud Metrics Routing. Refer [here](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-about) for more information.
98
99
99
-
- Variable name: `metrics_router_routes`.
100
-
- Type: A list of objects. Each object represents a route.
101
-
- Default value: An empty list (`[]`).
100
+
* Variable name: `metrics_router_routes`.
101
+
* Type: A list of objects. Each object represents a route.
102
+
* Default value: An empty list (`[]`).
102
103
103
104
### Options for metrics_router_routes
104
105
105
-
-`name` (required): The name of the route.
106
-
-`rules` (required): The routing rules that will be evaluated in their order of the array. You can configure up to 10 rules per route.
107
-
-`action` (optional): The action if the inclusion_filters matches, default is send action. Allowed values are `send` and `drop`.
108
-
-`inclusion_filters` (required): A list of conditions to be satisfied for routing metrics to pre-defined target.'inclusion_filters' is an object with three parameters:
109
-
-`operand` - Part of CRN that can be compared with values. Allowable values are: `location`, `service_name`, `service_instance`, `resource_type`, `resource`.
106
+
*`name` (required): The name of the route.
107
+
*`rules` (required): The routing rules that will be evaluated in their order of the array. You can configure up to 10 rules per route.
108
+
*`action` (optional): The action if the inclusion_filters matches, default is send action. Allowed values are `send` and `drop`.
109
+
*`inclusion_filters` (required): A list of conditions to be satisfied for routing metrics to pre-defined target.'inclusion_filters' is an object with three parameters:
110
+
*`operand` - Part of CRN that can be compared with values. Allowable values are: `location`, `service_name`, `service_instance`, `resource_type`, `resource`.
110
111
111
-
-`operator` - The operation to be performed between operand and the provided values. Allowable values are: `is`, `in`.
112
+
*`operator` - The operation to be performed between operand and the provided values. Allowable values are: `is`, `in`.
112
113
113
-
-`values` - The provided string values of the operand to be compared with.
114
-
-`targets` (required): The target uuid for a pre-defined metrics router target.
114
+
*`values` - The provided string values of the operand to be compared with.
115
+
*`targets` (required): The target uuid for a pre-defined metrics router target.
115
116
116
117
### Example metrics_router_routes
117
118
@@ -131,22 +132,55 @@ metrics_router_routes = {
131
132
}
132
133
}
133
134
```
135
+
134
136
Refer [here](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-route_rules_definitions&interface=ui) for more information about IBM Cloud Metrics Routing route.
The `metrics_router_settings` input variable allows you to set the account settings for IBM Cloud® Metrics Routing. These settings are set to define where and how metrics are collected, routed, and managed in your account. Refer [here](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-settings-about&interface=ui) for more information.
141
+
142
+
* Variable name: `metrics_router_settings`.
143
+
* Type: An object.
144
+
* Default value: null (`null`).
145
+
146
+
### Options for metrics_router_settings
147
+
148
+
*`default_targets` (optional): A list of default target locations that is, 1 or more targets in the account, that will collect metrics from supported IBM Cloud Metrics Routing locations where the user have not configured how they want to collect metrics.
149
+
*`permitted_target_regions` (optional): Displays the targets regions where metrics can be sent.
150
+
*`primary_metadata_region` (optional): The location where the IBM Cloud Metrics Routing account configuration metadata is stored. For new accounts, all target/route creation will fail until `primary_metadata_region` is set.
151
+
*`backup_metadata_region` (optional): To backup all your meta data in a different region.
152
+
*`private_api_endpoint_only` (optional): The type of endpoints that are allowed to manage the IBM Cloud Metrics Routing account configuration in the account. If you set this true then you cannot access api through public network.
Refer [here](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-settings&interface=ui) for more information about IBM Cloud Metrics Routing settings.
The `at_cos_bucket_retention_policy` input variable allows you to provide the retention policy of the IBM Cloud Activity Tracker Event Routing COS target bucket that will be configured. Refer [here](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable) for more information.
The `cloud_log_data_bucket_retention_policy` input variable allows you to provide the retention policy of the IBM Cloud Logs data bucket that will be configured. Refer [here](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable) for more information.
0 commit comments