[FEATURE] Make error log for flag not found optionally a warning/disabled

[jcsawyer]

Requirements

Feature flags may not exist in production environments prior to CI/CD deployments.
The task of adding feature flags for us is tracked via external tools so an error log entry is needless and clogs our log monitors giving false positives, so a warning would be a sufficient level in this case.

It might even be nice to have the level entirely configurable for flag not found or disable it entirely.

[askpt]

Thanks for reporting this. Could you please provide some more details?
Please provide the log message and the providers that you are using at the moment so we can debug it better.

[jcsawyer]

We're using OTEL logging and the log message getting flooded is:

Error while evaluating flag feature-flag-name: FLAG_NOT_FOUND

While it makes sense that it should typically be an error (you want to know if you haven't added the feature flag, right?), and the simplest solution is to make sure the feature flag exists. But I think this couples the feature flag existing in prod too tightly to its implementation when using CI/CD as we're obviously checking the feature flag to see if the feature is enabled yet or not, so it's one of the first things added.

When we see these errors, they're logging errors multiple times a second which are triggering our monitors.