Thanks for the help.
So, what do the Data Source Exception and Decryption Failed alarms do on the Master side of a persistent tunnel actually indicate? What would cause those to actualy generate their own events?
I've seen the Outstation (Publisher) side give me alarms when alarms are enabled, when I remote in to do troubleshooting and stuff, but I've never see the Master (Data source) alarms actually do anything.. Do they actually alarm on anything? I understand the difficulty of alarming on the Persistent thing, since there's a lot of hair on how people configure it (updating nightly, etc).. So, maybe I just answered my own question there.
I appreciate your advice, and I'll go for option (1). Putting a heartbeat on an edge detector seems like a kludgey workaround to me. And, well, I'm paying for cell data bandwidth here, so I'd rather not shovel more data than I need to. Especially if there's already handy counters built into the Persistent TCP metrics.
You've got me thinking, though, of any other steady-state values I regularly get throughout the day that I could alarm on for this. We do solar, and it changes all day long, but at night nearly all my data goes dead (no sun, you see), but we do have all our environmental sensors going out there. Problem is, we already have alarms on most of those.. and for some really still nights, the temperature and stuff are really quite stable.
I'll have to think a bit on this.. I think maybe your option 1 is probably the best option for this. Thanks for your help!