Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Functionbeat failing to deploy due to Alphanumeric Error #9420

Closed
musayev-io opened this issue Dec 6, 2018 · 3 comments
Closed

Functionbeat failing to deploy due to Alphanumeric Error #9420

musayev-io opened this issue Dec 6, 2018 · 3 comments
Assignees
@ph
Labels
bug Functionbeat

Comments

@musayev-io
Copy link

Summary

Looking at the CloudFormation resource that Functionbeat creates from the functionbeat.yml, the dashes get converted to "" but the underscores remain underscores, causing the ValidationError.

  • Version: functionbeat-6.5.2-darwin-x86_64
  • Operating System: MacOS High Sierra 10.13.6
  • Discuss Forum Post
  • Steps to Reproduce: Deploy a CloudWatch function with triggers to log groups that contain underscores in the name
@ph ph self-assigned this Dec 12, 2018
@musayev-io
Copy link
Author

Hey guys! Just wanted to check up and see if there was any timeline for this bug to get fixed. We're evaluating Lambda monitoring solutions and would hate to disqualify ELK because we couldn't set it up.

Thanks!!

@ph ph mentioned this issue Jan 15, 2019
Merged
ph added a commit to ph/beats that referenced this issue Jan 16, 2019
@ph
Instead of blacklisting chars in the resource name for cloudformation
07410d7 
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
@ph ph closed this as completed in #10087 Jan 16, 2019
ph added a commit that referenced this issue Jan 16, 2019
@ph
Instead of blacklisting chars in the resource name for cloudformation…
56c6857 
… use whitelisting. (#10087)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: #9420
@ph ph mentioned this issue Jan 16, 2019
Merged
ph added a commit to ph/beats that referenced this issue Jan 16, 2019
@ph
Instead of blacklisting chars in the resource name for cloudformation…
56bbdd5 
… use whitelisting. (elastic#10087)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
(cherry picked from commit 56c6857)
@ph ph mentioned this issue Jan 16, 2019
Merged
ph added a commit to ph/beats that referenced this issue Jan 18, 2019
@ph
Instead of blacklisting chars in the resource name for cloudformation…
9c635c0 
… use whitelisting. (elastic#10087)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
(cherry picked from commit 56c6857)
ph added a commit that referenced this issue Jan 21, 2019
@ph
Instead of blacklisting chars in the resource name for cloudformation…
fdbfb10 
… use whitelisting. (#10087) (#10120)

* Instead of blacklisting chars in the resource name for cloudformation
use whitelisting.

Only [a-zA-Z0-9] are permitted as resource name

Fixes: #9420
(cherry picked from commit 56c6857)
ph added a commit that referenced this issue Jan 21, 2019
@ph
Cherry-pick #10087 to 6.6: Instead of blacklisting chars in the resou…
a065bc3 
…rce name for cloudformation use whitelisting. (#10121)

Cherry-pick of PR #10087 to 6.6 branch. Original message: 

Only [a-zA-Z0-9] are permitted as resource name

Fixes: #9420
@PosicubeBeege
Copy link

When can we expect a release with this merge? Just so I know when to come back to adding our AWS logs (all using _ as word delimiters) into our new ELK setup. Thanks!

@musayev-io
Copy link
Author

According to Elastic, this fix will be part of the 6.6.1 release which is targeted sometime between 2/12/19- 2/22/19.

leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
@ph
Cherry-pick elastic#10087 to 6.6: Instead of blacklisting chars in th…
927c6b8 
…e resource name for cloudformation use whitelisting. (elastic#10121)

Cherry-pick of PR elastic#10087 to 6.6 branch. Original message: 

Only [a-zA-Z0-9] are permitted as resource name

Fixes: elastic#9420
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ph ph

Labels
bug Functionbeat
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ph @musayev-io @PosicubeBeege