Elasticsearch is _not_ included in the Omnibus packages. You will have to
Elasticsearch is _not_ included in the Omnibus packages. You will have to
[install it yourself](https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html"Elasticsearch installation documentation")
[install it yourself](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/install-elasticsearch.html"Elasticsearch 6.8 installation documentation")
whether you are using the Omnibus package or installed GitLab from source.
whether you are using the Omnibus package or installed GitLab from source.
Providing detailed information on installing Elasticsearch is out of the scope
Providing detailed information on installing Elasticsearch is out of the scope
of this document.
of this document.
NOTE: **Note:**
NOTE: **Note:**
Elasticsearch should be installed on a separate server, whether you install
Elasticsearch should be installed on a separate server, whether you install
it yourself or by using the
it yourself or use a cloud hosted offering like Elastic's [Elasticsearch Service](https://www.elastic.co/products/elasticsearch/service)(available on AWS, GCP, or Azure) or the
[Amazon Elasticsearch](http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-gsg.html) service. Running Elasticsearch on the same server as GitLab is not recommended
service. Running Elasticsearch on the same server as GitLab is not recommended
and will likely cause a degradation in GitLab instance performance.
and it will likely cause performance degradation on the GitLab installation.
NOTE: **Note:**
NOTE: **Note:**
**For a single node Elasticsearch cluster the functional cluster health status will be yellow** (will never be green) because the primary shard is allocated but replicas can not be as there is no other node to which Elasticsearch can assign a replica.
**For a single node Elasticsearch cluster the functional cluster health status will be yellow** (will never be green) because the primary shard is allocated but replicas can not be as there is no other node to which Elasticsearch can assign a replica.
@@ -138,7 +138,7 @@ configured or there was an error reporting the status via the API.
...
@@ -138,7 +138,7 @@ configured or there was an error reporting the status via the API.
### Merge Request event does not trigger a Jenkins Pipeline
### Merge Request event does not trigger a Jenkins Pipeline
Check the `/var/log/gitlab/gitlab-rails/production.log` file for messages like:
Check [service hook logs](../user/project/integrations/project_services.md#troubleshooting-project-services) for request failures or check the `/var/log/gitlab/gitlab-rails/production.log` file for messages like:
| [Mattermost slash commands](mattermost_slash_commands.md) | Mattermost chat and ChatOps slash commands | No |
| [Mattermost Notifications](mattermost.md) | Receive event notifications in Mattermost |
| [Mattermost Notifications](mattermost.md) | Receive event notifications in Mattermost | No |
| [Microsoft teams](microsoft_teams.md) | Receive notifications for actions that happen on GitLab into a room on Microsoft Teams using Office 365 Connectors |
| [Microsoft teams](microsoft_teams.md) | Receive notifications for actions that happen on GitLab into a room on Microsoft Teams using Office 365 Connectors | No |
| Packagist | Update your project on Packagist, the main Composer repository |
| Packagist | Update your project on Packagist, the main Composer repository | Yes |
| Pipelines emails | Email the pipeline status to a list of recipients |
| Pipelines emails | Email the pipeline status to a list of recipients | No |
| [Slack Notifications](slack.md) | Send GitLab events (e.g. issue created) to Slack as notifications |
| [Slack Notifications](slack.md) | Send GitLab events (e.g. issue created) to Slack as notifications | No |
| [Slack slash commands](slack_slash_commands.md)**(CORE ONLY)** | Use slash commands in Slack to control GitLab |
| [Slack slash commands](slack_slash_commands.md)**(CORE ONLY)** | Use slash commands in Slack to control GitLab | No |
| [GitLab Slack application](gitlab_slack_application.md)**(FREE ONLY)** | Use Slack's official application |
| [GitLab Slack application](gitlab_slack_application.md)**(FREE ONLY)** | Use Slack's official application | No |
| [YouTrack](youtrack.md) | YouTrack issue tracker | No |
## Push hooks limit
## Push hooks limit
...
@@ -74,6 +74,25 @@ your liking which will then be pre-filled on each project's Service.
...
@@ -74,6 +74,25 @@ your liking which will then be pre-filled on each project's Service.
Read more about [Services templates in this document](services_templates.md).
Read more about [Services templates in this document](services_templates.md).
## Troubleshooting project services
Some project services use service hooks for integration with external applications. To confirm which ones use service hooks, see the [services table](#services). GitLab stores details of service hook requests made within the last 2 days. To view details of the requests, go to the service's configuration page.
The **Recent Deliveries** section lists the details of each request made within the last 2 days:
- HTTP status code (green for 200-299 codes, red for the others, `internal error` for failed deliveries)
- Triggered event
- URL to which the request was sent
- Elapsed time of the request
- Relative time in which the request was made
To view more information about the request's execution, click the respective **View details** link.
On the details page, you can see the data sent by GitLab (request headers and body) and the data received by GitLab (response headers and body).
From this page, you can repeat delivery with the same data by clicking **Resend Request**.
## Contributing to project services
## Contributing to project services
Because GitLab is open source we can ship with the code and tests for all
Because GitLab is open source we can ship with the code and tests for all
