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

Adding support for sourcetype in Splunkmetric serializer and standardizing tags for other metadata fields #5504

Closed
wants to merge 3 commits into from

Conversation

dgshue
Copy link

@dgshue dgshue commented Feb 28, 2019

Required for all PRs:

Bugfix/5503

This will have impact on any previous config files as users will have to update their tags to reflect the new tag names. Other than that it's pretty straight forward. Welcome any feedback, first time contributor so bare with me.

  • Signed CLA.
  • Associated README.md updated.
  • Has appropriate unit tests.

@danielnelson
Copy link
Contributor

I think we should use the sourcetype tag but not rename any of the existing tags, this should fit in with the existing implementation without breaking anything. Alternately, I could see these as being configurable options on the parser:

data_format = "splunkmetric"
splunkmetric_sourcetype_tag = "splunkmetric_sourcetype"

@danielnelson danielnelson added the feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin label Feb 28, 2019
@ronnocol
Copy link
Contributor

I'm with @danielnelson here, breaking the existing configuration syntax could be significantly painful for people who have large telegraf deployments. I think just adding sourcetype as an overridable field and generally adopting #3362 should be sufficient to resolve the issue without requiring config changes.

There are Splunk based apps that are widely deployed that have the existing configuration schema included in them, I'm not saying it can't change, but it would first have to be deprecated before being removed.

@srebhan
Copy link
Member

srebhan commented Oct 28, 2021

@dgshue are you still interested in this PR?

@srebhan srebhan self-assigned this Oct 28, 2021
@srebhan srebhan added plugin/output 1. Request for new output plugins 2. Issues/PRs that are related to out plugins plugin/serializer and removed plugin/output 1. Request for new output plugins 2. Issues/PRs that are related to out plugins labels Oct 28, 2021
@srebhan
Copy link
Member

srebhan commented Dec 20, 2021

@dgshue any update?

@srebhan srebhan added the waiting for response waiting for response from contributor label Dec 20, 2021
@powersj
Copy link
Contributor

powersj commented Jan 24, 2022

Hi,

This PR has not been touched in a while and as a result I am going to close it. We are happy to review again once someone picks this back up with the suggested changes and rebased on master.

Thanks!

@powersj powersj closed this Jan 24, 2022
@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin plugin/serializer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants