-
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
feat: Openstack input plugin #9236
Conversation
Thanks @singamSrikar. We'll get a review on this PR. |
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.
Looks good to me. Thanks @singamSrikar for the contribution. The only issue I see is the missing tests, but given the code I guess it is not easily possible to mock some stack responses, is it?
yeah, that is right. There are few applications which can mock the Openstack APIs but that would be an additional dependency. |
@singamSrikar TBH I think the additional dependency is well spent. Can you please add such a test-case as it will probably trap changes in telegraf that might break this plugin and eases the live of all other devs. |
Oh and we do have linter warnings again... :-S |
I have checked the Openstack api mimic but looks like it doesn't have latest api version support, which we are using, and it requires us to run a system level service with ports enabled to mimic. |
Is there a docker container for this mockup? If so, we should add a test-case in non-short mode. Take a look at e.g. https://github.com/influxdata/telegraf/blob/master/plugins/inputs/sql/sql_test.go on how to do it. |
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.
Please fix the linter warnings.
I have checked but there is no mockup that would work here. |
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.
Looks good to me. Unfortunately, we have to live without tests as there seems to be no mockup...
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.
Thank for this! This is great.
I do want the warning about cardinality/# of tags to be more prominent in the readme. can you update that with my items and then look at my other comment about status?
Thanks!
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.
Almost there :)
📦 Looks like new artifacts were built from this PR. Expand this list to get them here! 🐯Artifact URLs |
Hey @powersj, I have added the changes as suggested to README doc, please take a look and let me know if any changes are required. |
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.
Happy when you are... ;-)
I can't help but feel like a nod to the original author of a large part of this plugin, @spjmurray, would've been the right thing to do here - especially since he unsuccessfully attempted to shepherd the original PR for several years before eventually giving up due to lack of traction on the InfluxData side. |
Hey @yankcrime, I'm sorry for this lurking around so long (though I'm not with InfluxData). As you might have noticed I tried to reactivate the "old" PR, but unfortunately the original author did not react on any of my attempts. This PR was linked to the original one and I really appreciate the work @spjmurray put into this, but I have no means to reach him beside Github comments... |
added openstack input plugin to gather metrics from openstack services
Required for all PRs:
Wrote appropriate unit tests.resolves #243