-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Default timestamps for splunkhecexporter #965
Labels
enhancement
New feature or request
Comments
@nebffa When you say you are ingesting into Splunk, do you mean you are using the splunk HEC exporter? |
@keitwb yep - I am using the splunk HEC exporter |
nebffa
changed the title
Default timestamps for signalfx receiver
Default timestamps for splunkhecexporter
Oct 25, 2020
@nebffa Is this issue now resolved? OK to close? |
@atoulme yes this issue is now resolved. I suppose I can close it with this comment? Let me try... |
codeboten
pushed a commit
that referenced
this issue
Nov 23, 2022
codeboten
pushed a commit
that referenced
this issue
Nov 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Metrics sent to the Splunk HEC in some cases have a timestamp of 0 - Splunk accepts these timestamps without modification and consequently it is impossible to analyse these metrics meaningfully.
Describe the solution you'd like
In the case of metrics that have a 'zero' timestamp (i.e. beginning of Unix Epoch time), omit the timestamp field so that Splunk automatically sets it at ingestion time.
Describe alternatives you've considered
Splunk has options available to override the timestamps (https://docs.splunk.com/Documentation/Splunk/8.0.6/Data/Configuretimestamprecognition) in events, but despite repeated attempts these options have not worked. I think it's something special related to the way the HEC itself works.
Additional context
An example SignalFx Smart Agent monitor that publishes metrics without timestamps is https://docs.signalfx.com/en/latest/integrations/agent/monitors/telegraf-win_services.html, which is how I uncovered this behaviour.
The text was updated successfully, but these errors were encountered: