-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Introduce a dedicated parser for prometheus #7778
Introduce a dedicated parser for prometheus #7778
Conversation
Since |
@danielnelson , sure. Done |
@danielnelson , Any chance to include it into 1.15? My team is looking forward to this functionality |
Sorry, we have missed the merge window for 1.15, it will have to go in 1.16. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a Telegraf user interested in this feature. I've left some comments, hope it helps you.
Just stumbled across this and thought I'd add a comment that we'd also find this useful. Thanks for doing the work. |
Just checking in on this. Anything missing that I might be able to help with? |
- Small correction - added full stop
Not saying this to put any pressure on this being merged but just wanted to report I've been running a build of telegraf with this change and am successfully reporting metrics using it. Thanks for doing the work. 👏 👏 👏 Thanks everyone for putting work in to both manage this project and submit PRs. |
@DmitrySenin it seems that there is conflict with |
db1563c
to
4fd2a00
Compare
This should get merged! |
closes: #4414
Required for all PRs:
Testing
Tested locally with the following configuration of input: