- Functionbeat Reference:
- Functionbeat overview
- Quick start: installation and configuration
- Set up and deploy
- Configure
- AWS functions
- General settings
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- append
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- rate_limit
- registered_domain
- rename
- replace
- syslog
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- Regular expression support
- Instrumentation
- functionbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Understand logged metrics
- Common problems
- Deployment to AWS fails with "failed to create the stack"
- Deployment to AWS fails with "resource limit exceeded"
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- High RSS memory usage due to MADV settings
Deployment to AWS fails with "resource limit exceeded"
editDeployment to AWS fails with "resource limit exceeded"
editDeployment fails with the following message if you attempt to deploy a Lambda function that reads from a CloudWatch log group that already has a subscription filter defined on it:
CREATE_FAILED, ResourceStatusReason: Resource limit exceeded
The AWS limit on subscription filters is one per log group. If you’ve already deployed a Lambda function that monitors the log group, even if you deleted the function, the filter subscription might still exist.
To resolve this issue, use the AWS logs
describe-subscription-filters
command on the log group. For example, if you’re using the AWS CLI, run:
aws logs describe-subscription-filters --log-group-name /aws/lambda/hello-world-python
The output will look something like:
{ "subscriptionFilters": [ { "filterPattern": "", "filterName": "fnb-cloudwatch-stack-fnbcloudwatch3SFawslambdahelloworldpython-11WH0BC1BM1NP", "creationTime": 1565194872642, "logGroupName": "/aws/lambda/hello-world-python", "destinationArn": "arn:aws:lambda:us-east-2:551009506772:function:cloudwatch", "distribution": "ByLogStream" } ] }
If you’re no longer using the subscription filter, you can use the AWS logs
delete-subscription-filter
command to delete it. For example:
aws logs delete-subscription-filter --log-group-name /aws/lambda/hello-world-python --filter-name fnb-cloudwatch-stack-fnbcloudwatch3SFawslambdahelloworldpython-11WH0BC1BM1NP
Before attempting to redeploy the function, you might need to go to the CloudFormation console in AWS and delete the stack that Functionbeat created for the failed deployment.