MqttHistory

An MQTT-based history handler for messages recorded by mqttbot in MongoDB

There's also support for messages stored in MongoDB, assuming the message documents contain these required fields:

{
    "topic": "<mqtt history target topic name>",
    "original_payload": "<message payload>",
    "timestamp": <int64 seconds from Unix epoch>
}

V2 returns the messages from Mongo in the following format:

{
    "topic": "<mqtt history target topic name>",
    "original_payload": "<message payload>",
    "timestamp": <int64 seconds from Unix epoch>,
    "game_id" : "",
    "player_id": "",
    "blocked" bool,
    "should_moderate": bool, 
    "metadata" : {}, 
    "id": ""
}

Use make setup/mongo to create indexes on MongoDB for querying messages over user_id or topic, as well as a default 6 month TTL for messages stored in MongoDB.

Features

• Listen to healthcheck requests
• Retrieve message history from MongoDB when requested by users
• Authorization handling with support for MongoDB or an HTTP Authorization API

Setup

Make sure you have Go installed on your machine.

You also need to have access to running instances of Mongo.

Running the application

If you want to run the application locally you can do so by running

make deps
make setup/mongo
make run

You may need to change the configurations to point to your MQTT and Mongo servers, or you can use the provided containers, they can be run by executing make run-containers

Running the tests

The project is integrated with Github Actions and uses docker to run the needed services.

If you are interested in running the tests yourself you will need docker (version 1.10 and up) and docker-compose.

To run the tests simply run make test

Authorization

The project supports checking whether a user is authorized to retrieve the message history for a given topic. This can be done via either MongoDB- or HTTP-based authorization, depending on the configuration.

For MongoDB, which is the default method, the required settings are

mongo:
  host: "mongodb://localhost:27017"
  allow_anonymous: false # whether to make authorization checks or not
  database: "mqtt"

For HTTP auth, the required settings are

httpAuth:
  enabled: true # whether to use HTTP or MongoDB for authorization
  requestURL: "http://localhost:8080/auth" # endpoint to make auth requests
  timeout: 10 # request timeout in seconds
  iam:
    enabled: true # whether to use Basic Auth when accessing the Auth API
    credentials: # credentials for Basic Auth
      username: user
      password: pass

Observability

Logs

There is a middleware using the zap package to log requests with the JSON zap encoder.

All other pieces of code use the op package with a custom format.

⚠️ Only logs formatted as JSON are usually exported to a logging platform, i.e., only the aforementioned middleware is logging correctly and the team should fix this issue.

Traces

OpenTracing is used to report traces. The client implementation used is Jaeger's.

⚠️ OpenTracing is deprecated, as well as Jaeger's client package. That is, the team should replace OpenTracing with OpenTelemetry and Jaeger's client package with OpenTelemetry's agnostic client package.

Metrics

Metrics are exported using Datadog's statsd client package.