Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-2023

Add section to troubleshooting FAQ per driver with top SEO results

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Implementing
    • Unknown
    • Resolution: Unresolved
    • None
    • Docs
    • None
    • Needed
    • Hide

      Teams should review the links Rachelle included on each language team ticket and and add documentation pages for these common errors.

      Show
      Teams should review the links Rachelle included on each language team ticket and and add documentation pages for these common errors.

    Description

      Summary

      Users often get a stack trace/error message indicating a connectivity issue and then paste the text into Google looking for a solution.  Each month, various driver and language project tickets get thousands, or tens of thousands, of views via these searches, and users are forced into:

      • reading and understanding our previous comments, some of which are years old
      • playing detective in terms of which version of the driver the fix is available in (sometimes)
      • having advice that doesn't apply to their circumstance
      • seeing that we still haven't fixed the issue

      We should add documentation pages for the most common errors to our official documentation so that these searches are fruitful.

      Motivation

      Who is the affected end user?

      Application or operations engineers.

      How does this affect the end user?

      The hypothesis is that they are frustrated to not find the information they need.  They end up finding random Jira issues that don't have useful information, or that the information they find is outdated, or difficult to understand rather than a straightforward Q&A.

      How likely is it that this problem or use case will occur?

      It's an edge case, but not uncommon.  Google SEO is showing that our most "popular" Jira issues are for issues like this, e.g. JAVA-2895

      If the problem does occur, what are the consequences and how severe are they?

      Minor/major annoyance at a log message, misconfiguration, outdated knowledge of how drivers work, extra work/cognitive burden

      Is this issue urgent?

      No but it would be useful to our SEO to correct this problem

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      No

      Attachments

        Issue Links

          Activity

            People

              rachelle.palmer@mongodb.com Rachelle Palmer
              jeff.yemin@mongodb.com Jeffrey Yemin
              Jeffrey Yemin Jeffrey Yemin
              Rachelle Palmer Rachelle Palmer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: