Shyju Krishnankutty
Shyju Krishnankutty
Question: Is this a problem only for this specific logger/use case? Other loggers/environments does not have this problem of data service not getting the data fast enough?
@Hector47 Do you have any[ life cycle management policy](https://docs.microsoft.com/en-us/azure/azure-functions/storage-considerations?tabs=azure-cli#lifecycle-management-policy-considerations) enabled which cleans up your storage blobs periodically? You should exclude the storage used by function app from that.
> The issue [Azure/azure-functions-dotnet-worker#832](https://github.com/Azure/azure-functions-dotnet-worker/issues/832), was opened by someone looking specifically for retry logic for CosmosDBTrigger and @kshyju offered the linked comment as the solution. That issue should be updated to...
@ealsur Yes, Same list. The logic is somewhere in the functions host I believe.
> @kshyju , thanks for your response. The retry behavior you depict above is/will be permanent in the runtime for out-of-proc functions? > > I opened this issue since as...
The retry behavior is currently a preview feature. As the deprecation notice mentions, this feature will only be available for Timer and EventHub triggers for GA. Preview features are considered...
Hi @Yashuaa 👋 Where are you seeing this log messages? How does your `Logging` or `LogLevel` settings configured? You should be able to update the log level for any logger...
@Yashuaa Can your host.JSON, specifically the logging portion of the JSON. Also, Is this is a V3 app or V4? In-proc or isolated?
@Yashuaa Can your host.JSON, specifically the logging portion of the JSON?