Sentry Enabled By Default (#1721)

* Update values.yaml

Enable Sentry by default.

* Update README.md
This commit is contained in:
Alon Girmonsky
2025-03-24 14:09:58 -07:00
committed by GitHub
parent f85c7dfb4b
commit c95d63feb0
2 changed files with 2 additions and 2 deletions

View File

@@ -200,7 +200,7 @@ Example for overriding image names:
| `tap.debug` | Enable debug mode | `false` |
| `tap.telemetry.enabled` | Enable anonymous usage statistics collection | `true` |
| `tap.resourceGuard.enabled` | Enable resource guard worker process, which watches RAM/disk usage and enables/disables traffic capture based on available resources | `false` |
| `tap.sentry.enabled` | Enable sending of error logs to Sentry | `false` |
| `tap.sentry.enabled` | Enable sending of error logs to Sentry | `true` (only for qualified users) |
| `tap.sentry.environment` | Sentry environment to label error logs with | `production` |
| `tap.defaultFilter` | Sets the default dashboard KFL filter (e.g. `http`). By default, this value is set to filter out noisy protocols such as DNS, UDP, ICMP and TCP. The user can easily change this, **temporarily**, in the Dashboard. For a permanent change, you should change this value in the `values.yaml` or `config.yaml` file. | `"!dns and !error"` |
| `tap.liveConfigMapChangesDisabled` | If set to `true`, all user functionality (scripting, targeting settings, global & default KFL modification, traffic recording, traffic capturing on/off, protocol dissectors) involving dynamic ConfigMap changes from UI will be disabled | `false` |

View File

@@ -146,7 +146,7 @@ tap:
watchdog:
enabled: true
sentry:
enabled: false
enabled: true
environment: production
defaultFilter: "!dns and !error"
liveConfigMapChangesDisabled: false