Mongo Agent not connecting
search cancel

Mongo Agent not connecting

book

Article ID: 408821

calendar_today

Updated On:

Products

DX SaaS

Issue/Introduction

Using APMIA(Application Performance Management Infrastructure Agent) with the Mongo extension does not connect to the instance and no metrics getting collected.

[ERROR] [IntroscopeAgent.mongodb-ia] Timed out after 30000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=HOSTNAME, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketException:}, caused by {java.net.UnknownHostException: }}]

Environment

APMIA 25.5.1 (Build 990011)

Resolution

Change the properties below to lowercase: 

BEFORE:
introscope.agent.mongodb.profiles.default.isAtlasMongoDb

AFTER
introscope.agent.mongodb.profiles.default.isatlasmongodb

Also, we are going to refactor the implementation. We may consider checking on introscope.agent.mongodb.profiles.default.isAtlasMongoDb upfront to avoid such unnecessary connection attempts based on introscope.agent.mongodb.profiles.default.host.port instead of the generated MongoDB Atlas connection string URI.

Also, looks like the current mongodb extension implementation is hardcoded to use mostly the "default" profile instance instead of using the profile instances specified by the user with introscope.agent.mongodb.profiles. There is MongoPropertyKeyReader class defined, but it does not appear to get used to look up the corresponding mongodb extension agent properties specific to the configured profile instances.

A permanent fix will be implemented in future releases.