search

Appdynamics / config-assessment-tool

This project aims to provide a single source of truth for performing AppDynamics Health Checks.
Other
17 stars 16 forks source link

Improve BT maturity assessment #79

Open davidskeen opened 2 years ago

davidskeen commented 2 years ago

It's ok to report overall number of BTs, but I would not score that. It would be better to score average number of BTs per tier. If you have > 40 BTs per tier, that is bronze, etc. Also I'd like to see separate scoring for apps with BT lockdown vs not. If lockdown, then only score based on BTs per tier. If no lockdown, then also look for load in All Other Traffic BTs: the more AOT BTs with load, the worse.

Keep in mind that BT lockdown is powerful, but it also has to be manually configured at each level of an app. There is no API to register BTs as 1st class from AOT BTs. So BT lockdown is not best suited depending on the app and how it is managed.

There is a related issue involving number of tiers. If an app has > 50 tiers, that could arguably be bronze. I am unsure of this, because if there is an app with BTs in a few tiers, then many downstream tiers, that would work fine. Not sure if this is worth reporting or scoring.

bhjelmar commented 2 years ago

Good points David.

And one additional criteria to add, is the BT limit reached. Aaron shared with me a little while ago a hidden API to fetch that. I think I'll include that as well as part of this effort.