Hey all,
Was curious to hear anyone's opinions on at what point during the lifecycle of an APM policy (for instance, i have one that has roots in v11.5) should I consider building a fresh one?
Similarly, is there any guidance on converting a policy to Modern templates?
Thanks,
Josh
MVPwhen you upgrade - the schema can and does change - and the new features are available for use.
i have migrated apps using the export / import feature which will also adjust the schema if needed
Funnily enough I tried the export via GUI and got an Internal Server error, which led me to troubleshooting that with this guide. Troubleshooting continues...
K03600730: Receiving ''internal server error'' when exporting APM policy through GUI
NimbostratusDid you find the solution.?
EmployeeRe-evaluation of authentication/authorization logic is a great thing to keep on top of.
APM's customization system is complicated. The template files that define all of the end-user facing HTML and JS are written when you first create the per-session access profile (which also creates the policy). You'll have to create a new one to try out Modern. Other than the end-user web content, modern and standard policies operate the same way.
