# Can't monitor the secondary node in mongodb replication
**URL:** https://forums.percona.com/t/cant-monitor-the-secondary-node-in-mongodb-replication/10664
**Category:** PMM 2.x
**Tags:** pmm, mongodb
**Created:** [June 2, 2021, 3:30am UTC](https://forums.percona.com/t/cant-monitor-the-secondary-node-in-mongodb-replication/10664 "2021-06-02T03:30:01Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@webstock\_zt](https://forums.percona.com/u/webstock_zt)
#### Post date: [June 2, 2021, 3:30am UTC](https://forums.percona.com/t/cant-monitor-the-secondary-node-in-mongodb-replication/10664/1 "2021-06-02T03:30:01Z")
I deployed a mongodb sharded cluster on my servers.The cluster has two shards: rs0 : PRIMARY-SECONDARY-ARBITOR rs1: PRIMARY-SECONDARY-ARBITOR. And I deployed pmm2 (Both server and client version are 2.17) to monitor the cluster.I followed the official document to deploy the pmm2.x.However, when I watch the mongodb repliset summary tag, The monitoring data of nodes in the same replica set is the same as the primary node which means I can’t monitor the secondary node.How can I solve this problem?Thank you.
---
### Author:  [@Vadim\_Yalovets](https://forums.percona.com/u/Vadim_Yalovets)
#### Post date: [June 2, 2021, 7:53am UTC](https://forums.percona.com/t/cant-monitor-the-secondary-node-in-mongodb-replication/10664/2 "2021-06-02T07:53:27Z")
Hi @webstock_zt
The issue with nodes ReplSet states has been fixed in 2.18.0
Please update pmm2-client to the latest version.
---
### Author:  [@webstock\_zt](https://forums.percona.com/u/webstock_zt)
#### Post date: [June 3, 2021, 12:27am UTC](https://forums.percona.com/t/cant-monitor-the-secondary-node-in-mongodb-replication/10664/3 "2021-06-03T00:27:49Z")
Thank you @Vadim_Yalovets!
I have updated pmm2 to version 2.18.0 and the problem is solved.