As an Application Engineer, you will be confronted with tickets that require you to seek help from engineering. You are encouraged to do so! There are two ways to do so, largely depending on the nature of the ticket.
For “how-to” tickets, you are not required to create a Request for help (RFH) in GitHub1. Instead, follow the procedure below.
- As you normally would, check the docs, and ticket database (searchable on
cse-k8s) for possible solutions.
- If no solution is found, create a new post in the #customer-support-internal channel in Slack. Start the post with “HTQ:” so that it is searchable in the future.
- If you still don’t have a solution after doing so, create a new post in #ask-engineering in slack. Again, make sure you start the post with “HTQ:” to make it more searchable.
- If you are not getting a response, raise this to leadership, and they will help move the request forward.
- Lastly, once a solution is provided and the ticket is closed,
- include the Slack thread in your summary for future AER lookup
- update relevant pages on docs for future customer questions
RFH’s should be reserved for tickets that are more complex in nature. More times than not, this is intuitive, but in case you find yourself unsure of whether an issue warrants an RFH, here are a few good markers:
- Is it likely this will require deep research/work from an engineering team?
- Is it likely that multiple log files or grafana screen shots will be shared throughout the troubleshooting process?
- Is this issue a P1?
- Does this customer require a high touch?
If the answer to any one of these questions is “yes”, it’s probably a good idea to file an RFH.
While RFH’s are a valuable tool when dealing with complex issues, they introduce overhead and complexity that isn’t necessary for “How-To” questions. Furthermore, they limit visibility, and collaboration between teams that happens in public, shared channels. ↩