So, I ran | delete on the wrong query. ooopz. Per the various docs I've poured through, it seems that warm directories are where I would find events that I want to thaw. Is there any advice out there to offer for rebuilding indexes because of events marked for delete ? I would move them all to the thaw bucket and rebuild but I fear I will have lots of duplicates in that case since I only ran the delete cmd on a certain subset of events. Any suggestions are appreciated! Thanks Adam ... View more

Hello, I've tried a wide variety of queries but Postgres is returning errors when trying to pass a UUID in a variable to my query: base search | table l_id, l_name | eval l_id_quotes="'".l_id."'" | map maxsearches=100 search="dbquery mydb \"select * from my_table where id LIKE '$l_id_quotes$' \"" The errors look like: [map]: command="dbquery", A database error occurred: ERROR: syntax error at or near "027e435" Position: 47 Without the eval statement, I was unable to get a single-quoted value for postgres to not parse as a column. And if I exclude single quotes from around '$l_id_quotes$' then the query is always wrapped in double quotes, which causes the same problem with postgres. In addition to WHERE id LIKE... , I've tried: WHERE id::varchar='$l_id_quotes$' WHERE CHARINDEX (id, '$_id_quotes$') > 0 WHERE id IN ('$_id_quotes$') ... all to return the same errors. The query WHERE id::varchar='fake-literal-valid-uuid' actually works. Anybody done this successfully with postgres? Thanks! ... View more

I have multiple searches over a year's date range, similar to: base search | timechart span=1month dc(foo) and they are all reproducing the same strange statistics, and in turn visualization... all of the data is grouped by month, but the very last month is repeated twice, time stamps 7 hours apart, and the values for the first of those points being incomplete _time count 2013-12-01 00:00 100 2013-12-01 08:00 200 2014-01-01 08:00 300 2014-02-01 08:00 400 2014-03-01 08:00 500 2014-04-01 07:00 600 2014-05-01 07:00 700 2014-06-01 07:00 800 2014-07-01 07:00 900 2014-08-01 07:00 1000 2014-09-01 07:00 1100 2014-10-01 07:00 1200 2014-11-01 00:00 250 2014-11-01 07:00 1300 Is this expected behavior? If so, I would greatly appreciate any assistance with cleaning it up! Thanks very much ... View more