[ZBX-20357] MongoDB monitoring plugin problem with custom port Created: 2021 Dec 15 Updated: 2025 Feb 14 Resolved: 2025 Feb 14 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent2 plugin (G) |
Affects Version/s: | 5.0.18, 5.4.8, 6.0.0beta1 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Major |
Reporter: | Sergei Grigoriev | Assignee: | Stanislavs Jurgensons |
Resolution: | Duplicate | Votes: | 0 |
Labels: | Agent2, MongoDB | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() |
||||||||
Issue Links: |
|
Description |
Checking Mongodb with a custom port. |
Comments |
Comment by Edgar Akhmetshin [ 2021 Dec 16 ] |
Hello Sergei, Thank you for reporting the issue. Could you please set DebugLevel to 5 in the agent configuration file and restart it, after repeat check with mongodb. Attach log to the issue. Regards, |
Comment by Sergei Grigoriev [ 2021 Dec 16 ] |
Hi Edgar, Check port from net.tcp.service |2021-12-16 15:03:52|1| |2021-12-16 15:03:22|0| |...| | |2021-12-16 15:01:22|0| |2021-12-16 15:00:52|1| Check from mongodb.ping (at 15:18 decreased Discard unchanged with heartbeat to 1 min) |2021-12-16 15:19:21|0| |2021-12-16 15:18:21|0| |2021-12-16 15:01:21|0| |2021-12-16 14:38:21|1| |
Comment by Edgar Akhmetshin [ 2021 Dec 20 ] |
Hi, thank you, but log is not attached to the issue. Could you please try once again? |
Comment by Sergei Grigoriev [ 2021 Dec 20 ] |
Comment by Edgar Akhmetshin [ 2021 Dec 21 ] |
Sergei, could you please confirm, this 27018 is part of the instances started with --shardsvr or just separate one with port modified? |
Comment by Sergei Grigoriev [ 2021 Dec 21 ] |
MongoDB standalone docker container (0.0.0.0:27018->27017/tcp)
|
Comment by Edgar Akhmetshin [ 2021 Dec 21 ] |
|