No exception thrown when Refusing to schedule a batch in Limiting Scheduler, only warning is logged, causing data loss. about newrelic-telemetry-sdk-java HOT 5 OPEN

@nmala01 thanks for bringing this to our attention. We're not able to commit to changing this at the moment but it's a good suggestion

Since your code is fresh in your mind, would you be willing to provide a sample app that reproduces the problem?

from newrelic-telemetry-sdk-java.

Imagine if a logging framework threw an exception and ended up rolling back a transaction or ending a procedure early. It would not look good, and try/catch every log call is not feasible.

The point here is that both logging and New Relic are 3rd parties that should not prevent the main application from functioning.

That does not mean it is not a good idea to have a method that can allows to treatment of an exception.

So ideally there should be 2 methods:

• one that only logs;
• one that throws checked exceptions.

Implementation wise, the logging method should call the exception method, catch the exception, log it and continue the flow.

from newrelic-telemetry-sdk-java.

@meiao I understand that 3rd parties should not prevent main application from functioning, but data loss is such a crucial error that just logging it seems like a bug.
Also the option for logging or throwing exception can be handled using the NotificationHandler if appropriate exception get thrown to TelemetryClient.

from newrelic-telemetry-sdk-java.

https://issues.newrelic.com/browse/NEWRELIC-4094

from newrelic-telemetry-sdk-java.

Unfortunately, we were not able to prioritize this for the next (Jan-Mar) quarter. Will consider for a future quarter.

from newrelic-telemetry-sdk-java.