We are currently use azure scale set (many VMs on one source group with load balance and one availability set), we used to use NLog to log our web app action and errors, but now we asked/needs to use Elastic Search and also use centralized log for all azure vm instances instead of file per each instance.
I am new to ES and LogStash concepts, Do I need to replace NLog with something else? and How I move to use ES and unify all logs in one (I think to make nlog store in azure storage table as unify results or do I needs to use LogStash or you prefer something else)?
What is the most logging that give support for .net core app on azure multi VMs as described above?
Any help please?
For NLog there is a target "NLog.Targets.ElasticSearch" (nuget) which uses the Elasticsearch.Net package.
Usage:
Docs for the parameters: https://github.com/ReactiveMarkets/NLog.Targets.ElasticSearch/wiki
Please note:
Since you want to log into
ElasticSearch
, it's best if you use a Logging framework which supports Structured Logging which for NLog this feature is inbetaRTM.You can
Serilog
as your Logging Framework which supports Structured Logging.And there's also Serilog sink for Elasticsearch https://github.com/serilog/serilog-sinks-elasticsearch
You should add these nuget packages to your project :
This is a sample code for config of serilog to sink to Elasticsearch
Many recommends that the application should not write directly to ElasticSearch, but should just write to local files.
Then have a service (Ex. FileBeat) to upload the contents of the log-files into ElasticSearch.
This will optimize network traffic to the ElasticSearch instance (bulk), and will ensure logging is not lost if problems with the network or ElasticSearch instance is restarted because of maintenance.