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
Copy file name to clipboardexpand all lines: solutions/instances/DA-types.md
+59-6
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,24 @@
1
-
# Configuring Event Notification (EN) Instances for Cloud Logging
1
+
# Configuring complex inputs for Cloud Automation for Observability
2
2
3
-
An optional input variables in the IBM Cloud [Observability instances deployable architecture](https://cloud.ibm.com/catalog#deployable_architecture) use complex object types. You specify these inputs when you configure deployable architecture.
3
+
Several optional input variables in the IBM Cloud [Observability instances deployable architecture](https://cloud.ibm.com/catalog#deployable_architecture) use complex object types. You specify these inputs when you configure deployable architecture.
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 with the following attributes:
14
+
- Type: A list of objects. Each object represents an EN instance.
15
+
- Default value: An empty list (`[]`).
16
+
17
+
### Options for cloud_logs_existing_en_instances
18
+
13
19
-`instance_crn` (required): The Cloud Resource Name (CRN) of the Event Notification instance.
14
20
-`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"`.
15
21
-`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`.
16
-
- Default value: An empty list (`[]`).
17
-
18
22
19
23
### 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.
46
+
47
+
- Variable name: `cloud_logs_policies`.
48
+
- Type: A list of objects. Each object represents a policy.
49
+
- Default value: An empty list (`[]`).
50
+
51
+
### Options for cloud_logs_policies
52
+
53
+
-`logs_policy_name` (required): The unique policy name.
54
+
-`logs_policy_description` (optional): The description of the policy to create.
55
+
-`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.
56
+
-`application_rule` (optional): The rules to include in the policy configuration for matching applications.
57
+
-`subsystem_rule` (optional): The subsystem rules to include in the policy configuration for matching applications.
58
+
-`log_rules` (required): The log severities to include in the policy configuration.
logs_policy_description = "Send info and debug logs of the application (name starts with `test-system-app`) and the subsytem (name starts with `test-sub-system`) logs to Store nad search pipeline"
68
+
logs_policy_priority = "type_low"
69
+
application_rule = [{
70
+
name = "test-system-app"
71
+
rule_type_id = "start_with"
72
+
}]
73
+
log_rules = [{
74
+
severities = ["info", "debug"]
75
+
}]
76
+
subsystem_rule = [{
77
+
name = "test-sub-system"
78
+
rule_type_id = "start_with"
79
+
}]
80
+
},
81
+
{
82
+
logs_policy_name = "logs-policy-2"
83
+
logs_policy_description = "Send error logs of all applications and all subsystems to Analyze and Alert pipeline"
description="Log Analysis has been deprecated, and can no longer be deployed wuth this solution, however you can continue to manage the COS bucket that may have been in older versions for Log Analysis log archiving by setting this input to true."
0 commit comments