Commit da58d992 authored by Daphne Kua's avatar Daphne Kua
Browse files

Clarify DHR log availability and link to troubleshooting runbook

parent 12ee07cd

content/handbook/support/workflows/dedicated_runners.md

+6 −3
Original line number Diff line number Diff line
@@ -21,7 +21,9 @@ To identify if a customer is using Hosted Runners, use Switchboard. 
`gitlab-runner` and `systemd` logs are available in OpenSearch

alongside the [GitLab Dedicated application logs](dedicated_logs.html).



To view on Runner-related logs only:

CI job logs are **not** captured in OpenSearch. For job logs, reach out to the customer directly.



To view Runner-related logs only:



1. Filter generally with `fluentd_tag:cloudwatch.*`

2. Obtain the more exact `fluentd_tag:cloudwatch.<name>-fleeting-logs`,
@@ -29,9 +31,10 @@ To view on Runner-related logs only: 
   The `<name>` is a customer-specific value (attribute of **CommonProperties** on

   [Runner Model](https://gitlab-com.gitlab.io/gl-infra/gitlab-dedicated/runner-model-schema/)),

   but is not yet available in Switchboard.

3. Using that same prefix based on `cloudwatch.<name>` `manager-logs` are available as well.

3. Using that same prefix based on `cloudwatch.<name>`, `manager-logs` are available as well.



For job logs reach out to the customer.

For additional troubleshooting guidance from the Dedicated Hosted Runner team, refer to the

[Hosted Runners troubleshooting runbook](https://gitlab-com.gitlab.io/gl-infra/gitlab-dedicated/team/runbooks/hosted-runners-troubleshooting.html#accessing-logs-in-opensearch).



## Monitoring