Status counters

[Alan DeKok]

Anders Holm wrote:
> So, for Access-Requests we ignore Status-Server packets, but
> Status-Server packets do increment Access-Accept?

  Perhaps you didn't see my message or read the names of the counters.
One counter counts Access-Requests, and another one counts Access-Accepts.

  There is no "ignore" of Status-Server packets.

  The reason for incrementing Access-Accepts has been explained.

> Would there be a
> counter for Status-Requests, so I could correlate the figures so I can
> figure out what is what?

  Sure.  Send a patch.

> Would there be an idea to have separate counters just for the Status-*
> type counters? Might be one handy way to handle that, as that'd separate
> those type of stats from each other as well as giving higher resolution.

 There is only one Status-Server packet.  I don't know what you mean by
"Status-*".

>>   If you need deltas, track them yourself in the client app.  It's the
>> only way to get them right.
>>   
> Mmm.. Even then there'd be potential race conditions, data loss etc.

  Huh?  You have one client app querying the server and keeping track of
deltas.  Other client apps query it.  And data loss can be prevented by
keeping track of counters on disk, too.

> I'd
> be using this data to gather metrics, and then in turn have alarms based
> on those metrics (levelling and thresholds). Ensuring the base data is
> correct then is of importance. OR at least understanding what the base
> data is telling us is of importance I should say .. ;)

  Sure.  Track it, store it, no problem.

  Alan DeKok.