Submit a request
Solo customers can submit new requests and update existing ones by using the Support Portal, email (support@solo.io), or Slack.
Use the Support Portal
Create a Support Portal account
- Navigate to the Support Portal and click Sign up.
- On the next page, enter your full name and email address. You receive an email with instructions for how to create a password.
- Follow the Create password link in that email. Check your Spam folder if you do not see it in your inbox.
- You MUST add your phone number to your newly created profile. Failing to do so prevents your calls from being routed to a Solo Support Engineer when you call the Support Hotline to report Urgent incidents.
Submit a ticket
- Navigate to the Support Portal.
- Log in, and ensure your phone number is added to your profile. This is an important step, as it allows our system to recognize your account when you call the Support Hotline for urgent incidents.
- Click Create a ticket.
- Fill out the form. Start by entering any email addresses that you want updates to be sent to while Solo Support works on the ticket. Add a subject related to the issue that you are reporting.
- Add details for the issue in the description field. Refer to Details to include in your support request to help Solo Support better understand your request and provide timely and accurate assistance.
- Enter the priority for this request. To learn more about priority levels and how to assign the right priority level to your ticket, see Priority levels.
- Optional: Enter a GitHub issue and upload any attachments.The ticketing system has an attachment file size limit of 50MB.
- Submit your request. A Solo Support Engineer will be in touch following the Targeted times for initial response.
To update an existing ticket, log in to your account, and click View pending tickets. You see a new page where you can select the ticket you want to update and add comments to.
Details to include in your support request
Environment:
- Versions for Gloo Gateway and Kubernetes
- Infrastructure provider, such as AWS or on-premises VMs
- Production, development, or other environment details
Setup:
- Installation method, such as Helm or
glooctl - Gateway details and namespace
- HTTPRoute details and namespace
- ReferenceGrant details if applicable
Issue:
- Description of the issue
- Steps to reproduce the issue
- Attach any relevant configuration/YAML files related to the issue, such as Gateway, HTTPRoute, or ReferenceGrant resources
- Severity of the issue, such as urgent, high, normal, or low
- Impact of the issue, such as blocking an update, blocking a demo, data loss or the system is down
Product-specific details:
- Control plane issues:
- Output of
glooctl check - Logs, debug mode if possible, from the
gloopod
- Output of
- Data plane issues:
- Config_dump from the gateway (envoy) pod
- Envoy access log(s) for failed request
- If possible, Envoy debug logs during failed request
Priority levels
| Priority level | Description |
|---|---|
| Urgent priority** | A problem that severely impacts your use of the software in a production environment, such as loss of production data, or in which your production systems are not functioning. The situation halts your business operations, or your revenue or brand are impacted and no procedural workaround exists. |
| High priority | A problem where the production environment is operational but functionality is severely reduced. The situation is causing a high impact to portions of your business operations, or your revenue or brand are threatened and no procedural workaround exists. |
| Normal priority | A problem that involves partial, non-critical loss of use of the software in a production environment or development environment. For production environments, there is a medium-to-low impact on your business, but your business continues to function, including by using a procedural workaround. For development environments, where the situation is causing your project to no longer continue or migrate into production. |
| Low priority | A general usage question, reporting of a documentation error, or recommendation for a future product enhancement or modification. For production environments, there is low-to-no impact on your business or the performance or functionality of your system. For development environments, there is a medium-to-low impact on your business, but your business continues to function, including by using a procedural workaround. |
Targeted times for initial response
When you contact Solo Support, you can choose a priority for your request:
| Priority Level | Standard Support Policy | Enhanced Support Policy |
|---|---|---|
Urgent** | 1 hour (24/7/365) | 15 minutes (24/7/365) |
| High | 4 hours | 2 hours (24/7/365) |
| Normal | 8 hours | 4 hours |
| Low | 24 hours | 12 hours |
**For urgent priority issues that impact production, call the Support Hotline.
Solo Support reserves the right to adjust the priority you select if it does not align with the priorities documented above.
Join the solo.io Slack community
Join the solo.io Slack community to participate in conversations with other users and ask questions to the Solo team.
Navigate through the channels to find topics relevant to you. We recommend #gloo, and #general for general discussion.
To migrate a discussion from Slack into an email-based support ticket, you can use the /zendesk create_ticket macro within the channel where the conversation started. Select Support as the assignee to ensure your request reaches the Solo Support team. Selecting other options will delay or prevent our team from seeing your ticket.
If the macro hasn’t been added to a channel, ask a Solo team member to assist you.
Additional resources
Check out the following guides to start troubleshooting your environment and to collect the information to provide in your support request.
- Downloadable version of our versioned Technical Support Policy
- Gloo Gateway contribution guidelines
- Gloo Gateway community