Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@jbau
Copy link
Contributor

@jbau jbau commented Aug 28, 2015

@panghy

Trying again

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we really need to time regex speeds :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is just in case there's something ridiculous (Sam was a bit worried that we couldn't predict the compute expense of the regex that the customer supplies)

(But probably the metric machinery might be as expensive as the regex =P, so I could take it out if you want )

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the timer is efficient but not free. If they have a problem, I think we can just ask them to give us the regex and we'd know (probably right away) whether it's a problem or not. Tracking every call seems a bit heavy.

@jbau jbau force-pushed the jbau/new/validation-regex branch from ff1c1d7 to e83487b Compare August 28, 2015 02:20
@jbau
Copy link
Contributor Author

jbau commented Aug 28, 2015

repushed

panghy added a commit that referenced this pull request Aug 31, 2015
Add hooks for blacklist/whitelist regexs for graphite listener
@panghy panghy merged commit d5d887b into wavefrontHQ:master Aug 31, 2015
sbhakta-vmware added a commit that referenced this pull request Sep 7, 2022
jk892689 pushed a commit that referenced this pull request Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants