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

Rationalize source and sourcetype #2

Closed
halr9000 opened this issue Sep 8, 2019 · 0 comments
Closed

Rationalize source and sourcetype #2

halr9000 opened this issue Sep 8, 2019 · 0 comments
Labels
enhancement New feature or request SmartApp

Comments

@halr9000
Copy link
Owner

halr9000 commented Sep 8, 2019

SmartThings events have a field named source (https://docs.smartthings.com/en/latest/ref-docs/event-ref.html#getsource). Currently, it is passed in to Splunk with the same name. However, looking at the data, I don’t really think it makes sense to do so. Instead, I would like to rename it spot something like “stSource”, and let source be the default based on how the data arrives at Splunk (probably HEC).

For sourcetype, there was not one specified prior to my fork. I made it “http:smartthings” at first, but now I realize I am trying to stuff source and sourcetype into one field. So I will make it simply “smartthings “.

@halr9000 halr9000 added enhancement New feature or request SmartApp labels Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request SmartApp
Projects
None yet
Development

No branches or pull requests

1 participant