As a rule, there is no right or wrong answer.
Fast data recording, any solution will be fine, although you did not say how much per second you store. Both solutions have everything you need to pay attention to.
Search (very fast) across all columns. For small volumes, say a few hundred Gb, then any solution would be Ok (assuming experienced people put it together). You really did not say how fast / often you search, so if it is many times a minute, this consideration becomes more important. A quick search often slows down the ability to quickly record large volumes because the indexes needed for a search need to be updated.
Audit reports usually have a time component, so a limited time search, for example, over the last 7 days, will significantly speed up the search time compared to searching for all records.
Reporting When you get up to 100Tb, you will need some real tricks or a big budget to get a report quickly. For static reporting, you are likely to end up creating one program that generates several reports at once to save I / O. Dynamic reports will be complex.
My opinion? Since you know the DBMS, I will start with this as a method and submit a solution. This will buy you time to study the real problems that you will encounter (the lack of premature optimization that many people at SO are so keen on). During this initial period of time, you can begin to choose nosql solutions and study them. I assume that you want to run your own hardware / database if you want to use cloud-type solutions, then go straight to them right away.