Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 01222019 run at 16:01:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 1145 We received this many responses to our CAP messages: 1145 We received this many unintelligible responses to our CAP messages: 0 HCE had this many retries in connecting to FEMA: 1 Total failures to connect to IPAWS (message lost): 0 ipaws_return_code | status | count -------------------+------------------------------------------------+------- 200 | Ack | 1080 202 | alert-signature-is-valid +| 1080 | +| | | 209 | message-references-expired-alert | 65 221 | invalid-CAPEXCHANGE-message | 65 300 | Ack | 1080 301 | non-IPAWS-alert | 65 401 | message-not-disseminated-as-NWEM | 1080 501 | message-not-disseminated-as-EAS | 1080 601 | message-not-disseminated-as-CMAS | 1080 602 | invalid-value-in-element-responseType | 103 606 | invalid-value-in-element-eventcode | 105 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 33 610 | lacks-parameters-to-generate-CMAM-text | 105 615 | signer-not-authorized-for-event-code-CMAS | 106 619 | signer-not-authorized-for-geocode_CMAS | 33 620 | referenced-alert-never-disseminated to CMAS | 117 800 | Ack | 1080 802 | public-blockchannel-disregarded | 1080 (18 rows) (remember, for some reason, 705 really counts against the 3xx range) The Latency is the delta between the time we create the cap message and the time we get the response back from IPAWS.H:M:S.ms Average_Daily_Transmission_Latency 00:00:08.107154