For the micro services implementation on the Docker / Openshift environment, we have these choices:
Option 1. Creating one management module per micro-service. This will result in many management modules (.jar files) per EM server
Option 2. Create many metrics grouping inside one management module. Limit the number of modules but have large numbers of metrics groupings within one module (jar).
Can you let me know which approach is recommended? Thanks.
All supported APM releases
| . Of the two approaches outlined, Option 1 would be the best approach. |
Option 1 makes it easier to add and make changes.
Option 2 is a more complex approach that could be harder to find MM components.
Also, the more metric groups, alerts, calculators, actions, etc, that you use, then the more resources that are taken up. Need to keep administering the large MM, and remove constantly unneeded MM components
Both approaches will have overhead and it will be an "it depends" answer. It is based on number of management module, size of management modules etc. If there are a few small management modules then option 1 will be a better. choice. As the number of small management modules goes up, then option 2 can be a viable option. It is hard to give a clear cut answer when option 2 would become viable because it is environment-dependent