Please don't read this file with IE, it won't work, use Firefox or Chrome Stats for 01012019 run at 23:56:01Z run on vm-lnx-hce-heap1a.ncep.noaa.gov We sent this many CAP messages (1 per segment): 2057 We received this many responses to our CAP messages: 2057 We received this many unintelligible responses to our CAP messages: 1 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 | 1898 202 | alert-signature-is-valid +| 1898 | +| | | 209 | message-references-expired-alert | 158 221 | invalid-CAPEXCHANGE-message | 158 300 | Ack | 1898 301 | non-IPAWS-alert | 157 401 | message-not-disseminated-as-NWEM | 1898 501 | message-not-disseminated-as-EAS | 1898 601 | message-not-disseminated-as-CMAS | 1898 602 | invalid-value-in-element-responseType | 190 606 | invalid-value-in-element-eventcode | 190 608 | marine-zone-SAME-geocode-not-disseminated-CMAS | 61 610 | lacks-parameters-to-generate-CMAM-text | 190 615 | signer-not-authorized-for-event-code-CMAS | 197 619 | signer-not-authorized-for-geocode_CMAS | 61 620 | referenced-alert-never-disseminated to CMAS | 209 800 | Ack | 1898 802 | public-blockchannel-disregarded | 1898 (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.402383