Commit ad24346b authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'doc-integration-elasticsearch-mention-logs' into 'master'

Mention logs in Elasticsearch integration troubleshooting

See merge request gitlab-org/gitlab!48100
parents 2c2404b9 8337cfc9
...@@ -761,6 +761,17 @@ However, some larger installations may wish to tune the merge policy settings: ...@@ -761,6 +761,17 @@ However, some larger installations may wish to tune the merge policy settings:
## Troubleshooting ## Troubleshooting
One of the most valuable tools for identifying issues with the Elasticsearch
integration will be logs. The most relevant logs for this integration are:
1. [`sidekiq.log`](../administration/logs.md#sidekiqlog) - All of the
indexing happens in Sidekiq, so much of the relevant logs for the
Elasticsearch integration can be found in this file.
1. [`elasticsearch.log`](../administration/logs.md#elasticsearchlog) - There
are additional logs specific to Elasticsearch that are sent to this file
that may contain useful diagnostic information about searching,
indexing or migrations.
Here are some common pitfalls and how to overcome them. Here are some common pitfalls and how to overcome them.
### How can I verify that my GitLab instance is using Elasticsearch? ### How can I verify that my GitLab instance is using Elasticsearch?
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment