I don't think monitoring blade will help you here. But of course you can give it a try.
What you can do, if you have Application Control blade available:
Create different rules for TLS 1.0, TLS 1.1, TLS 1.2.
In these rules, use custom tcp objects where you set the protocol approprietly (TLS10, TLS11, TLS12) AND enable the "Protocol Signature" checkbox in the advanced tab of these service objects.
Then you can observe the hits on that rules. With using one service object per rule, you can use the rule hitcount as fast indicator. If that is not needed because you do log analysis anyway, you can put all three objects in rule because you will see which object has matched in the log entry. But you need to make sure your traffic is handled by a rule, where these objects are used. Otherwise, other objects (like the default https or "tls1.0" will match).