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: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ No modules.
135
135
| <aname="input_deployment_tag"></a> [deployment\_tag](#input\_deployment\_tag)| Sets a global tag that will be included in the components. It represents the mechanism from where the components have been installed (terraform, local...). |`string`|`"terraform"`| no |
136
136
| <aname="input_enable_host_scanner"></a> [enable\_host\_scanner](#input\_enable\_host\_scanner)| Enable host scanning to detect vulnerabilities and identify the resolution priority based on available fixed versions and severity. Requires a Security and Compliance Center Workload Protection instance to view results. |`bool`|`true`| no |
137
137
| <aname="input_enable_kspm_analyzer"></a> [enable\_kspm\_analyzer](#input\_enable\_kspm\_analyzer)| Enable Kubernetes Security Posture Management (KSPM) analyzer. Requires a Security and Compliance Center Workload Protection instance to view results. |`bool`|`true`| no |
138
-
| <aname="input_enable_universal_ebpf"></a> [enable\_universal\_ebpf](#input\_enable\_universal\_ebpf)| Deploy monitoring agent with universal extended Berkeley Packet Filter (eBPF) enabled. It requires kernel version 5.8+. Learn more: https://github.com/terraform-ibm-modules/terraform-ibm-monitoring-agent/blob/main/solutions/fully-configurable/DA-docs.md#when-to-enable-enable_universal_ebpf|`bool`|`true`| no |
138
+
| <aname="input_enable_universal_ebpf"></a> [enable\_universal\_ebpf](#input\_enable\_universal\_ebpf)| Deploy monitoring agent with universal extended Berkeley Packet Filter (eBPF) enabled. It requires kernel version 5.8+. [Learn more](https://github.com/terraform-ibm-modules/terraform-ibm-monitoring-agent/blob/main/solutions/fully-configurable/DA-docs.md#when-to-enable-enable_universal_ebpf)|`bool`|`true`| no |
139
139
| <aname="input_existing_access_key_secret_name"></a> [existing\_access\_key\_secret\_name](#input\_existing\_access\_key\_secret\_name)| An alternative to using `access_key`. Specify the name of an existing Kubernetes secret containing the access key in the same namespace that is defined in the `namespace` input. Either `access_key` or `existing_access_key_secret_name` is required. |`string`|`null`| no |
140
140
| <aname="input_image_registry_base_url"></a> [image\_registry\_base\_url](#input\_image\_registry\_base\_url)| The image registry base URL to pull all images from. For example `icr.io` or `quay.io`. |`string`|`"icr.io"`| no |
141
141
| <aname="input_image_registry_namespace"></a> [image\_registry\_namespace](#input\_image\_registry\_namespace)| The namespace within the image registry to pull all images from. |`string`|`"ext/sysdig"`| no |
@@ -146,6 +146,7 @@ No modules.
146
146
| <aname="input_metrics_filter"></a> [metrics\_filter](#input\_metrics\_filter)| To filter custom metrics you can specify which metrics to include and exclude. For more info, see https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent#change_kube_agent_inc_exc_metrics| <pre>list(object({<br/> include = optional(string)<br/> exclude = optional(string)<br/> }))</pre> |`[]`| no |
147
147
| <aname="input_name"></a> [name](#input\_name)| The name to give the agent helm release. |`string`|`"sysdig-agent"`| no |
148
148
| <aname="input_namespace"></a> [namespace](#input\_namespace)| Namespace to deploy the agent to. |`string`|`"ibm-observe"`| no |
149
+
| <aname="input_prometheus_config"></a> [prometheus\_config](#input\_prometheus\_config)| Prometheus configuration for the agent. If you want to enable Prometheus configuration provide the prometheus.yaml file content in `hcl` format. [Learn more](https://github.com/terraform-ibm-modules/terraform-ibm-monitoring-agent/blob/main/solutions/fully-configurable/DA-types.md#prometheus_config). |`map(any)`|`{}`| no |
149
150
| <aname="input_tolerations"></a> [tolerations](#input\_tolerations)| List of tolerations to apply to the agent. | <pre>list(object({<br/> key = optional(string)<br/> operator = optional(string)<br/> value = optional(string)<br/> effect = optional(string)<br/> tolerationSeconds = optional(number)<br/> }))</pre> | <pre>[<br/> {<br/> "operator": "Exists"<br/> },<br/> {<br/> "effect": "NoSchedule",<br/> "key": "node-role.kubernetes.io/master",<br/> "operator": "Exists"<br/> }<br/>]</pre> | no |
150
151
| <aname="input_use_private_endpoint"></a> [use\_private\_endpoint](#input\_use\_private\_endpoint)| Whether send data over a private endpoint or not. To use a private endpoint, you must enable virtual routing and forwarding (VRF) for your account. See https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint.|`bool`|`true`| no |
151
152
| <aname="input_use_scc_wp_endpoint"></a> [use\_scc\_wp\_endpoint](#input\_use\_scc\_wp\_endpoint)| By default an IBM Cloud Monitoring endpoint is used and is constructed from the `instance_region` and `use_private_endpoint` inputs. To use an IBM Cloud Security and Compliance Center Workload Protection endpoint instead, set this to true. |`bool`|`false`| no |
Copy file name to clipboardExpand all lines: solutions/fully-configurable/DA-types.md
+47Lines changed: 47 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,3 +47,50 @@ type = list(object({
47
47
48
48
**Tip:**
49
49
Use `metrics_filter` to optimize your monitoring setup by collecting only the metrics that matter most to your use case. This can help reduce costs and improve performance.
50
+
51
+
## `prometheus_config`
52
+
53
+
The `prometheus_config` variable allows you to enable sysdig agent to scrape metrics from processes that expose Prometheus metric endpoints on its own host and send findings to the Sysdig collector for storing and further processing.
description="Prometheus configuration for the agent. If you want to enable Prometheus configuration provide the prometheus.yaml file content in `hcl` format. [Learn more](https://github.com/terraform-ibm-modules/terraform-ibm-monitoring-agent/blob/main/solutions/fully-configurable/DA-types.md#prometheus_config)."
0 commit comments