SQL Server database transaction logs contain multiple virtual log files, or VLFs. The number of VLFs is dictated by the initial size and auto-growth size for the transaction log. Too many VLFs can lead to increased backup/recovery times and possible performance problems.
If VLFs are too high, the count can be reset by shrinking and resizing the log. See the "8 Steps" article below for more details and scripts.
See Also:
https://www.sentryone.com/blog/create-advisory-conditions-for-sql-server-on-amazon-rds
http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/
http://www.sqlskills.com/blogs/kimberly/8-steps-to-better-transaction-log-throughput/