2014년 12월 4일 목요일

MMS Concerns

We have no plans on using the new MMS automation functionality.   We have a proven, documented process for installing Mongo that we are in no hurry to change.  We support many clients MongoDB implementations.  Our security rules dictate that NO ports can be opened between different clients servers, because of this each client needs their own group.  (We have a lot of groups).

We have been told several things:

1.  No new development is going to be done on Classic MMS groups
2.  Eventually the Classic groups will be deprecated and everyone will have to use the new groups in order to use MMS.

We are not going to rebuild all of our production servers just to be monitored by MMS.   We really don't want to be forced to change our implementation methods.  

How long will the Classic groups be supported?  Will you be doing bug fixes on the Classic groups?  Will there ever be an option of picking your group type?  (I'm baffled by the business decision to require automation in order to monitor - how many people are actually rebuilding their production stacks??)

Evidently we may have to look for a new way to monitor our existing implementations and it would be good to know how much time we have.



We continue to maintain, develop and support MMS Classic for existing groups. We have not scheduled ending support for Classic groups and we will provide advanced notice. We're happy to discuss some options with you, offline.



I have a similar problem than Evelyn... Would it be possible to create new classic groups at least for the existing accounts? We already have a deploy procedure and, as Evelyn, we don't want to open ports between different servers. We already tried adding a new agent for the new infra, but 2 active monitoring agents is not supported... 

How can we manage this without going to automation? 



I have the same concern, we have a docker based environment, so automated deploy is out of the scope of possibilities for now....

Am I out of options as fa as using (and paying for) MMS?



The question that poses in my mind is, would older MMS customers be willing to pay for the monitoring portion of MMS? Because, and this is total conjecture, but if you look at it, MMS was at first a way for MongoDB Inc./ 10gen to get intimate knowledge of MongoDB usage, to improve Mongo. So I am assuming that is why it was free to begin with. I still think the symbiosis could be there, but obviously Mongo shouldn't be footing too big a part of the bill to run the monitoring side of MMS. So, now would be the time to start charging for MMS monitoring, to cover some of the costs. But, would customers pay for it, since it has been free to begin with? 



Oh, and I also brought up this as a business concern in another thread. 


I believe one of the decision makers for a pure management system within MMS answered nicely on that thread. I've noted this thread in that one, so he is aware of this discussion. 


댓글 없음:

댓글 쓰기