You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
defaultDateFormat is now deprecated. There is a newer defaultDateFormats object array that allows for specifying multiple timestamp formats and this is defaultDateFormats
It should be possible to create a source using the cookbook containing one or more date formats in defaultDateFormats
Actual Behavior
new attribute is missing from possible configuration options
Steps to Reproduce
defaultDateFormats doesn't exist as a possible attribute yet
@rickjuryxero can you point me to what version it was deprecated? Hopefully we can write something to be backwards compatible by inspecting the version. If not we can do a major release where we can have breaking changes.
I only found out about this after logging a case with sumo support about a source where we were having problems with auto timestamping (and previously you could only define a single manual timesstamp). The timestamping happens on the cloud side, so it doesn't seem to be tied to a particular agent version. I believe the change was fairly recent (like sometime 2018) but I'm not sure.
Environment Information
Please include the following:
sumo_source_local_file in my use case, but it would affect any json source type.
Expected Behavior
as per: https://help.sumologic.com/Send-Data/Sources/03Use-JSON-to-Configure-Sources
defaultDateFormat is now deprecated. There is a newer defaultDateFormats object array that allows for specifying multiple timestamp formats and this is defaultDateFormats
It should be possible to create a source using the cookbook containing one or more date formats in defaultDateFormats
Actual Behavior
new attribute is missing from possible configuration options
Steps to Reproduce
defaultDateFormats doesn't exist as a possible attribute yet
Important Factoids
none
References
https://help.sumologic.com/Send-Data/Sources/03Use-JSON-to-Configure-Sources
The text was updated successfully, but these errors were encountered: