Enable additional logging using the application runtime environment - aspNetCore

The Application runtime environment parameter, "aspNetCoreEnvironment" can be set to Development, Staging, or Production. For example, once you set to Development, you should be able to see an exception stack trace in the Response section of the Chrome Developer Tool's Network tab.

Important: Remember to remove it once you're done with debugging the application, especially in Production.

Linux Swimlane Platform Installer (SPI)

On Swimlane Settings under logging, you can set the ASP.NET Hosting Environment:

Linux HA (Kubernetes / Helm)

Swimlane's Kubernetes Helm Chart version 0.9.0 and above has a parameter, 'aspnetcoreEnvironment', in the values.yaml for this purpose. There are three possible options to update the parameter value.

Option 1: Update values.yaml

Update the parameter value for aspnetcoreEnvironment to Development in the API section.

Run the following command to make the changes:

helm upgrade <RELEASE_NAME> <CHART_NAME> -f swimlane/secret-values-override.yaml

Option 2: Override by --set parameter

Set the value of aspnetcoreEnvironment to Development as part of the command:

helm upgrade <RELEASE_NAME> <CHART_NAME> -f swimlane/secret-values-override.yaml --set api.aspnetcoreEnvironment=Development

Option 3: Older Helm Chart

Swimlane Helm Chart Version 0.1.0 doesn’t have the `aspnetcoreEnvironment` parameter in values.yaml. It's best to update the chart, otherwise, follow the steps below:

Get the name of the swimlane-api deployment.

kubectl get deployments -n swimlane

Add the environment variable with:

kubectl set env deployments swimlane-api ASPNETCORE_ENVIRONMENT=Development

Now check the value of ASPNETCORE_ENVIRONMENT inside the swimlane-api deployment.

kubectl describe deployments swimlane-api | grep ASPNETCORE_ENVIRONMENT

Restart the api pods. The next pod created would pull in that environment variable.

# Scale down to 0 kubectl scale deployment swimlane-api --replicas=0

Wait for all pods to terminate.

kubectl get pods -n swimlane -w

Scale back to 3.

kubectl scale deployment swimlane-api --replicas=3

Wait for all pods to start back up again.

kubectl get pods -n swimlane

Now check to see if the value of ASPNETCORE_ENVIRONMENT has been updated inside the api pod.

kubectl exec <api pod name> env -n swimlane | grep ASPNETCORE_ENVIRONMENT