Setup & access .NET logs
Zerops provides 3 different logs:
How to access logs​
Build log​
Zerops GUI​
To access a build log in Zerops GUI, go to the service detail and choose Service dashboard & runtime containers in the left menu. Then open the pipeline detail of an application version and click on Build log. The build log button is available only if the build pipeline was triggered for the selected deploy.
zCLI​
To access a build log in Zerops CLI use
Read more about the zcli service log command.
Prepare runtime log​
Zerops GUI​
To access a prepare runtime log in Zerops GUI, go to the service detail and choose Service dashboard & runtime containers in the left menu. Then open the pipeline detail of an application version and click on Prepare runtime log. The prepare runtime log button is available only if the prepare runtime pipeline was triggered for the selected deploy.
zCLI​
Prepare runtime log is currently not supported in zCLI.
Runtime log​
Zerops GUI​
To access a runtime log in Zerops GUI, go to the service detail and choose Runtime log in the left menu.
// TODO screenshot
Each runtime container has its own log. If your service has multiple containers, select the container in the log header.
You can filter log records by minimum severity or by time.
zCLI​
To access the log of the runtime containers in Zerops CLI use
Read more about the zcli service log command.
.NET logging configuration​
Zerops logs all messages sent
- to the standard error (
stderr
) - to the standard output (
stdout
) - via the .NET
Console
logging provider andLog{LogLevel}
method
Severity level​
By default the Log{LogLevel}
methods create messages with the Informational (6)
severity.
Add a severity number in the <N>
format as a prefix to set a custom severity as shown below:
builder.Logging.AddConsole();
var app = builder.Build();
app.Logger.LogInformation('A message with the informational severity ...');
app.Logger.LogInformation('<0>Emergency (0) severity > system is unusable.');
app.Logger.LogInformation('<1>Alert (1) severity > action must be taken immediately.');
app.Logger.LogInformation('<2>Critical (2) severity > critical conditions.');
app.Logger.LogInformation('<3>Error (3) severity > error conditions.');
app.Logger.LogInformation('<4>Warning (4) severity > warning conditions.');
app.Logger.LogInformation('<5>Notice (5) severity > normal, but significant, condition.');
app.Logger.LogInformation('<6>Informational (6) severity > informational message.');
app.Logger.LogInformation('<7>Debug (7) severity > debug-level message.');
logger.LogTrace
, logger.LogInformation
,
logger.LogWarning
, logger.LogDebug
, logger.LogError
and logger.LogCritical
are just aliases to the logger.LogInformation
method. They don't set the appropriate severity number. Use the <N>
prefix instead. :::