|
| 1 | +--- |
| 2 | +title: Troubleshooting Go App and API Protection |
| 3 | +--- |
| 4 | + |
| 5 | +## Common Issues |
| 6 | + |
| 7 | +### No security signals appearing |
| 8 | + |
| 9 | +1. **Verify Agent version** |
| 10 | + - Ensure you're running Datadog Agent v7.41.1 or higher |
| 11 | + - Check Agent status: `datadog-agent status` |
| 12 | + |
| 13 | +2. **Check Go tracer version** |
| 14 | + - Confirm you're using Go tracer v1.53.0 or higher |
| 15 | + |
| 16 | +3. **Verify environment variables** |
| 17 | + - Ensure `DD_APPSEC_ENABLED=true` is set |
| 18 | + - Check `DD_SERVICE` and `DD_ENV` are properly configured |
| 19 | + |
| 20 | +4. **Check file system permissions** |
| 21 | + - Ensure the application has write access to `/tmp` if you are not on linux |
| 22 | + |
| 23 | +5. **Check your framework is actually compatible** |
| 24 | + - Review the [Go compatibility requirements][1] to ensure your framework and libraries are supported |
| 25 | + |
| 26 | +### Application fails to start |
| 27 | + |
| 28 | +TODO: linker & shared libraries issues |
| 29 | + |
| 30 | +TODO: Incompatible libc version |
| 31 | + |
| 32 | +### Build failures |
| 33 | + |
| 34 | +TODO: Building on alpine and running on glibc-based systems and the other way around |
| 35 | + |
| 36 | +TODO: Bazel build issues |
| 37 | + |
| 38 | +### Still having issues? |
| 39 | + |
| 40 | +If you're still experiencing problems: |
| 41 | +1. Check the [Application Security Monitoring troubleshooting guide][1] |
| 42 | +2. Review the [Go tracer documentation][2] |
| 43 | +3. Contact [Datadog support][3] |
| 44 | + |
| 45 | +[1]: /security/application_security/troubleshooting |
| 46 | +[2]: /tracing/trace_collection/compatibility/go |
| 47 | +[3]: /help |
0 commit comments