Legacy Heartbeat URL setting?


#1

We’re in process of upgrading all of our old clients to new clients, but we’ve already upgraded our Couchbase cluster…

I’ve discovered, however, with the 3.x releases of Couchbase that /pools/heartbeat now returns “Not Found.”

What is the best way to configure these legacy applications?

Best to leave the heartbeat monitor or remove it? What is the consequence of leaving it if that’s not the best choice (we’ve not noticed any issues so far)?

Thanks - H