Yes, I have order by that field too, so then it will not import anymore data since the rising_column will be the last date in your selection.
No, it will automatically be replaced with the last value of DATE_FIELD returned from the result set.
... View more
Should be ok, splunk simply sends the query at the database and takes in the result set and may format it as epoch when storing it in it's index so that it will work with _time
... View more
If you are definining a rising column..
SELECT * FROM TABLE_NAME WHERE TRUNC(DATE_FIELD) BETWEEN to_date('04-03 2014','mm/dd/yyyy') AND to_date('04-03 -2014','mm/dd/yyyy') {{AND $rising_column$ > ?}}
ORDER BY DATE_FIELD ASC
... View more
I saw that http://apps.splunk.com/app/533/ Cisco ESA is deprecated, however, what add-on replaces it in the Cisco Enterprise Security Suite? I'm only seeing ISE, WSA, and ASA
... View more
I've solved this question. The answer is, When the log contains events that are specifically authentication, then assign those events to authentication. Otherwise a Network Log should just be a network log.
... View more
We have some new logs we would like to import.
These logs seem to contain all the fields of network traffic, but it was requested to also show them as authentication. Is it best practice to tie in a given log with multiple Common Information Models? Or should everything be Network Or Authentication Or Web etc..
I was thinking definitely not as the "action" field would need to follow each model.
... View more
Right, have you tried any of the queries i have suggested? such as one like
SELECT TOP 1000 * FROM TABLE_NAME WHERE DateField <= '01/01/2014 00:00:00' and DateField >= '03/31/2014 23:59:59'
... View more
Also, You may have to re-create your data input if you are changing the query as it will not re-run the first run again, the clone feature works nicely for this.
... View more
The stuff in the brackets will not be run the first time the query is run, so if you have curly braces around that, it will grab all your data. the curly braces are meant to hold the {{ $rising_column$ > ?}} pattern
... View more
I think you want something like
SELECT * FROM TABLE_NAME WHERE ROWNUM <= 30 {{AND $rising_column$ > ?}}
Or if you are not doing "Tail"
SELECT * FROM TABLE_NAME WHERE ROWNUM <= 30
The stuff in the brackets will not be run the first time, so putting {{ where rownum <= 30 }} will exclude this from the first run.
... View more
The timezone will be applied on index time. Therefore you cannot modify existing data to show correctly. You may want to export the data and re-import it.
... View more