Hi there,

Just threw together something that, at least I think is cool/useful.

A "critical" status filter for the [NET1] Node Queue and BinkP Sessions messages. (Boards that aren't keeping a 0 Days since picking up mail, or
fail on their BinkP sessions is listed as "critical")

So if you don't see your node, you are setup correctly with no mail
pile or failure to authenticate in BinkP)

Currently it's just for NET 1 / Hub 1 (21:1/100), but if it's useful I
may extend it so it posts 3 and 4, and maybe even 21:1/10

I've thrown in 2 test messages to show off what it would look like, and
yes that is real data.

I'm not sure if any board can post in FSX_STA but I'll be posting this
in FSX_BOT.

As my board reads the Node Queue and BinkP Sessions messages ffrom
FSX_STA it will generate a filtered message and post that.

It's a simple Lua script that I setup with my Talisman board, so if
network control would like I can provide it. (Right now it's a bit
sketchy, but I'll be cleaning it up as I poke more with it)

Take Care,
Apollo


--- Talisman v0.47-dev (Linux/x86_64)
* Origin: Lunar Mod (21:1/236)

A "critical" status filter for the [NET1] Node Queue and BinkP
Sessions
messages. (Boards that aren't keeping a 0 Days since picking up mail,
or
fail on their BinkP sessions is listed as "critical")

Due to the differences in global time zones, would 1 days be more likely
to indicate issues or does this script take that into account?

Interesting stats.


--- Talisman v0.53-dev (Linux/armv7l)
* Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (21:4/134)

Due to the differences in global time zones, would 1 days be more
likely
to indicate issues or does this script take that into account?

I didn't think about that, easy enought to increase the days value as I
parse it into a number. (days > 4 maybe? rather than the current days !=
0)

Interesting stats.

Yup, I'm hoping it helps with network maintenance.

Take Care,
Apollo


--- Talisman v0.47-dev (Linux/x86_64)
* Origin: Lunar Mod (21:1/236)