Skip to main content
LoginTry Now
Momentum Documentation
Momentum 4.x
Momentum 3.x
Momentum Mobile
Changelog
Submit a Ticket
Community
Customers
Developer Blog
Developer Hub
Service Status
Momentum
Momentum 3.x
Momentum for Mobile Push Notifications
gcm_logger Module

gcm_logger Module

Last updated March 2020

The gcm_logger logs Google notifications to file, writing to a single file in ‘@’ delimited format.

**Configuration Change. ** This feature is available as of version 3.5.5.

Like other loggers, the gcm_logger is configured in the ecelerity.conf file. To load this module add the following lines to the main body of the ecelerity.conf file:

gcm {}
gcm_logger "gcm_logger1" {
  logmode = 0644
  logfile = "/var/log/ecelerity/gcmlog.ec"
  heartbeat = 60
}

In order to load the gcm_logger module, you must first load the gcm module as shown in “gcm_logger module configuration”. The gcm module has no options apart from debug_level and enabled.

You can configure multiple instances of this logger. For instance, you may also wish to create "real time" jlogs. For more information see the jlog Module and Logging.

Note

If you wish to export logged data to an external system create jlog files and follow the instructions given at Using JLog::Reader.

The configuration shown in “gcm_logger module configuration” instructs Momentum to write a file containing GCM records to /var/log/eclerity/gcmlog.ec with the file permissions 0644. The heartbeat option sets the interval at which "heartbeat" entries will write to the log. 60 is the default value. The heartbeat entries in the log are essential for proper operation of the real time statistics and changing the default value of heartbeat is not recommended unless you are advised to do so by Message Systems support. In a cluster configuration, the gcm_logger module must be enabled on each MTA node used to deliver Google Push notifications.

A complete list of the configuration options follows:

concurrency

This option defines the number of threads used by the gcm_logger. The default value for this option is 1.

heartbeat

The interval at which "heartbeat" entries will be written to the log. The default value for this option is 60.

log_delivery

Whether or not to log deliveries. The default value for this option is true.

log_delivery_format

This option determines the format of the delivery log. The default value for this option is "%t@D@%i@\"%sa\"@\"%da\"@%d@%g@%b@%H@%B@". How these macros are expanded is described in “gcm_logger Macros”. The second field value, D, is a literal indicating that this is a delivery log entry.

log_heartbeat_format

This option determines the format of the heartbeat log. The default value for this option is %t@M where the macro %t expands to a Unix timestamp and M is a literal indicating that this entry is a heartbeat.

log_permfail

Whether or not to log permanent failures. The default value for this option is true

log_permfail_format

This option determines the format of the permanent failure log. The default value for this option is %t@P@%i@\"%sa\"@\"%da\"@%d@%g@%b@%H@%B@%S@%e. How these macros are expanded is described in “gcm_logger Macros”. The second field value, P, is a literal indicating that this is a permanent failure log entry.

log_tempfail

Whether or not to log temporary failures. The default value for this option is true.

log_tempfail_format

This option determines the format of the temporary failure log. The default value for this option is "%t@T@%i@\"%sa\"@\"%da\"@%d@%g@%b@%H@%B@%%S@%e". How these macros are expanded is described in “gcm_logger Macros”. The second field value, T, is a literal indicating that this is a temporary failure log entry.

logfile

This option determines the name of the log file. The default value for this option is /var/log/ecelerity/gcmlog.ec.

logmode

The mode of the log file in octal notation. The default value for this option is 0644.

namespace

This option specifies which macro namespaces should be searched, when expanding the format strings. This variable is set using commas to separate different namespaces. The default value for this option is gcm_logger,sieve,custom_logger.

thread_pool

Associate a thread pool with the logger. There is no default value for this option. To create a thread pool, see threadpool.

gcm_logger Macros

The macros are expanded as indicated in the following

  • %B – Size of the outbound message in bytes, including the headers and payload. Taken from the value of the context variable "DLV_Msg_Length".

  • %b – The outbound binding name.

  • %d – The outbound domain name.

  • %da – The destination address, Taken from the value of the context variable "DLV_Dest_Addr" or the rcptto local part from the email envelop

  • %dt – The Registration ID (device token). This is not captured in any of the default formats but it is supported for custom formats. Taken from the value of the context variable "DLV_Dest_ID".

  • %e – The GCM error description. Taken from the value of the context variable "DLV_Response_Status_Detail".

  • %g – The outbound binding group name.

  • %H – The IP address of the remote server. Taken from the value of the context variable "DLV_Remote_IP_Address".

  • %i – The message ID.

  • %P – The pathway

  • %PG – The pathway_group

  • %S – The numerical equivalent of the GCM error status code. Taken from the value of the context variable "DLV_Response_Status".

  • %sa – The source address of the sender. Taken from the value of the context variable "DLV_Source_Addr" or the mailfrom (including both local part and domain part) from the email envelope.

  • %t – The Unix timestamp.

Was this page helpful?