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
When performing a SOAP call, it looks like %{+yyyy-MM-dd} for getting the currentDate in the body doesn't seem to work. I don't know whether this is expected behaviour or some sort of bug. Example below:
This is driving us mad. Would love this to be fixed as it makes the product useless for our need since we use the current date as part of our body to pull the current logs.
%{+YYYY-MM-dd} is an interpolation of a date and/or time - but the important part is to know which date is used. As this interpolation is used (and was designed) for creating a text with the date/time taken from the current event (so that, for example, events can be steered to different dated indexes) it uses the @timestamp field of the current event.
Because inputs generate events there is no event and @timestamp field to use to build the interpolation when the input config is compiled.
Because of this limitation, only some settings are interpolated and which ones those are is the decision of the plugin author. That is, one can't assume that all settings are interpolated.
One could argue that the interpolation should use Time.now() if an event is not available but this would be a new piece of code (for inputs to use) because now the sprintf method is defined on the Event class.
When performing a SOAP call, it looks like %{+yyyy-MM-dd} for getting the currentDate in the body doesn't seem to work. I don't know whether this is expected behaviour or some sort of bug. Example below:
The text was updated successfully, but these errors were encountered: