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.

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

Fix #871: Adjust aggregator-rules input_pattern match greediness #872

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

hessu
Copy link
Contributor

@hessu hessu commented Jan 13, 2020

... to support numeric matching after captured field. Fixes bug #871 .

Before, an input regexp of "collectd.mycluster-<location>\d+.app.requests" in aggregation-rules.conf, with a hostname of "mycluster-paris105" would capture "paris10" as the location, instead of paris. With a large cluster this would create a whole lot of aggregates, one per 10 nodes.

This patch makes the <location> match not greedy, letting the user-supplied \d+ side to be greedy and eat the 105 away fully, leaving "paris" as the location.

… greediness to support numeric matching after captured field
@piotr1212
Copy link
Member

@deniszh It seems that pyhash does not support py27 anymore which results in failing travis builds. We should drop py27-pyhash or pin pyhash to some older version.

@deniszh
Copy link
Member

deniszh commented Jan 14, 2020

@piotr1212 : I'm voting for drop, but pinning also OK for me.

@hessu : thanks for fix, LGTM!

@piotr1212 piotr1212 merged commit 526eeab into graphite-project:master Jan 15, 2020
deniszh added a commit that referenced this pull request Feb 29, 2020
…858_pr-858_pr-858_pr-874_pr-875_pr-880_pr-881_pr-882

[1.1.x] s390x support for travis (#869) | Fix #871: Adjust aggregator-rules input_pattern match greediness to support numeric matching after captured field (#872) | sanitize names when using them as tag value (#858) | sanitize names when us
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants