Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Edge - Gateway Troubleshooting Documentation #391

Closed
NiaStorj opened this issue Jan 16, 2024 · 6 comments
Closed

Edge - Gateway Troubleshooting Documentation #391

NiaStorj opened this issue Jan 16, 2024 · 6 comments
Assignees
@nergdron
Labels
documentation Improvements or additions to documentation edge

Comments

@NiaStorj
Copy link

NiaStorj commented Jan 16, 2024 •
edited

Motivation/Why?

This documentation is for our internal Storj teams to use before contacting an engineer to troubleshoot.

Goal

To cut down on:
Edge team spending time in slack troubleshooting
ticketes/issues for things that could be resolved via the documentation
@NiaStorj NiaStorj added edge documentation Improvements or additions to documentation labels Jan 16, 2024
@amwolff
Copy link
Member

amwolff commented Jan 26, 2024

  1. Document hosted gateway endpoints
  2. Document where to get help if routing is bad
  3. Identify what we spent time on in the past that could be resolved via documentation
  4. Document how to escalate

@amwolff
Copy link
Member

amwolff commented Jan 26, 2024

@NiaStorj will clarify if this is for SPC specifically.

@NiaStorj
Copy link
Author

NiaStorj commented Jan 26, 2024 •
edited

@amwolff JG confirmed SPC related troubleshooting is not needed at this time. It will probably be needed in the near future.

@amwolff
Copy link
Member

amwolff commented Jan 30, 2024

@NiaStorj says this should live in Confluence.

@nergdron
Copy link
Contributor

nergdron commented Feb 6, 2024

work in progress:
https://storjlabs.atlassian.net/wiki/spaces/OPS/pages/2728001548/Gateway+Troubleshooting

@nergdron nergdron mentioned this issue Feb 6, 2024
Open
@NiaStorj NiaStorj mentioned this issue Mar 20, 2024
Open
@NiaStorj
Copy link
Author

@nergdron this ticket can be moved to done. John wanted to add additional information to the document, so I created another issue with updated AC.

#416 - new ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nergdron nergdron

Labels
documentation Improvements or additions to documentation edge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nergdron @amwolff @NiaStorj