docs: Add section in troubleshooting for timeout errors (504, context cancelled, error processing requests)

[gmintoco]

We had many issues with configuring timeout errors. The main kicker for us was the Timeout between the Grafana client and the Grafana interface (nothing to do with Loki). This PR adds a small section to the troubleshooting guide to mention some potential causes of timeout errors and where you should look to resolve them.

What this PR does / why we need it:

This PR extends the documentation and would have assisted us with a problem we were having.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist

• Documentation added
• Tests updated
• Add an entry in the CHANGELOG.md about the changes.

[CLAassistant]

All committers have signed the CLA.

[kavirajk]

Thanks @gmintoco for the PR. 👍

LGTM. suggested few minor things.

[kavirajk]

Leave it to @KMiller-Grafana for final review.

[stale]

Hi! This issue has been automatically marked as stale because it has not had any
activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project.
A stalebot can be very useful in closing issues in a number of cases; the most common
is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

• Mark issues as revivable if we think it's a valid issue but isn't something we are likely
  to prioritize in the future (the issue will still remain closed).
• Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task,
our sincere apologies if you find yourself at the mercy of the stalebot.

[gmintoco]

@kavirajk could this one please be reopened?

[gmintoco]

@KMiller-Grafana any chance of a reopen and review?

[KMiller-Grafana]

The file you've added to, @gmintoco, has changed locations. I'm going to leave this PR closed, and re-implement this PR with your name added.

[gmintoco]

Still relevant

…

On Mon, 25 Apr 2022 at 5:24 pm, stale[bot] ***@***.***> wrote: Hi! This issue has been automatically marked as stale because it has not had any activity in the past 30 days. We use a stalebot among other tools to help manage the state of issues in this project. A stalebot can be very useful in closing issues in a number of cases; the most common is closing issues or PRs where the original reporter has not responded. Stalebots are also emotionless and cruel and can close issues which are still very relevant. *If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.* We regularly sort for closed issues which have a stale label sorted by thumbs up. We may also: - Mark issues as revivable if we think it's a valid issue but isn't something we are likely to prioritize in the future (the issue will still remain closed). - Add a keepalive label to silence the stalebot if the issue is very common/popular/important. We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task, our sincere apologies if you find yourself at the mercy of the stalebot. — Reply to this email directly, view it on GitHub <#5649 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMCHXCANDSJA3J5UOHVIEB3VGZCEFANCNFSM5Q5XWODQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>