Questions tagged [semantic-logging]

Designed to provide to .NET developers a strongly-typed (semantic) logging approach, making it easier to consume logging information, especially when there is a large volume of log data to be analyzed.

What is Semantic Logging?

Semantic Logging (formerly know at the Semantic Logging Application Block or SLAB) is designed by the patterns & practices team to help .NET developers move from the unstructured logging approach towards the strongly-typed (semantic) logging approach, making it easier to consume logging information, especially when there is a large volume of log data to be analyzed. When used out-of-process, Semantic Logging uses Event Tracing for Windows (ETW), a fast, lightweight, strongly typed, extensible logging system that is built into the Windows operating system.

Semantic Logging enables you to use the EventSource class and semantic log messages in your applications without moving away from the log formats you are familiar with (such as database, text file, Azure table storage). Also, you do not need to commit to how you consume events when developing business logic; you have a unified application-specific API for logging and then you can decide later whether you want those events to go to ETW or alternative destinations.

How do I use Semantic Logging?

Official releases are available via NuGet. You can also head to msdn.com for additional information, documentation, videos, and hands-on labs.

Building

To build the solution, clone the Github repo and run msbuild.exe from the project’s build folder. You'll need to use the Visual Studio Developer Command Prompt. Some of the unit tests require a SQL database.

How do I contribute?

See CONTRIBUTING.md in for more details.

Release notes

Release notes in each release are available.

You can use its Gitter for quick questions.

36 questions
0
votes
0 answers

Semantic Logging with Enterprise Library 6 out-of-process

I've migrated to Enterprise Library 6 with semantic logging. It works fine with in process logging, but I could not get out-of-process logging working. SemanticLogging SVC is started as Windows Service, and I know it's working fine because I could…
K232
  • 1,040
  • 14
  • 36
0
votes
2 answers

The schema of EventEntry was not updated using out-of-process semantic logging

I write a custom EventSource class and add a method for log as below: [EventSource(Name = "MyCompany")] public class MyCompanyEventSource : EventSource { [Event(6, Message = "test.", Keywords = Keywords.Perf, Level =…
capcom923
  • 638
  • 5
  • 15
0
votes
1 answer

What Tools are best suited for viewing Semantic Logs with Azure Table Sink?

I've setup my application to use Semantic Logging and Azure sink. What I see in the tables looks great and I'm pretty happy with what I'm seeing. My issue is that I'd really like to filter and search these logs. For example, I am currently logging a…
Mike Bynum
  • 763
  • 2
  • 10
  • 22
0
votes
2 answers

Runtime configuration of EventSource guid

We have a scenario whereby multiple pre-release versions of an application run in the same environment. The problem we're seeing is that, because our EventSource has the same name/guid, we cannot differentiate between logs. Is it possible to…
Richard Szalay
  • 83,269
  • 19
  • 178
  • 237
0
votes
2 answers

How does an out-of-process semantic logging service receive events?

The reason I'm asking is I would like to use the out-of-proc mode, but I cannot install a service on each user's workstation, only on a central server. Is the communication between event source and listener service an ETW thing, or is there some…
ProfK
  • 49,207
  • 121
  • 399
  • 775
0
votes
1 answer

Semantic logging vs wad logs table

I want to decide between semantic logging for azure vs traditional logging where all logs use to go to wadlogs table. Is there any specific reason we should go for one or other? what is the difference between two and which one is preferable?
1 2
3