Skip to main content

Submit a support request or feature request

This topic describes how to open a support request or submit a feature request to the Replicated team. It also describes how to attach support bundles to existing support issues.

For more information about working with support bundles, see Generating Support Bundles.

Overview​

You can submit support requests, feature requests, and support bundles through the Vendor Portal. For support and feature requests, a multi-step wizard guides you through selecting a product area, reviewing self-service resources, and submitting your request.

Replicated recommends that you always provide a support bundle when you open a new support request, and that you attach new bundles to an existing support issue when conditions change or new problems arise. Uploading a support bundle is secure and helps the Replicated support team troubleshoot your application faster. Severity 1 issues are resolved three times faster when you submit a support bundle with your support request.

Prerequisites​

The following prerequisites must be met to submit support requests:

  • Your Vendor Portal account must be configured for access to support before you can submit support requests. Contact your administrator to ensure that you are added to the correct team.

  • Your team must have a replicated-collab repository configured. If you are a team administrator and need information about getting a collab repository set up and adding users, see Adding Users to the Collab Repository.

If you open a support request when viewing a bundle on the Vendor Portal Support Bundle Analysis page, the support request form is pre-populated with information from the support bundle and the associated customer license. The support bundle is also automatically attached to the request.

To submit a support request from the Support Bundle Analysis page:

  1. In the Vendor Portal, go to the Troubleshoot tab.

  2. Select the support bundle that you want to attach to a new support request. If you need to upload the support bundle, click Add support bundle > Upload a support bundle.

  3. At the top of the Support Bundle Analysis page, click Submit support ticket.

    note

    The Share with Replicated button on the Support Bundle Analysis page does not open a support request. You might be directed to use the Share with Replicated option when you are already interacting with a Replicated team member. For more information, see Provide support bundles to Replicated after opening a support request.

  4. In section 1 of the support request form, review the pre-populated information and make any changes as needed. For more information about these fields, see Submit a support request from the Support page below.

  5. Complete any empty fields, including adding an issue title and description.

  6. Click Submit support request.

Submit a support request from the Support page​

Replicated calculates support severity based on customer license type, your Replicated plan, the affected product, and other factors. Your answers to the support request form generate a severity label on the GitHub issue and can page an engineer for high severity incidents.

To submit a support request:

  1. In the Vendor Portal, go to Support.

  2. Select the product area related to your request.

  3. On the self-service page, review the suggested resources. If you still need help, click Open a support request.

    note

    You can click View open issues and requests on the self-service page to see all issues and feature requests in your Replicated collab repository in GitHub.

  4. (KOTS, Embedded Cluster, and kURL only) Upload one or more support bundles. The Vendor Portal uses support bundle metadata to pre-populate customer information in the request form.

  5. Complete the support request form:

    FieldDescription
    First Name, Last Name, and GitHub Username

    These fields are only displayed if you haven't added a GitHub username to your Vendor Portal account. Your GitHub username is required to access the GitHub collab repo used for support tickets.

    Customer Name

    Search for the name of the customer associated with this support request. This field is available if you uploaded a support bundle in the previous step, or when customer information is available from the application context.

    Choosing a customer is required to enable some SLA levels that are specific to paid licenses.

    Issue Title

    (Required) The issue title on GitHub.

    Problem Description

    (Required) A description of the issue or problem.

    Issue Impact

    (Required) The impact level of the issue. The available options vary by product:

    • KOTS, kURL, Embedded Cluster, and Native Scheduler: Issue in paid production environment, Issue in non-production environment, Any other question
    • Compatibility Matrix: Resources are entirely unavailable, A feature or resource is degraded, Any other question
    • Helm CLI: Production issue with SDK Microservice, Production issue with Helm install, Non-production issue, Any other question
    • Vendor Portal: SaaS Service inoperative, SaaS Service/Feature degraded, Any other question

  6. If you selected a high-severity impact level (such as a production or service-inoperative issue), answer the additional assessment questions:

    FieldDescription
    Is this issue currently preventing you from using the product in production?

    Indicates whether business-critical functionality is completely unavailable.

    Has this been reproduced in a different installation/environment?

    Indicates whether the issue has been confirmed in more than one environment. If the issue is both blocking production and reproducible, the request may be escalated to Severity 1.

    Is this blocking a production release of the product?

    (Compatibility Matrix only) Displayed when the impact level is "Resources are entirely unavailable". Indicates whether the issue is blocking a production release.

    Select Cluster/VM

    (Compatibility Matrix only) Optionally select a cluster or VM from your recent Compatibility Matrix history to associate with the request.

  7. Click Submit Request.

    If the severity calculation results in a Severity 1 (critical) issue, the Vendor Portal displays a confirmation dialog that informs you that an on-call engineer will be paged. From this dialog, you can choose to:

    • Go back and edit the request details
    • Continue and submit as Severity 2 without paging an engineer
    • Continue and submit as Severity 1, which pages an on-call engineer

    After you submit the support request, you receive a link to your support issue where you can interact with the support team.

Submit a feature request​

You can submit feature requests to share ideas for new features or improvements to Replicated products.

To submit a feature request:

  1. In the Vendor Portal, go to Support.

  2. Select the product area related to your request.

  3. On the self-service page, click Make a feature request.

    note

    You can click View open issues and requests on the self-service page to see all issues and feature requests in your Replicated collab repository in GitHub.

  4. Complete the feature request form:

    FieldDescription
    Request Title

    (Required) A short title for your feature request.

    What is the problem you're trying to solve?

    (Required) Describe the problem or use case that this feature would address.

    Do you have a proposed product change that would solve this problem?

    (Optional) Describe any specific product changes or solutions you have in mind.

  5. Click Submit Request.

    After you submit the feature request, Replicated creates an issue in your team's collab repository on GitHub.

Provide support bundles to Replicated after opening a support request​

You can attach new support bundles to existing support issues when conditions change or new problems arise. This helps the Replicated support team troubleshoot the issue more quickly.

note

Replicated recommends uploading support bundles through the Vendor Portal rather than uploading bundles to the issue in Github directly. Many support bundles will exceed the Github size limits for file uploads. Additionally, the Vendor Portal provides insights and analysis for uploaded bundles that are beneficial for the support process.

After you open a support request, you can do the following to share additional support bundles with Replicated:

  • Go to the Troubleshoot tab and click Add support bundle > Upload support bundle. In the Upload a support bundle dialog, select any open support issue to attach the bundle to that issue.

    Upload a support bundle dialog

    View a larger version of this image

  • Go to any Customer page and select the Support bundles tab. Click Add support bundle > Upload support bundle. In the Upload a support bundle dialog, select any open support issue to attach the bundle to that issue.

  • From the Support Bundle Analysis page for a bundle, click Share with Replicated to allow Replicated support engineers to be able to access the bundle. Then, copy the support bundle URL directly from the address bar in your browser and share the link in the open support issue. The support bundle URL is in the format: https://vendor.replicated.com/troubleshoot/analyze/2024-08-07@22:10.

    note

    You do not need to click Share with Replicated to share support bundles URLs internally with members of your Vendor Portal team.

On this page