Having a transaction log larger than the associated data files would suggest that the transaction log is not being backed up frequecntly enough, or possibly ever!
There is a risk that if left uncontrolled it will fill up all available drive space.
The following Microsoft document provides a number of steps to halp manage your transaction logs: https://docs.microsoft.com/en-us/sql/relational-databases/logs/manage-the-size-of-the-transaction-log-file
Please look at the Disk Space tab in SQL Sentry (Not available in SQL Sentry Essentials) to see how much space is free in the Transaction Logs