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
You can view the status of deployment actions and get additional information on events, including why a particular event fails e.g. misconfiguration details.
15
16
@@ -22,20 +23,19 @@ For example, if you don’t increase the visibility timeout for an SQS queue as
It is important to monitor the Elastic Serverless Forwarder Lambda function for timeouts to prevent unexpected costs. You can use the [AWS Lambda integration](https://docs.elastic.co/en/integrations/aws/lambda) for this. If the timeouts are constant, you should throttle the Lambda function to stop its execution before proceeding with any troubleshooting steps. In most cases, constant timeouts will cause the records and messages from the event triggers to go back to their sources and trigger the function again, which will cause further timeouts and force a loop that will incure unexpected high costs. For more information on throttling Lambda functions, refer to [AWS docs](https://docs.aws.amazon.com/lambda/latest/operatorguide/throttling.md).
28
29
29
30
30
-
###Increase debug information [_increase_debug_information]
31
+
## Increase debug information [_increase_debug_information]
31
32
32
33
To help with debugging, you can increase the amount of logging detail by adding an environment variable as follows:
33
34
34
35
1. Select the serverless forwarder **application** from **Lambda > Functions**
35
36
2. Click **Configuration** and select **Environment Variables** and choose **Edit**
36
37
3. Click **Add environment variable** and enter `LOG_LEVEL` as **Key*** and `DEBUG` as ***Value** and click **Save**
37
38
38
-
39
39
## Using the Event ID format (version 1.6.0 and above) [aws-serverless-troubleshooting-event-id-format]
40
40
41
41
Version 1.6.0 introduces a new event ID format that prevents duplicate ID errors when a high volume of events is ingested to {{es}}. This new format combines a timestamp with data specific to the relevant AWS resource, extracted from the AWS Lambda event received by the forwarder.
@@ -46,7 +46,7 @@ The timestamp is used as a prefix for the ID, because identifiers that gradually
46
46
If old events that are already published to {{es}} using a version of Elastic Serverless Forwarder before v1.6.0 are ingested again, they will be treated as new events and published to {{es}} as duplicates.
# Check Serverless status and get updates [general-serverless-status]
8
+
9
+
Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.
10
+
11
+
To check current and past service availability, go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
12
+
13
+
14
+
## Subscribe to updates [general-serverless-status-subscribe-to-updates]
15
+
16
+
You can be notified about changes to the service status automatically.
17
+
18
+
To receive service status updates:
19
+
20
+
1. Go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
21
+
2. Select **SUBSCRIBE TO UPDATES**.
22
+
3. You can be notified in the following ways:
23
+
24
+
* Email
25
+
* Slack
26
+
* Atom or RSS feeds
27
+
28
+
29
+
After you subscribe, you’ll be notified whenever a service status update is posted.
# Check Serverless status and get updates [general-serverless-status]
5
+
# Troubleshoot {{serverless-full}}
7
6
8
-
Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.
7
+
Use the topics in this section to troubleshoot {{serverless-full}}:
9
8
10
-
To check current and past service availability, go to the Elastic [service status](https://status.elastic.co/?section=serverless) page.
0 commit comments