logwarn | Utility for finding interesting messages in log files | Machine Learning library

This looks like an old LocalDB bug we hit once. I think it was fixed sometime after the initial 2017 release. Try updating to see if it goes away.

It seems like your REST client is not passing the user credentials along with the request. The Firebase SDK passes this information with each connection/request, and you'll have to do the same here.

Have a look at the Firebase documentation on authorizing REST requests, specifically the section on authenticating with an ID token, which is probably easiest for you.

On the other hand, I'd recommend having a look using using the Firebase Realtime Database SDK instead of calling the REST API, as this will pass the required information automatically.

In case response was null the line containing response[5] and response[6] would throw NullPointerException which means the if (response != null) will not be reachable when response is null.

If you remove or rewrite the line

securityLog.logInfo(LogInfoEvent.GENERAL_INFO, "Card Auth Resp : " + String.format("%02X ", response[5]) + " " + String.format("%02X ", response[6]));

to check for null response, then the if condition would not be redundant anymore.

Here is a discussion of other people experiencing similar issues regarding CA2254. Hopefull this will get addressed in future versions.

For the time being, my best solution is to ignore the warning.

The major difference of Log levels (like LogInformation, LogError, LogWarning, LogCritical, etc.,) is When you write traces from your application code, you should assign a log level to the traces. Log levels provide a way for you to limit the amount of data that is collected from your traces. Refer here

I have tried the way which you have followed to know the log level processing time.

Logging the error depends on the application code failure. If there are any unhandled exceptions in the azure functions these are handled by LogError only (Exception, exceptionMsg) but AppInsights don't see it was the failure.

• To Return the bit more meaningful full error message, I guess that's why for you it takes time to execute the error log.

Here I am adding the log levels to know the exact time taken to complete those log level iteration times. I cannot see any delay in log execution & depends on the Business logic written from our end prior to log execution.

As the error shows we should consume scope services in scoped instances to avoid data corruption or threading issue.

You should use Using ServiceScopeFactory to resolve scope instances.

Like this:

UHM I fixed it... in the weirdest possible way? I'm not sure at all what caused the issue, but if anybody knows it, please share. Some people could find it interesting.

Anyways, here is the fix:

It seems that you were missing a VPC Endpoint for DynamoDB, since your Glue Jobs run in a private VPC when you write to Redshift.

azure app service

This is almost certainly due to multiple instances of your app running.

What would be the safest way to have the backgroundservice running only once, beside going through some data persist / check in DB?

An external "lease" is the safest approach. You can build one yourself using CosmosDb / Redis as a backend, or you can use a built-in approach by factoring your background service out of your web app into either an Azure WebJob or an Azure Function. Both of those services use leases automatically for timer-triggered jobs.