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
Hi, I see in packetloss, if sth is wrong in GetSymsByStack() , the evt won't be sent to the sink because we continue to skip the next steps :
stacks, err:=bpfutil.GetSymsByStack(uint32(event.StackId), p.objs.InspPlStack)
iferr!=nil {
log.Warnf("%s failed get sym by stack, err: %v", probeName, err)
continue
}
It means we finaly miss record this event. Actually in my production env, I do encounter this problem, I get some packetloss metric but no event.
So how about not continue,
Stop on failing getting kernel symbol to avoid too many meaningless drop event (drop event on tcp closing e.g.).
I understand user do need the event regardless of whether symbol was resolved. Should we add a config for packetloss probe to specify the behaviour when cannot resolve symbol
Hi, I see in packetloss, if sth is wrong in
GetSymsByStack()
, the evt won't be sent to the sink because wecontinue
to skip the next steps :It means we finaly miss record this event. Actually in my production env, I do encounter this problem, I get some packetloss metric but no event.
So how about not
continue
,The text was updated successfully, but these errors were encountered: