Skip to content

Commit f477a5c

Browse files
author
iru
authored
Update README.md
1 parent 9dad1c1 commit f477a5c

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -225,9 +225,10 @@ It may take some time, but you should see logs detecting the new image in the EC
225225

226226
## Troubleshooting
227227

228-
## Q-Debug: Need to troubleshoot cloud-connector with `debug` loglevel
228+
## Q-General: Need to modify cloud-connector config (to troubleshoot with `debug` loglevel, modify ingestors for testing, ...)
229229
A: both in ECS and AppRunner workload types, cloud-connector configuration is passed as a base64-encoded string through the env var `CONFIG`
230-
<br/>S: Get current value, decode it, edit the desired `logging: debug` value, encode it again, and spin it again with this new definition.
230+
<br/>S: Get current value, decode it, edit the desired (ex.:`logging: debug` value), encode it again, and spin it again with this new definition.
231+
<br/>For information on all the modifyable configuration see [Cloud-Connector Chart](https://charts.sysdig.com/charts/cloud-connector/#configuration-detail) reference
231232

232233
### Q-General: Getting error "Error: cannot verify credentials" on "sysdig_secure_trusted_cloud_identity" data
233234
A: This happens when Sysdig credentials are not working correctly.

0 commit comments

Comments
 (0)