Combinations of logLevels in host.json can stop function projects starting #7493
Assignees
Labels
area-integrations
Issues pertaining to Aspire Integrations packages
azure
Issues associated specifically with scenarios tied to using Azure
azure-functions
Issues related to the Azure Functions integration
needs-author-action
An issue or pull request that requires more info or actions from the author.
Milestone
Comments
|
For got to add, that it always works when you run without debugging |
davidfowl
added
area-integrations
|
@perfectphase Thanks for filing this issue!
EDIT: I missed that you included the version in the configuration details. It seems like you are on 17.12? Can you trying 17.13 Preview 4 to help us confirm if this is the same as the other bug? |
captainsafia
added
the
needs-author-action
|
This submission has been automatically marked as stale because it has been marked as requiring author action but has not had any activity for 14 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
I'm currently in the process of migration one of our solutions to Aspire, it contains a function project that has very high throughput, so has a set of custom log levels in it's host.json. When we try to start the AppHost we end up in this state for a couple of minutes
finally moving to a failed to start state.
Expected Behavior
Function project expected to start regardless of long levels. Or at least with rational 'don't do this' guidelines
Steps To Reproduce
To repo this, we have created a new Aspire starter project from the public template and added a function project (default with timer-based function). We then started the project and ensured that everything started OK.
We then copied the log level section into the new test project's host.json
{ "version": "2.0", "logging": { "logLevel": { "Function.DeviceChangedIntegrationEventHandler": "Information", "Function.DeviceExtraInfoEventHandler": "Information", "Function.DeviceStateChanged": "Information", "Host.Results": "Information", "Host.Aggregator": "Information", "Default": "Information", "Microsoft": "Warning", "System": "Warning", "Azure.Messaging.ServiceBus": "Error", "Azure.Messaging.EventHubs": "Error" }, "applicationInsights": { "samplingSettings": { "isEnabled": true, "excludedTypes": "Request" }, "enableLiveMetricsFilters": true } } }After that the function host failed to start.
Through trial and error we found that removing the Default entry allows the project to start.
But we also found that this works
{ "version": "2.0", "logging": { "logLevel": { "Default": "Information", "Microsoft": "Warning", "System": "Warning" }, "applicationInsights": { "samplingSettings": { "isEnabled": true, "excludedTypes": "Request" }, "enableLiveMetricsFilters": true } } }but this does not
{ "version": "2.0", "logging": { "logLevel": { "Host.Results": "Information", "Host.Aggregator": "Information", "Default": "Information", "Microsoft": "Warning", "System": "Warning" }, "applicationInsights": { "samplingSettings": { "isEnabled": true, "excludedTypes": "Request" }, "enableLiveMetricsFilters": true } } }But this does
{ "version": "2.0", "logging": { "logLevel": { "Host.Results": "Information", "Host.Aggregator": "Information", "Default": "Information", "Microsoft": "Warning", "System": "Warning" } } }and so does this
{ "version": "2.0", "logging": { "logLevel": { "Host.Results": "Information", "Host.Aggregator": "Information" }, "applicationInsights": { "samplingSettings": { "isEnabled": true, "excludedTypes": "Request" }, "enableLiveMetricsFilters": true } } }In all cases the project starts correctly if launched directly rather than via aspire
So there must be some combination but have no idea on what the root cause is
Exceptions (if any)
After several minutes:
fail: Aspire.Hosting.Dcp.dcpctrl.ExecutableReconciler[0]
timeout of 120 seconds exceeded waiting for the IDE to start a run session; you can set the DCP_IDE_REQUEST_TIMEOUT_SECONDS environment variable to override this timeout (in seconds) {"Executable": {"name":"functionapp1-rvrnqgmb"}, "Reconciliation": 7, "error": "Put "https://localhost:50213/run_session?api-version=2024-04-23\": context deadline exceeded"}
.NET Version info
Versions: .net 9.0, aspire 9.0, functions 9.0.0-preview.5.24551.3, VS:17.12.4
Also tried on daily builds of 9.1 with same outcome.
Anything else?
startup log with "Aspire.Hosting.Dcp": "Trace"
The text was updated successfully, but these errors were encountered: