By Kimserey Lam with

Serilog Setup For Multi Environments

Jun 29th, 2018 - written by Kimserey with .

Few months ago we saw how to get started with Serilog. We discovered what was Serilog and the different concepts of settings, enrichers and sinks. Today we will see how we can take Serilog further and configure a logging mechanism for an application running in multi environment.

1. Setup Serilog
2. Multi environment
3. AWS CloudWatch

1. Setup Serilog

If you have never seen Serilog before you can start with my previous post on How to get started with Serilog.

In order to configure our first logging mechanism, we start by creating an AspNet Core application and install Serilog, Serilog.AspNetCore and the sinks we will be using Serilog.Sinks.Console, Serilog.Sinks.File.

RollingFile sink also exists but it has been superseded with File sink.

Next we can configure the logger to write to Console and write to a file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
public static IWebHost BuildWebHost(string[] args)
{
return WebHost.CreateDefaultBuilder(args)
.UseSerilog((builder, cfg) =>
{
cfg
.MinimumLevel.Debug()
.MinimumLevel.Override("Microsoft", LogEventLevel.Information)
.WriteTo.Console(
theme: AnsiConsoleTheme.Code,
outputTemplate: "[{Timestamp:HH:mm:ss.fff} {Application} {Level:u3}][{RequestId}] {SourceContext}: {Message:lj}{NewLine}{Exception}"
)
.WriteTo.File(
formatter: new CompactJsonFormatter(),
path: "C:/log/myapp/myapp.log",
fileSizeLimitBytes: 10485760,
rollOnFileSizeLimit: true,
retainedFileCountLimit: 3
);
})
.UseStartup<Startup>()
.Build();
}


We have set the minimun level of the logs to Debug and have overwritten Microsoft to only provide Information level. We have also configure two sinks, the Console sink to write with the format [{Timestamp:HH:mm:ss.fff} {Application} {Level:u3}][{RequestId}] {SourceContext}: {Message:lj}{NewLine}{Exception} and using the theme AnsiConsoleTheme.Code and the File sink which we have configured to rotate files on size limit and keep only 3 files.

Once we run the applicatiom, we should now be able to see the logs from the Console and, at the same time, logs should flow into files at the path specified.

2. Multi environment

So far we are logging to the Console and in a file with a Debug minimim level. While having a Debug level is great in development, it is best to restrict to Information the log level for our production environment. Similarly for the sinks, it is best to log to Console only for development hence what we need is two configurations:

1. development, with Debug log level and Console sink
2. production, with Information log level and File sink

AspNet Core already ship with a powerful configuration framework which we can leverage using Serilog.Settings.Configuration.

If you haven’t used AspNet Core configuration, you can have a look at my previous post where I briefly touch on the Configuration framework.

We start by installing the package and setup Serilog using configuration:

1


Next we setup the appsettings.development.json to include the settings which will be used in development:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
{
"serilog": {
"MinimumLevel": {
"Default": "Debug",
"Override": {
"Microsoft": "Information"
}
},
"WriteTo": [
{
"Name": "Console",
"Args": {
"theme": "Serilog.Sinks.SystemConsole.Themes.AnsiConsoleTheme::Code, Serilog.Sinks.Console",
"outputTemplate": "[{Timestamp:HH:mm:ss.fff} {Application} {Level:u3}][{RequestId}] {SourceContext}: {Message:lj}{NewLine}{Exception}"
}
}
]
}
}


And we create a appsettings.production.json which will be used for production:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
{
"serilog": {
"MinimumLevel": "Information",
"WriteTo": [
{
"Name": "File",
"Args": {
"path": "/var/log/myapp/myapp.log",
"fileSizeLimitBytes": 10485760,
"rollOnFileSizeLimit": true,
"retainedFileCountLimit": 3
}
}
]
}
}


When we run now it should only write to Console and no longer to the file when ASPNETCORE_ENVIRONMENT is set to 1 development or it should only write the file and no longer to the Console if the environment is production. The behavior should apply too to the log level.

