Skip to content

docs: update Troubleshooting Guidelines section #1740

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Anze1508
Copy link

Our support team decided to change the command so that it outputs a ZIP file, which is better than a .gz file because it can be sent both on HubSpot and on Slack.

Copy link

⚡️ Deploying PR Preview...

@Anze1508 Anze1508 requested a review from komarkovich April 28, 2025 10:14
@quetzalliwrites quetzalliwrites self-requested a review April 29, 2025 15:24
Copy link
Collaborator

@quetzalliwrites quetzalliwrites left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for putting this up! 🌷

Let's just make sure we make it clear HOW and WHERE they send this info to us.

- Call the diagnostic endpoint `curl -s localhost:4566/_localstack/diagnose | gzip -cf > diagnose.json.gz` (Endpoint URL depends on your configuration)
- Send the output file to our Slack chat
- Call the diagnostic endpoint `curl -s localhost:4566/_localstack/diagnose > diagnose.json && zip diagnose.zip diagnose.json && rm diagnose.json` (Endpoint URL depends on your configuration)
- Send the output file to us
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unclear, where and how do they send it to us?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants