I'm running a combination of MongoDb, Elasticsearch and FluentD on an Azure Kubernetes cluster. The intention is to sync data from the MongoDb to ElasticSearch so it is available for quick search / analysis.
I've got things up and running up to the point where the plugin makes a connection with the MongoDb. But it does not pick up any records from the database.
I can confirm that if I change the username, password or database name in my ConfigMap, the fluentD pod log shows an 'unauthorized for database X' message.
If I use the correct connection string, the logs show nothing.
This makes me think initial connection is established properly.
I've verified that the ElasticSearch plugin works properly using a simple @type tail as input <source>.
I can also confirm that the collection I'm using exists and contains data in the given MongoDb.
So I seem to have a working connection, but nothing happens. And that's where I hit a wall. I suspect the plugin either can't find the collection, or can't read from it, but without any kind of log output I'm not sure what's happening.
I'm not suggesting this is an issue with the plugin itself, but if anyone has any advice on what additional steps I can take to find out what the issue is and/or can spot a fault in my configmap (below), I'd be most grateful.
I'm running a combination of MongoDb, Elasticsearch and FluentD on an Azure Kubernetes cluster. The intention is to sync data from the MongoDb to ElasticSearch so it is available for quick search / analysis.
I've got things up and running up to the point where the plugin makes a connection with the MongoDb. But it does not pick up any records from the database.
I can confirm that if I change the username, password or database name in my ConfigMap, the fluentD pod log shows an 'unauthorized for database X' message. If I use the correct connection string, the logs show nothing. This makes me think initial connection is established properly.
I've verified that the ElasticSearch plugin works properly using a simple
@type tail
as input<source>
. I can also confirm that thecollection
I'm using exists and contains data in the given MongoDb.So I seem to have a working connection, but nothing happens. And that's where I hit a wall. I suspect the plugin either can't find the collection, or can't read from it, but without any kind of log output I'm not sure what's happening.
I'm not suggesting this is an issue with the plugin itself, but if anyone has any advice on what additional steps I can take to find out what the issue is and/or can spot a fault in my configmap (below), I'd be most grateful.