In order to securely communicate with your organization's systems, SailPoint uses Virtual Appliances (VAs) to connect your tenant and on-premises applications. A VA is a Linux-based virtual machine that connects to your sources and apps using SailPoint APIs, connectors, and integrations.
Have the high-level architectural visuals been deprecated and removed from Compass? I don’t see any on this article or poking around the IdentityNow Wiki. I swear I remember SailPoint used to provide some diagrams of the various VA implementation options.
Hello @cassidiopia !
We have configuration diagrams here.
We also have HA/DR diagrams here.
I hope this helps.
Can we have documentation here regarding:
How to change the log level for a particular connector.
How to stop and start CCG services.
A list of useful commands to use in the VA.
I know it is in the documentation somewhere on compass, but I prefer documentation.sailpoint.com
I recommend scanning the following documentation and migrating the missing, usefull and still relevant bits.
Hello Angelo! Thanks for reaching out. Glad to hear you prefer documentation.sailpoint.com!
For security reasons, the information in the VA Troubleshooting Guide must remain in Compass behind a login.
Thanks!
Hi @hope_carlson,
Sorry for the late response. I did not get notified on your answer as you statically used my name rather than tagging my account or marked this as reply on my specific question.
I do encourage SailPoint to rethink this decision. First of all I think that this is only creating a false sense of security. First of all it is very easy for anybody to create an account anyway. My girlfriend created one such that she could watch me present during the developer days 
. Secondly content of that page can be discussed on this developer portal anyway by end users asking others for help when they get stuck with VA management and others replying. So this information is “leaking” to developer.sailpoint.com anyway, which does not require an account or login to see the content.
Finally for end users it would make sense if documentation can be found in one location, regardless of whether a login is preferred or not. So even if SailPoint wants to keep this login requirement, it would make sense to look at options for marking certain documentation.sailpoint.com pages as login_required:true or something like that, such that opening those pages trigger the login prompt.
Kind regards,
Angelo
Hello @angelo_mekenkamp ,
Thanks for your feedback. We’ll take this into consideration for future content strategy.
Kind regards,
Hope