[LogRedac] User data exposed in query error messages

While looking at longevity logs against 5.5.0-1911, came across these messages in the logs:

_time=2018-02-19T07:48:08.350-08:00 _level=ERROR _msg=Failed to perform <ud>insert</ud> on key <ud>1.7115</ud> for Keyspace STOCK Error Duplicate Key 1.7115
_time=2018-02-19T07:48:08.351-08:00 _level=ERROR _msg=Failed to perform <ud>insert</ud> on key <ud>1.7116</ud> for Keyspace STOCK Error Duplicate Key 1.7116
_time=2018-02-19T07:48:08.358-08:00 _level=ERROR _msg=Failed to perform <ud>insert</ud> on key <ud>1.7117</ud> for Keyspace STOCK Error Duplicate Key 1.7117
_time=2018-02-19T07:48:08.360-08:00 _level=ERROR _msg=Failed to perform <ud>insert</ud> on key <ud>1.7119</ud> for Keyspace STOCK Error Duplicate Key 1.7119
_time=2018-02-19T07:48:08.361-08:00 _level=ERROR _msg=Failed to perform <ud>insert</ud> on key <ud>1.7120</ud> for Keyspace STOCK Error Duplicate Key 1.7120

Questions:

1. Why is insert that is part of query syntax user data?
2. Why is keyspace STOCK not being tagged as user data?

Problem:

The key which was tagged by query has anyways been exposed in the error message - it should be tagged in error messages too