2024-02-24
▼ ▲ Namespaces/NotificationHubs/metricDefinitions
Operations :
Name : outgoing.fcmv1.success
Displayname : FCMv1 Successful Notifications
Displaydescription : The count of all successful notifications.
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.invalidcredentials
Displayname : FCMv1 Authorization Errors (Invalid Credentials)
Displaydescription : The count of pushes that failed because the PNS did not accept the provided credentials (FCMv1 result: Sender Id Mismatch, Unauthorized, or Forbidden).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.badchannel
Displayname : FCMv1 Bad Channel Errors
Displaydescription : The count of pushes that failed because the registrationId in the registration was not recognized (FCMv1 result: Invalid registration, Missing Registration, Not registered, Not found, or Gone).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1v1.throttled
Displayname : FCMv1 Throttled Notifications
Displaydescription : The count of pushes that failed because FCMv1 throttled this app (FCMv1 Result: Quota Exceeded or 429).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.invalidnotificationformat
Displayname : FCMv1 Invalid Notification Format
Displaydescription : The count of pushes that failed because the payload was not formatted correctly (FCMv1 result: Invalid TTL, Invalid parameters, or Invalid data key).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.invalidnotificationsize
Displayname : FCMv1 Invalid Notification Size Errors
Displaydescription : The count of pushes that failed because the payload was too large (FCMv1 result: Message too big).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.wrongchannel
Displayname : FCMv1 Wrong Channel Errors
Displaydescription : The count of pushes that failed because the registrationId in the registration is not associated to the current app (FCMv1 result: Invalid package name).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.pnserror
Displayname : FCMv1 Errors
Displaydescription : The count of pushes that failed because of errors communicating with FCMv1.
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
▼ ▲ Namespaces/NotificationHubs/metricDefinitions
Operations :
Name : outgoing.fcmv1.success
Displayname : FCMv1 Successful Notifications
Displaydescription : The count of all successful notifications.
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.invalidcredentials
Displayname : FCMv1 Authorization Errors (Invalid Credentials)
Displaydescription : The count of pushes that failed because the PNS did not accept the provided credentials (FCMv1 result: Sender Id Mismatch, Unauthorized, or Forbidden).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.badchannel
Displayname : FCMv1 Bad Channel Errors
Displaydescription : The count of pushes that failed because the registrationId in the registration was not recognized (FCMv1 result: Invalid registration, Missing Registration, Not registered, Not found, or Gone).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1v1.throttled
Displayname : FCMv1 Throttled Notifications
Displaydescription : The count of pushes that failed because FCMv1 throttled this app (FCMv1 Result: Quota Exceeded or 429).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.invalidnotificationformat
Displayname : FCMv1 Invalid Notification Format
Displaydescription : The count of pushes that failed because the payload was not formatted correctly (FCMv1 result: Invalid TTL, Invalid parameters, or Invalid data key).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.invalidnotificationsize
Displayname : FCMv1 Invalid Notification Size Errors
Displaydescription : The count of pushes that failed because the payload was too large (FCMv1 result: Message too big).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.wrongchannel
Displayname : FCMv1 Wrong Channel Errors
Displaydescription : The count of pushes that failed because the registrationId in the registration is not associated to the current app (FCMv1 result: Invalid package name).
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes
Name : outgoing.fcmv1.pnserror
Displayname : FCMv1 Errors
Displaydescription : The count of pushes that failed because of errors communicating with FCMv1.
Unit : Count
Aggregationtype : Total
Availabilities :
Timegrain : PT1M
Blobduration : P30D
Supportedtimegraintypes : PT1M
Fillgapwithzero : Yes