Ryan Wynn

hi @oliveiracdz thank you I think I see the problem. `encoding.go` is not accounting for types `primitive.A`, `primitive.M` and `primitive.D`. Hopefully, that should fix it.

the reason for the difference is that change events go through https://github.com/rwynn/gtm/blob/master/gtm.go#L869 which handles those types, but monstache view replication takes a slightly different path.

Hi @neilchen12 Would you be able to try a different resume strategy? There is another that saves a separate resume token per change stream (per collection in your case) instead...

It may be because in Elasticsearch 8 security is enabled by default. https://www.elastic.co/guide/en/elasticsearch/reference/current/manually-configure-security.html You can configure monstache using config options `elasticsearch-user` / `elasticsearch-password` OR `elasticsearch-pki-auth` and transport level security with...

Monstache only connects via the http/https endpoint. So you can generate a pem file and then reference that in your monstache config. This configuration worked for me on a new...

In your case the url to connect in docker compose would be `https://es7:9200`. Notice that is `https` not `http`. You can mount the pem file as a volume into the...

Are you running direct reads every day? The failed count could be because the documents already exist in MongoDB. There is a boolean configuration called `direct-read-stateful`. If enabled it would...

Hi @dwalker-va if your team could submit a PR I'd be happy to review and merge it. I think it would just be a matter of a new config option...

Yeah, any help would be really appreciated. Let me know if you need any help getting started. After installing go you should just be able to run monstache with `go...

@andreadistefano I did notice and correct one issue with reading the api key from the toml config file. Please let me know if that helps.