HTTP backend
Module description
This module is a backend of mod_event_pusher that enables forwarding certain events (messages, presence, etc.) via HTTP to external services such as push (by mobile, email or SMS), big data, or analytics services.
How it works
The module hooks on all packets sent by connected users. When the hook is triggered, the module:
- runs a callback module's
should_make_req/6
function to see if a notification should be sent - runs a callback module's
prepare_headers/7
to get http headers to be used - runs a callback module's
prepare_body/7
- sends a POST request composed of
{Host::binary(), Sender::binary(), Receiver::binary(), Message::binary()}
to the http notification server
You can configure multiple handlers e.g. for sending various types of messages to different HTTP servers.
Prerequisites
This module uses a connection pool created by mongoose_http_client
.
It must be defined in the outgoing_pools
settings.
Options
modules.mod_event_pusher.http.handlers
- Syntax: array of TOML tables with the keys described below
- Default: empty list
A list of handler definitions. All handlers are applied for each event.
modules.mod_event_pusher.http.handlers.pool_name
- Syntax: non-empty string
- Default:
"http_pool"
- Example:
pool_name = "http_pool"
Name of the pool to use to connect to the HTTP server (as defined in outgoing_pools
).
modules.mod_event_pusher.http.handlers.path
- Syntax: string
- Default:
""
- Example:
path = "/notifications"
Path part of an URL to which a request should be sent (will be appended to the pool's prefix path).
modules.mod_event_pusher.http.handlers.callback_module
- Syntax: string
- Default:
"mod_event_pusher_http_defaults"
- Example:
callback_module = "mod_event_pusher_http_notifications"
Name of a module which should be used to check whether a notification should be sent. The default callback module, mod_event_pusher_http_defaults
, sends notifications for all non-empty chat messages. You can use this module as a starting point for developing a custom one.
Example configuration
1 2 3 4 5 6 7 8 9 10 11 |
|
Notifications will be POSTed to http://localhost:8000/webservice/notifications
.
TOML also allows to specify the handler in its own subsection.
1 2 3 |
|
This alternative syntax is useful for specifying multiple handlers with options:
1 2 3 4 5 6 7 8 9 |
|
Here, some notifications will be POSTed to http://localhost:8000/webservice/notifications
and some to http://localhost:8000/webservice/alerts
, depending on implementation of should_make_req/6
in the two callback modules.
Default payload format
The default HTTP event pusher sends a POST request with Content-Type application/x-www-form-urlencoded
. The form has the following fields:
author
: name of the user who authored the messageserver
: name of the server from where the message originatesreceiver
: name of the user who the message is formessage
: content of<body>
element of the message
The contents of the author, server and receiver fields are processed by stringprep
.
As a result, these values are all lower case.
Example
Below is an example of what the body of an HTTP POST request can look like:
1 |
|
Metrics
If you'd like to learn more about metrics in MongooseIM, please visit MongooseIM metrics page.
Name | Type | Description (when it gets incremented) |
---|---|---|
[Host, mod_event_pusher_http, sent] |
spiral | An HTTP notification is sent successfully. |
[Host, mod_event_pusher_http, failed] |
spiral | An HTTP notification failed. |
[Host, mod_event_pusher_http, response_time] |
histogram | Does not include timings of failed requests. |