monstache

• Fix issue where some date values would be rejected by Elasticsearch with invalid formatting

• Fix regression in cluster mode where http server would not be started immediately

• Fix regression in cluster mode where http server would not be started immediately

• Fix regression in cluster mode where http server would not be started immediately

• Fix regression in cluster mode where http server would not be started immediately

• Designed for the best support of Elasticsearch 7 (Choose monstache v5 if you are still on Elasticsearch 6)
• Utilizes the offical golang driver from MongoDB for improved compatibility with recent versions of the server

• Improvements to cluster mode

• Improvements to cluster mode

• Improvements to cluster mode

Version 5

Version 5 is the first release of monstache to use the official MongoDB golang driver. Version 5 targets MongoDB 3.6+ and Elasticsearch 6+.

Changes from previous versions

Some of the previous monstache settings related to MongoDB have been removed in this version as they are now supported in the driver connection string

Monstache now defaults to use change streams instead of tailing the oplog for changes. Without any configuration monstache watches the entire MongoDB deployment. You can specify specific namespaces to watch by setting the option change-stream-namespaces to an array of strings.

The interface for golang plugins has changed due to the switch to the new driver. Previously the API exposed
a Session field typed as a *mgo.Session. Now that has been replaced with a MongoClient field which has the type *mongo.Client. See the MongoDB go driver docs for details on how to use this client.

• Add the field name to the message when a field is removed from a document with prune-invalid-json enabled
• Add a -debug flag to get very detailed information from the MongoDB driver
• Add a max-depth setting for relate configurations to give more control about how a relate fires
• Performance improvements
• Build with the release artifacts and docker images with golang version 1.12.4

• Add the field name to the message when a field is removed from a document with prune-invalid-json enabled
• Add a -debug flag to get very detailed information from the MongoDB driver
• Add a max-depth setting for relate configurations to give more control about how a relate fires
• Performance improvements
• Build with the release artifacts and docker images with golang version 1.12.4

Version 5 alpha1

This is a pre-release work in progress version of monstache 4 ported to use the official MongoDB golang driver.

This version of monstache targets MongoDB 3.6+ and Elasticsearch 6+.

Changes from previous versions

Some of the monstache settings related to MongoDB have been removed in this version as they are now supported in the connection string

Monstache now defaults to use change streams instead of tailing the oplog for changes. Without any configuration monstache watches the entire MongoDB deployment. You can specify specific namespaces to watch by setting the option change-stream-namespaces to an array of strings.

The interface for golang plugins has changed due to the switch to the new driver. Previously the API exposed
a Session field typed as a *mgo.Session. Now that has been replaced with a MongoClient field which has the type *mongo.Client. See the MongoDB go driver docs for details on how to use this client.

• Fix bug in mongoX509Settings validate ( issue #198)
• Fix issue stopping monstache when using legacy oplog tailing (non change-stream) of a sharded cluster
• Upgrade golang on release builds to 1.12.1
• Upgrade docker images to use Alpine 3.9.2

• Fix bug in mongoX509Settings validate ( issue #198)
• Fix issue stopping monstache when using legacy oplog tailing (non change-stream) of a sharded cluster
• Upgrade golang on release builds to 1.12.1
• Upgrade docker images to use Alpine 3.9.2

• Add a new integer setting direct-read-concur which, when set, limits the number of concurrent direct reads that will be performed. E.g. if you have direct-read-namespaces set to 23 namespaces and direct-read-concur set to 2, then monstache will read and sync namespace 1 and 2 concurrently and wait for both to finish before starting 3 and 4 - and so on.
• Add the ability to disable direct read collection splitting by setting direct-read-split-max to -1. By default, monstache will split each direct read collection up to 9 times and read each segment in a separate go routine. If you don't want to split collections at all then set direct-read-split-max to -1.

• Add a new integer setting direct-read-concur which, when set, limits the number of concurrent direct reads that will be performed. E.g. if you have direct-read-namespaces set to 23 namespaces and direct-read-concur set to 2, then monstache will read and sync namespace 1 and 2 concurrently and wait for both to finish before starting 3 and 4 - and so on.
• Add the ability to disable direct read collection splitting by setting direct-read-split-max to -1. By default, monstache will split each direct read collection up to 9 times and read each segment in a separate go routine. If you don't want to split collections at all then set direct-read-split-max to -1.

• Fix issue using monstache with GoCenter

• Fix issue using monstache with GoCenter

• Upgrade golang to 1.12
• Fix a panic under some conditions when processing the result of a golang plugin Map function