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

REGEXP_SNMP_TRIM does not handle Gauge fields properly #2474

Closed
fbellet opened this issue Mar 1, 2019 · 4 comments
Closed

REGEXP_SNMP_TRIM does not handle Gauge fields properly #2474

fbellet opened this issue Mar 1, 2019 · 4 comments
Labels
bug Undesired behaviour resolved A fixed issue
Milestone

Comments

@fbellet
Copy link

fbellet commented Mar 1, 2019

I think commit e9800f0 changed the REGEXP_SNMP_TRIM value in a way that now prevents it to correctly remove the "Gauge32:" prefix. Since this commit, "gauge" without ":" is matched, and "32" remains in the resulting string

@netniV netniV changed the title REGEXP_SNMP_TRIM issue REGEXP_SNMP_TRIM does not handle Gauge fields properly Mar 1, 2019
netniV added a commit that referenced this issue Mar 1, 2019
REGEXP_SNMP_TRIM does not handle Gauge fields properly
@netniV
Copy link
Member

netniV commented Mar 1, 2019

Thanks! Should be corrected in the latest development commit.

@netniV netniV added bug Undesired behaviour resolved A fixed issue labels Mar 1, 2019
@netniV netniV added this to the v1.2.3 milestone Mar 1, 2019
@fbellet
Copy link
Author

fbellet commented Mar 1, 2019

oups, it looks like a typo in commit a32dfb6: guage

@netniV
Copy link
Member

netniV commented Mar 1, 2019

💥

@netniV
Copy link
Member

netniV commented Mar 1, 2019

Looks fine to me

(in 86e2e33)

@cigamit cigamit closed this as completed Mar 3, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

3 participants