<div dir="ltr">Awesome, thanks! <br><div>It worked.</div><div><br></div><div>Nabil</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 10:52 PM Jon Siwek <<a href="mailto:jsiwek@corelight.com">jsiwek@corelight.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Apr 22, 2020 at 12:15 AM Nabil Memon <<a href="mailto:nabilmemon.ec@gmail.com" target="_blank">nabilmemon.ec@gmail.com</a>> wrote:<br>
<br>
> Stats gets updated in connection record after dns_end() event raised????<br>
<br>
Yes, the "dns_end" event and associated values can get<br>
created/enqueued before the states are updated. However, the updated<br>
stats *are* technically available by the time the event gets<br>
dispatched, so one trick to refresh the connection record value would<br>
be to use "lookup_connection()". See if this helps:<br>
<br>
event dns_end(c: connection, msg: dns_msg)<br>
{<br>
c = lookup_connection(c$id);<br>
print "dns_end: -------------------------------";<br>
print c$orig, c$resp, c$id, c$dns;<br>
print "dns_end: -------------------------------";<br>
}<br>
<br>
- Jon<br>
</blockquote></div>