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
added support to the Observability DA instances variation to create COS resources in a different account to the Observability resources (#175) (70a0338)
supported added to the agents variation to provision the logs agent for sending logs to IBM Cloud logs - NOTE: The Log Analysis agent is not longer deploted by default due to the Log Analysis services being deprecated (#167) (4a3a47f)
added support to the DA to wait till cluster is ready before deploying it using new inputs wait_till, wait_till_timeout and is_vpc_cluster (#168) (7dd440a)
added support for IBM Cloud Logs. By default, the instances variation will now deploy this instead of Log Analysis. To manage platform logs that are generated by IBM Cloud® services in a region of IBM Cloud, you must create a tenant in each region that you operate. This can be done passing the regions into the logs_routing_tenant_regions input.
Activity tracking will still send events to a COS bucket target, but now by default it will also send them to IBM Cloud Logs. These settings can be toggled using the enable_at_event_routing_to_cloud_logs and enable_at_event_routing_to_cos_bucket boolean inputs.
Upgrade considerations:
If you are upgrading from a previous version, and using the default inputs, you will see the Log Analysis instance identified for destroy. If you are not ready yet to destroy it, you can toggle the values of the log_analysis_provision and cloud_logs_provision inputs, but please be aware that Log Analysis is a deprecated service, and new instances cannot be provisioned after November 30, 2024. (#137) (9616b28)