Watch-DbaDbLogin - Enhancement - Additional Fields from DMV sys.dm_exec_connections

[DougStevensGCPS]

Becoming familiar with Watch-DbaDbLogin and liking that it captures information across multiple servers for analysis.

Request
Include fields from the DMV sys.dm_exec_connections to the output.
Believe that the the fields [auth_scheme] and [encrypt_option] would be helpful. Therefore, other fields from the DMV can be considered as well (e.g. [net_transport], [protocol_type], [client_net_address], etc.)

Background
While working on a NTLM vs KERBEROS issue. Learned about the DMV sys.dm_exec-connections with a focus on in the [auth_scheme] field. Which lead to thinking it would be nice to have the [auth_scheme] and maybe [encrypt_option] included with the output of the Watch-DbaDbLogin function.

Benefit(s)

• The function will help validate that connections are being made as expected/intended. For example, If seeing connections being made via NTLM where KERBEROS is expected; then we might have a SPN issue.

• We can provide a report, to the application managers, that validates connections, over a period of time, are encrypted. Giving them piece of mind.

• From a central server, we can capture information across multiple SQL instances. Instead of installing sp_whoisactive on each server, its local table, local agent job, etc.

[DougStevensGCPS]

Information can be obtained using the Get-DbaProcess function.
This contains similar output as Watch-DbaDBLogin. Includes additional fields such as AuthScheme, Encrption, etc.

A small script can be written to collect a list of SQL instances; preferably from a text file. Then produce a output that can be written to a table using Write-DbaDbTableData.