Allow disabling the log database

[onedr0p]

Is there an existing issue for this?

• I have searched the existing open and closed issues

Is your feature request related to a problem? Please describe

I am using Radarr with Postgres and it's a bit inconvenient to have to have 2 databases per instance of Radarr. In my setup I have logs via stdout which are also going to a log aggregator (Loki), Radarr also writes the logs to disk and writes logs to another database. I don't see the need to have 3 places for the logs.

Describe the solution you'd like

It would be awesome if there was a way in the config.xml to disable the log database completely and disable any feature in the app that relies on it.

Describe alternatives you've considered

There really isn't any alternative.

Anything else?

N/A

[onedr0p]

Maybe this is more inclusive to the logs sqlite database too. A single option to disable the logs database no matter if you are using sqlite or postgres would be great.

[Ornias1993]

Adding to this:
postgresql for logs seems like a weird choice to begin with.

But completely agree, we've gone back to sqlite for TrueCharts, partly due to forcing a second db just for logs.

[sillock1]

The only thing I can see that is going to block this work will be the UpdateHistory table in the log database that's used by the frontend to display previously installed versions.
Any chance this table could get moved to the main database?

Otherwise there's no reason why the DI registration can't conditionally register the logging database and migration scripts based on an environment variable.

[bakerboy448]

One day maybe / blocked upstream Sonarr/Sonarr#6743 (comment)

[onedr0p]

There is already a PR open here and @sillock1 is aware that the PR should be opened/merged on Sonarr first before it trickles down to the other arrs.