Note that the path given is a linux path for an AspNet Core application hosted on linux.

3. AWS CloudWatch with structured logs

Having the logs written into a file is great to be able to debug in a offline manner as we can refer back to the logs.

Before being written to the file, Serilog logs are actually in a object form called a structured log This native form is very useful as it allows to provide full control to the receiver of the log to decide how they wish to deal with the log. For example, AWS CloudWatch supports reading json logs which we can then be used to inspect logs in a more efficient way then pure text.

We start first by adding a formatter for the file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
{
"serilog": {
"MinimumLevel": "Information",
"WriteTo": [
{
"Name": "File",
"Args": {
"formatter": "Serilog.Formatting.Compact.CompactJsonFormatter, Serilog.Formatting.Compact",
"path": "/var/log/myapp/myapp.log",
"fileSizeLimitBytes": 10485760,
"rollOnFileSizeLimit": true,
"retainedFileCountLimit": 3
}
}
]
}
}


We also install Serilog.Formatting.Compact which provides CompactJsonFormatter, a formatter which reduce the overal log file size allowing us to log more.We also change the file extension to .json since it is now a json file. Once we run the application we can see that the logs are no longer text but json objects on each lines.

Assuming that we have deployed our application on a ec2 instance, we can now install the CloudWatch agent on our server and configure it to ship the content of our logs to CloudWatch.

We start first by adding an IAM Role with a CloudWatchAgentServerPolicy policy attached and attach the role to our ec2 instance. This role will allow the instance to access CloudWatch to use the agent to create log groups, log streams and write logs into the log streams. Installing the agent can be done by downloading the zip file and extracting it:

1
2
3
4
5
6
wget https://s3.amazonaws.com/amazoncloudwatch-agent/linux/amd64/latest/AmazonCloudWatchAgent.zip
cd ~
mkdir tmp
cd tmp
unzip AmazonCloudWatchAgent.zip
sudo ./install.sh


Once installed, we can remove the folder and navigate to /opt/aws/amazon-cloudwatch-agent/etc and we can create a configuration file called config.json, the documentation for the configuration can be found on the official documentation:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
{
"logs": {
"logs_collected": {
"files": {
"collect_list": [
{
"file_path": "/var/log/myapp/*.log",
"log_group_name": "myapp",
"log_stream_name": "myapp",
"timezone": "UTC",
"timestamp_format": "%Y-%m-%dT%H:%M:%S"
}
]
}
},
"log_stream_name": "default"
}
}


The timezone needs to be set to UTC else it will take the region timezone. The timestamp_format needs to correspond to the log time, Serilog will print the time as "@t": "2018-06-16T10:55:02.8853229Z", therefore our timestamp will be %Y-%m%dT%H:%M:%S. It is important to set the timestamp else the injestion time will be used as timestamp which will not correspond to the time when the log actually occured. It is possible to setup more log streams by adding another item in the collect_list. Once we are done, we can configure the agent by running the following command:

1
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -c file:/opt/aws/amazon-cloudwatch-agent/etc/config.json -s


Once this is done, we can check the status of the service and start it if not yet started:

1
2
sudo systemctl status amazon-cloudwatch-agent
sudo systemctl start amazon-cloudwatch-agent


Once we are done we should be able to see the log flowing into CloudWatch under the log group we specified and under the log stream specified. The advantage of providing Json over plain text is the capabilities offered by CloudWatch to filter on property of the Json object like { \$.ElapsedTimeMilliseconds > 200 }. The full filter documentation can be foudn on the official documentation.

Conclusion

Today we saw how we could use Serilog to construct and saved logs as structured logs. We saw how we could configure different outputs depending on the environment where we were running under, console for development and file for production. Lastly we saw how we could save the log as structured json log which we saved into AWS CloudWatch. AWS CloudWatch then makes it easy to navigate and run some query through the CloudWatch interface on the json logs. Hope you liked this post, see you next time!

Designed, built and maintained by Kimserey Lam.