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
feat: added support for the new cloud logs agent to send logs directly to a Cloud Logs instance. This is now the default logging agent deployed by this module as the Log Analysis service is deprecated (#368)
Copy file name to clipboardExpand all lines: cra-config.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# More info about this file at https://github.com/terraform-ibm-modules/common-pipeline-assets/blob/main/.github/workflows/terraform-test-pipeline.md#cra-config-yaml
2
2
version: "v1"
3
3
CRA_TARGETS:
4
-
- CRA_TARGET: "examples/basic"# Target directory for CRA scan. If not provided, the CRA Scan will not be run.
4
+
- CRA_TARGET: "examples/obs-agent-ocp"# Target directory for CRA scan. If not provided, the CRA Scan will not be run.
5
5
CRA_IGNORE_RULES_FILE: "cra-tf-validate-ignore-rules.json"# CRA Ignore file to use. If not provided, it checks the repo root directory for `cra-tf-validate-ignore-rules.json`
6
6
PROFILE_ID: "0e6e7b5a-817d-4344-ab6f-e5d7a9c49520"# SCC profile ID (currently set to the FSCloud 1.4.0 profile).
7
7
# SCC_INSTANCE_ID: "" # The SCC instance ID to use to download profile for CRA scan. If not provided, a default global value will be used.
# Monitoring agent + Cloud Logs agent on Kubernetes using CSE ingress endpoint with an apikey
2
+
3
+
An example that shows how to deploy Logs agents and Monitoring agent in a Kubernetes cluster to send Logs directly to IBM Cloud Logs and Cloud Monitoring instance respectively.
4
+
5
+
The example provisions the following resources:
6
+
- A new resource group, if an existing one is not passed in.
7
+
- A basic VPC (if `is_vpc_cluster` is true).
8
+
- A Kubernetes cluster.
9
+
- A Service ID with `Sender` role to `logs` service and an apikey.
# As a `Sender`, you can send logs to your IBM Cloud Logs service instance - but not query or tail logs. This role is meant to be used by agents and routers sending logs.
18
+
module"iam_service_id" {
19
+
source="terraform-ibm-modules/iam-service-id/ibm"
20
+
version="1.2.0"
21
+
iam_service_id_name="${var.prefix}-service-id"
22
+
iam_service_id_description="Logs Agent service id"
# example of how to include / exclude metrics - more info https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_log_metrics
167
-
cloud_monitoring_metrics_filter=[{ type ="exclude", name ="metricA.*" }, { type ="include", name ="metricB.*" }]
0 commit comments