We understand the issue with adding the custom field but our use case is:
We have structured log (JSON) written into Azure blob storage by azure websites.
For ex:
{
"Timestamp": "2016-06-30T20:39:51.6714837-07:00",
"Level": "Error",
"MessageTemplate": "Error running test silo worker role.",
"Exception": "System.Exception: Silo failed to start correctly - aborting\r\n at Orleans.Runtime.Host.AzureSilo.RunImpl(Nullable`1 cancellationToken)\r\n at Orleans.Runtime.Host.AzureSilo.Run()\r\n at TestSilo.WorkerRole.Run() in C:\\src\\upgrade-to-1.0rtm\\test\\TestSilo\\WorkerRole.cs:line 39",
"Properties": {
"loggerMethod": "_errorRunningWorkerRole",
"activityId": "00000000-0000-0000-0000-000000000000",
"EventId": {
"Id": 1013
},
"SourceContext": "TestSilo.WorkerRole"
}
}
But Azure websites are adding an overhead to the JSON its own properties:
Message: EventName="MessageEvent" Message="{"Timestamp":"2016-06-30T20:39:51.6714837-07:00","Level":"Error","MessageTemplate":"Error running test silo worker role.","Exception":"System.Exception: Silo failed to start correctly - aborting\r\n at Orleans.Runtime.Host.AzureSilo.RunImpl(Nullable`1 cancellationToken)\r\n at Orleans.Runtime.Host.AzureSilo.Run()\r\n at TestSilo.WorkerRole.Run() in C:\\src\\upgrade-to-1.0rtm\\test\\TestSilo\\WorkerRole.cs:line 39","Properties":{"loggerMethod":"_errorRunningWorkerRole","activityId":"00000000-0000-0000-0000-000000000000","EventId":{"Id":1013},"SourceContext":"TestSilo.WorkerRole"}}" TraceSource="WaWorkerHost.exe"
Therefore, we want our JSON to be indexed rather than with the other additional properties being added to it.
Please let me know if additional details are required.
... View more