In Umbraco, the underlying logging framework Serilog plays a crucial role in capturing and managing log data. With its default configuration, it generates a JSON Umbraco log file that offers a more rich and structured logging experience. This article delves into the features and benefits of using Serilog for logging in Umbraco, focusing on the JSON log file format and its advantages for log analysis and correlation.

The Importance of Umbraco Logging

Structured Umbraco logs provides numerous advantages over traditional plain text log files, and Serilog, the Umbraco logging framework leverages the JSON log file format to unlock these benefits.

Let's dive deeper into each aspect:

The Power of Structured Logging

Structured Umbraco logging organizes log data into key-value pairs, which enhances readability, searchability, and analysis. Unlike plain text logs, structured logs allow for easier parsing and extraction of relevant information. Each log entry contains well-defined properties, making it simpler to filter logs based on specific criteria and perform targeted searches.

Enriched Logfile Content

Umbraco's JSON log file includes important details such as the Machine name and the date of each log entry. These details help identify the source of log events and enable better tracking and correlation of logs across different environments or instances. This becomes particularly useful in complex systems where multiple instances are deployed, as it allows for better log management and troubleshooting.

Improved Logfile Searchability

The structured nature of the JSON log file format significantly enhances searchability. Tools like Elasticsearch, Logstash, and Kibana, commonly known as the ELK stack, can be utilized to index and analyze log data efficiently. With structured logs, precise searches can be performed based on various criteria, including timestamps, log levels, or custom properties. This empowers developers and system administrators to pinpoint specific log events and extract meaningful insights quickly.

Correlation of Log Events

The JSON log file format enables easier correlation of log events, providing a comprehensive view of the system's behavior. By including relevant contextual information in each log entry, such as request IDs, user identifiers, or session IDs, it becomes simpler to trace and understand the flow of actions or errors across multiple log entries. Correlating log events aids in troubleshooting, diagnosing issues, and identifying the root causes of problems more effectively.

Customizing Serilog Configuration

Umbraco offers flexibility in customizing the Serilog configuration to meet specific logging requirements. Developers can modify log levels to control the verbosity of logs, define custom log sinks to direct logs to different targets (e.g., file, database, or external logging services), and enrich log entries with additional properties to capture relevant application-specific information. This customization ensures that the Umbraco logging setup aligns precisely with the application's needs and facilitates easier analysis and monitoring.

Log Levels

Serilog employs Umbraco log levels as a means of assigning importance to log events. These levels, ranging from least important to most critical, allow developers and system administrators to effectively categorize and prioritize log entries. Let's explore the different log levels in Serilog and their significance in the context of logging for a tech-savvy audience.


The Verbose log level is used for tracing information and debugging minutiae. It captures detailed information that is typically required in unusual or edge cases. Verbose-level logs are not typically enabled in production environments due to the high volume of log entries they can generate. However, they play a crucial role in investigating and resolving complex issues that may arise during development or in specific debugging scenarios.


The Debug log level is designed for internal control flow and diagnostic state dumps. It provides insights into the application's internal workings and facilitates the pinpointing of recognized problems. Debug-level logs capture detailed information that assists developers in understanding the application's behavior, tracking variables, and identifying potential issues. These logs are useful during the development and testing phases and are often disabled in production environments, except when troubleshooting specific problems.


The Information log level signifies events of interest or relevance to outside observers. It is the default minimum logging level enabled in many applications, including Umbraco. Information-level logs capture essential events that provide visibility into the system's normal operation, user interactions, or significant milestones. They offer valuable insights for monitoring, tracking system usage, and identifying patterns in the application's behavior.


The Warning log level indicates possible issues or service/functionality degradation. When something unexpected occurs that does not cause a critical failure but requires attention, a Warning-level log entry is generated. These logs serve as early indicators of potential problems, allowing developers and system administrators to investigate and take appropriate actions before they escalate. Warnings can include deprecated API usage, configuration inconsistencies, or unusual but non-critical events.


The Error log level represents a failure within the application or connected systems. It captures critical errors that impact the application's functionality or expected behavior. Error-level logs indicate that an operation or a feature did not succeed as intended and may require immediate attention. These logs are valuable for identifying and resolving issues that affect the system's reliability, data integrity, or user experience.


The Fatal log level represents critical errors that cause complete failure of the application. When a fatal error occurs, it signifies a severe problem that prevents the application from functioning correctly or at all. Fatal-level logs are typically logged just before an application terminates or crashes. These logs help in identifying and addressing catastrophic failures that require urgent investigation and resolution.

By utilizing different log levels, Serilog empowers developers and system administrators to prioritize and focus their attention on the most critical aspects of application behavior. Properly categorizing log events according to their importance enables efficient log analysis, troubleshooting, and problem resolution. It also assists in identifying patterns, improving system reliability, and ensuring a smooth user experience.

In Conclusion

The power of Serilog and its log levels truly shines. The ability to capture, structure, and categorize log events provides developers and system administrators with a comprehensive view of their application's behavior. Whether it's tracing intricate details, diagnosing internal control flow, or identifying critical errors, Serilog's log levels offer a roadmap to navigate the intricacies of application development and maintenance.

To leverage the full potential of Umbraco logging and Serilog's capabilities, consider partnering with a trusted technology partner like Saffron Tech. Our experienced team specializes in Umbraco development and can help you implement robust logging practices that align with your specific business needs. From fine-tuning log configurations to harnessing the insights derived from log analysis, Saffron Tech is here to elevate your Umbraco logging experience.

Don't let your logs go unnoticed or underutilized. Take the next step in optimizing your Umbraco application's performance, reliability, and user experience. Contact Saffron Tech today and unlock the true power of Umbraco logging.

Subscribe to Saffron Tech

Explore your marketing zen with our newsletter! Subscribe now.