Skip to content

Commit 1411aee

Browse files
committed
Add support link to troubleshooting page
1 parent 01f68e6 commit 1411aee

File tree

1 file changed

+2
-22
lines changed

1 file changed

+2
-22
lines changed

content/en/cloudprem/troubleshooting.md

+2-22
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ further_reading:
1818
text: "Advanced Configurations"
1919
---
2020

21-
If you experience unexpected behavior with CloudPrem, there are a few common issues you can investigate.
21+
If you experience unexpected behavior with CloudPrem, there are a few common issues you can investigate. If you continue to have trouble, reach out to [Datadog support][1] for further assistance.
2222

2323
## Access permissions
2424

@@ -38,28 +38,8 @@ If you put the wrong region, you will see this error:
3838
Command failed: Another error occurred. `Metastore error`. Cause: `StorageError(kind=Internal, source=failed to fetch object: s3://my-bucket/datadog-index/some-id.split)`
3939
```
4040

41-
42-
43-
44-
1. Check pod status and logs:
45-
```bash
46-
# Check pod status
47-
kubectl get pods
48-
49-
# Check logs for specific components
50-
kubectl logs -l component=<your-indexer-label>
51-
kubectl logs -l component=<your-searcher-label>
52-
kubectl logs -l component=<your-metastore-label>
53-
```
54-
55-
2. Verify connectivity:
56-
- Ensure the Datadog agent can reach the internal ingress
57-
- Verify the public ingress is accessible from Datadog's services
58-
- Check that CloudPrem can access S3 and PostgreSQL
59-
60-
If you continue to have trouble, reach out to Datadog support for further assistance.
61-
6241
## Further reading
6342

6443
{{< partial name="whats-next/whats-next.html" >}}
6544

45+
[1]: /getting_started/support/

0 commit comments

Comments
 (0)