You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/aws-firehose/aws-firehose-troubleshooting.asciidoc
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ You can use the monitoring tab in the Firehose console to ensure there are incom
13
13
[role="screenshot"]
14
14
image::images/firehose-monitoring.png[Firehose monitoring page showing some charts of delivery success percentage and throughput]
15
15
16
-
By default Firehose also logs to a Cloudwatch log group with the name `/aws/kinesisfirehose/<delivery stream name>`, which is automatically created when the delivery stream is created.
16
+
By default Firehose also logs to a Cloudwatch log group with the name `/aws/kinesisfirehose/<delivery stream name>`, which is automatically created when the delivery stream is created.
17
17
Two log streams, `DestinationDelivery` and `BackupDelivery`, are created in this log group.
18
18
19
19
The backup settings in the delivery stream specify how failed delivery requests are handled.
@@ -23,7 +23,7 @@ See <<aws-firehose-config-backup-settings>> for details on configuring backups t
23
23
[[aws-firehose-scaling]]
24
24
== Scaling
25
25
Firehose can https://docs.aws.amazon.com/firehose/latest/dev/limits.html[automatically scale] to handle very high throughput.
26
-
If your Elastic deployment is not properly configured for the data volume coming from Firehose, it could cause a bottleneck, which may lead to increased ingest times or indexing failures.
26
+
If your Elastic deployment is not properly configured for the data volume coming from Firehose, it could cause a bottleneck, which may lead to increased ingest times or indexing failures.
27
27
28
28
There are several facets to optimizing the underlying Elasticsearch performance, but Elastic Cloud provides several ready-to-use hardware profiles which can provide a good starting point.
29
29
Other factors which can impact performance are https://www.elastic.co/guide/en/elasticsearch/reference/current/size-your-shards.html[shard sizing], https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-indexing-speed.html[indexing configuration], and https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html[index lifecycle management (ILM)].
@@ -32,5 +32,5 @@ Other factors which can impact performance are https://www.elastic.co/guide/en/e
32
32
[[aws-firehose-support]]
33
33
== Support
34
34
35
-
If you encounter further problems, please contact Elastic support by following the instructions https://www.elastic.co/guide/en/welcome-to-elastic/current/get-support-help.html[here].
35
+
If you encounter further problems, please contact Elastic support by following the instructions {estc-welcome-current}/get-support-help.html[here].
0 commit comments