Merge branch 'master' into ml_file_upload

Author: kibanamachine

docs/apm/images/apm-services-overview.png

@@ -17,8 +17,8 @@ Response times for the service. You can filter the *Latency* chart to display th
 image::apm/images/latency.png[Service latency]
 
 [discrete]
-[[service-traffic-transactions]]
-=== Traffic and transactions
+[[service-throughput-transactions]]
+=== Throughput and transactions
 
 The *Throughput* chart visualizes the average number of transactions per minute for the selected service.
 
@@ -62,6 +62,9 @@ each dependency. By default, dependencies are sorted by _Impact_ to show the mos
 If there is a particular dependency you are interested in, click *View service map* to view the related
 <<service-maps, service map>>.
 
+IMPORTANT: A known issue prevents Real User Monitoring (RUM) dependencies from being shown in the
+*Dependencies* table. We are working on a fix for this issue.
+
 [role="screenshot"]
 image::apm/images/spans-dependencies.png[Span type duration and dependencies]
 

docs/apm/images/apm-traces.png

@@ -17,10 +17,10 @@ If there's a weird spike that you'd like to investigate,
 you can simply zoom in on the graph - this will adjust the specific time range,
 and all of the data on the page will update accordingly.
 
-*Transactions per minute*::
-Visualize response codes: `2xx`, `3xx`, `4xx`, etc.,
-and is useful for determining if you're serving more of one code than you typically do.
-Like in the Transaction duration graph, you can zoom in on anomalies to further investigate them.
+*Throughput*::
+Visualize response codes: `2xx`, `3xx`, `4xx`, etc.
+Useful for determining if more responses than usual are being served with a particular response code.
+Like in the latency graph, you can zoom in on anomalies to further investigate them.
 
 *Error rate*::
 Visualize the total number of transactions with errors divided by the total number of transactions.
@@ -157,4 +157,4 @@ and solve problems.
 [role="screenshot"]
 image::apm/images/apm-logs-tab.png[APM logs tab]
 
-// To do: link to log correlation
+// To do: link to log correlation

docs/apm/images/apm-transactions-overview.png

@@ -1,14 +1,30 @@
 [[troubleshooting]]
-== Troubleshoot common problems
+== Troubleshooting
 
 ++++
 <titleabbrev>Troubleshooting</titleabbrev>
 ++++
 
-If you have something to add to this section, please consider creating a pull request with
-your proposed changes at https://github.com/elastic/kibana.
-
-Also, check out the https://discuss.elastic.co/c/apm[APM discussion forum].
+This section describes common problems you might encounter with the APM app.
+To add to this page, please consider opening a
+https://github.com/elastic/kibana/pulls[pull request] with your proposed changes.
+
+If your issue is potentially related to other components of the APM ecosystem,
+don't forget to check our other troubleshooting guides or discussion forum:
+
+* {apm-server-ref}/troubleshooting.html[APM Server troubleshooting]
+* {apm-dotnet-ref}/troubleshooting.html[.NET agent troubleshooting]
+* {apm-go-ref}/troubleshooting.html[Go agent troubleshooting]
+* {apm-java-ref}/trouble-shooting.html[Java agent troubleshooting]
+* {apm-node-ref}/troubleshooting.html[Node.js agent troubleshooting]
+* {apm-py-ref}/troubleshooting.html[Python agent troubleshooting]
+* {apm-ruby-ref}/debugging.html[Ruby agent troubleshooting]
+* {apm-rum-ref/troubleshooting.html[RUM troubleshooting]
+* https://discuss.elastic.co/c/apm[APM discussion forum].
+
+[discrete]
+[[troubleshooting-apm-app]]
+== Troubleshoot common APM app problems
 
 * <<no-apm-data-found>>
 * <<troubleshooting-too-many-transactions>>

docs/apm/images/traffic-transactions.png

@@ -9,7 +9,7 @@ Configuration options to be used to create a [cluster client](./kibana-plugin-co
 <b>Signature:</b>
 
 ```typescript
-export declare type ElasticsearchClientConfig = Pick<ElasticsearchConfig, 'customHeaders' | 'logQueries' | 'sniffOnStart' | 'sniffOnConnectionFault' | 'requestHeadersWhitelist' | 'sniffInterval' | 'hosts' | 'username' | 'password'> & {
+export declare type ElasticsearchClientConfig = Pick<ElasticsearchConfig, 'customHeaders' | 'sniffOnStart' | 'sniffOnConnectionFault' | 'requestHeadersWhitelist' | 'sniffInterval' | 'hosts' | 'username' | 'password'> & {
     pingTimeout?: ElasticsearchConfig['pingTimeout'] | ClientOptions['pingTimeout'];
     requestTimeout?: ElasticsearchConfig['requestTimeout'] | ClientOptions['requestTimeout'];
     ssl?: Partial<ElasticsearchConfig['ssl']>;

docs/apm/service-overview.asciidoc

@@ -27,7 +27,6 @@ export declare class ElasticsearchConfig
 |  [healthCheckDelay](./kibana-plugin-core-server.elasticsearchconfig.healthcheckdelay.md) |  | <code>Duration</code> | The interval between health check requests Kibana sends to the Elasticsearch. |
 |  [hosts](./kibana-plugin-core-server.elasticsearchconfig.hosts.md) |  | <code>string[]</code> | Hosts that the client will connect to. If sniffing is enabled, this list will be used as seeds to discover the rest of your cluster. |
 |  [ignoreVersionMismatch](./kibana-plugin-core-server.elasticsearchconfig.ignoreversionmismatch.md) |  | <code>boolean</code> | Whether to allow kibana to connect to a non-compatible elasticsearch node. |
-|  [logQueries](./kibana-plugin-core-server.elasticsearchconfig.logqueries.md) |  | <code>boolean</code> | Specifies whether all queries to the client should be logged (status code, method, query etc.). |
 |  [password](./kibana-plugin-core-server.elasticsearchconfig.password.md) |  | <code>string</code> | If Elasticsearch is protected with basic authentication, this setting provides the password that the Kibana server uses to perform its administrative functions. |
 |  [pingTimeout](./kibana-plugin-core-server.elasticsearchconfig.pingtimeout.md) |  | <code>Duration</code> | Timeout after which PING HTTP request will be aborted and retried. |
 |  [requestHeadersWhitelist](./kibana-plugin-core-server.elasticsearchconfig.requestheaderswhitelist.md) |  | <code>string[]</code> | List of Kibana client-side headers to send to Elasticsearch when request scoped cluster client is used. If this is an empty array then \*no\* client-side will be sent. |