There are some red fags over here, especially with "just implementing partitioning in production"!
You need to prepare for this all !! As jeff statted, it may not always be a win situation !
Your applications will keep on working, however, maybe not at the same speed !!
Since this is involving a logging table, one good thing is you are migrating to a now partitioned table, so you can load it, except for the newest rows, during normal operation time of your applications. Doing it this way, you only need to copy the last portion of "current" rows during the actual down time.
In our case, the partitioning function acts on datetime2 columns and pratitions on a per month basis.
For us, the most important reason for partitioning is to be able to delete the data without much overhead, hence by truncating a full partition at once.
We prepare for a couple of months up front, so we still have time to react is things fail.