Check OR, IN, and VA monitors

[lippytak]

(If we care at the moment). They all show down but I think they're all up.

[alanjosephwilliams]

Manual check confirmed they are all up. Texas and Louisiana are both actually down right now.

• Indiana has been down for 17 hours. Manually, I can confirm the string we check for is indeed present for Indiana. We've had some difficulty maintaining accurate checks on this site due to the way content is delivered.
• Oregon has been down for 13 hours. I've also manually confirmed that our transaction is using a string present on the page.
• Virginia has been showing as down for 8 days. Each word in the string in our transaction check was capitalized "Apply for Assistance", but that string now only appears on the site later in a sentence. I've now updated the string accordingly. Our checks are now showing it as up, but as of right this moment, we have not registered a corresponding event.

On Fri, Apr 3, 2015 at 10:23 AM, Jake Solomon notifications@github.com wrote:

(If we care at the moment). They all show down but I think they're all up.

— Reply to this email directly or view it on GitHub https://github.com/codeforamerica/snap-it-up/issues/57.

t: @alanjosephwilli p: 817 713 6264

[Mr0grog]

Our checks are now showing [Virginia] as up, but as of right this moment, we have not registered a corresponding event.

FYI, since we now poll Pingometer for changes instead of using the hook (unreliable), it can take a few minutes to see changes. However those changes will show up with the right date/times in the past.

If I understand correctly, Oregon and Indiana are up, but Pingometer is still failing them?

[alanjosephwilliams]

Ah yes, thanks @Mr0grog.

Yes. Interestingly, the Indiana monitor showed it as up for a couple of hours on 4/3

Looks like Oregon is experiencing frequent events—which could be that the monitor is timing out at 45 seconds. I however, am having no problem on my machine / the CfA connection.

[alanjosephwilliams]

Oregon is back up, suggesting further that it is simply at load time issue. Indiana continues to be down.

I'll close this issue once I articulate a process for QA (#58) and the escalation for problematic monitors.