Operations | Monitoring | ITSM | DevOps | Cloud

December 2022

NGINX Logging | Configuring Error and Access Logs, Sending Nginx Logs to Syslog & more

NGINX is a prominent web server, reverse proxy server, and mail proxy utilized by many websites and applications to serve content to their users. One important aspect of managing a web server is logging, which refers to the process of recording information about the server's activity and performance. In NGINX, logging is done using the error_log and access_log directives. error_log directive specifies the file where NGINX should log errors.

What are SysLog formats? How to use them?

Syslog is a standard for message logging that allows devices such as routers, switches, and servers to send event messages to a central log server. The messages sent by these devices are known as syslog messages and include information such as the date, time, device hostname, and message content. Syslog was originally developed as a part of the BSD operating system, but many other operating systems and network devices have since adopted it.

Logs UI | An intuitive UI for Log Management

A logs UI is a user interface for displaying log data. Logs are records of events that happen on a computer system, such as messages indicating that a particular operation has been performed or an error has occurred. A logs UI typically allows a user to view and search through log data and may also provide features such as filtering and highlighting to help the user find specific log entries of interest.

Logging as a service | Log Management with Open Source

Logging as a service (LAAS) is a type of cloud computing service that allows organizations to store and manage their log data in a central location. This type of service typically includes features such as centralized storage, real-time analytics, and search capabilities, as well as tools for visualizing and analyzing log data. Logs help you debug and troubleshoot your applications. They are also useful for other purposes like auditing and compliance, performance monitoring, and security.

Client logging | Best practices and examples

Client logging refers to the practice of collecting and storing log messages generated by client software, such as a web browser or mobile application. These log messages can provide valuable information about the behavior and performance of the client software, as well as any errors or issues that may have occurred. Client logging is often used by developers to troubleshoot and debug software issues, as well as to gather data for analysis and performance optimization.

Morgan Logger | Tutorial on how to use in an Express application

Morgan is a popular HTTP logging library for Node.js. It is designed to be a simple and flexible tool for logging HTTP requests and responses in Node.js applications. Using Morgan, you can easily log requests made to your Node.js server, including information such as the request method, the URL of the request, the status code of the response, and the length of the response body. You can also customize the format of the log messages and specify which requests should be logged and which should be ignored.

JSON Logs | Best Practices, benefits, and examples

JSON (JavaScript Object Notation) is a lightweight data-interchange format that has gained widespread popularity in recent years due to its simplicity and flexibility. It is easy for humans to read and write and for machines to parse and generate, making it a great choice for transmitting data in web applications. Logs serve multiple purposes for application developers. They are essential to understand what's happening in your application.

SigNoz - Logs Performance Benchmark

Logs are an integral part of any system that helps you get information about the application state and how it handles its operations. The goal of this blog is to compare the commonly used logging solutions, i.e., ElasticSearch(ELK stack) and Loki(PLG stack), with SigNoz on three parameters: ingestion, query, and storage. Performance benchmarks are not easy to execute. Each tool has nuances, and the testing environments must aim to provide a level playing field for all tools.

Docker Container Lifecycle Tutorial | Create, Run, Pause, Stop, Kill

In this tutorial, we will learn about Docker container lifecycle. But first, let me share a personal anecdote. On a hot summer afternoon in 2021, my manager called me out of the blue and said, “Muskan, the project file you shared with me is not working on my machine. Could you please come over and fix the setup? It’s really urgent.” I rushed to his cabin and tried my best but could not fix the dependencies issues.

API Monitoring in SigNoz - Monitoring Key APIs with Dashboards

More about SigNoz: SigNoz - Monitor your applications and troubleshoot problems in your deployed applications, an open-source alternative to DataDog, New Relic, etc. Backed by Y Combinator. SigNoz helps developers monitor applications and troubleshoot problems in their deployed applications. SigNoz uses distributed tracing to gain visibility into your software stack. If you need any clarification or find something missing, feel free to raise a GitHub issue with the label documentation or reach out to us at the community slack channel.

Ability to import Grafana dashboards, Alerts based on ClickHouse queries and more advanced features - SigNal 19

Welcome back to our monthly product updates - SigNal! Last month, the SigNoz team shipped many advanced features that will help our users take observability to the next level. With our newly shipped alerts based on ClickHouse queries, users will have the flexibility to set alerts on all three telemetry signals - logs, metrics, and traces. We made two important releases, presented a talk at one of the top DevOps conferences, and made plans for upcoming releases.

FluentD vs Logstash - Choosing a Log collector for Log Analytics

When we have large-scale, distributed systems, Logging becomes essential for observability, monitoring, and security. No matter what architecture (Monolith/Microservices) our systems have, they are complex due to the number of moving parts they have and the challenges they face around management, deployment, and scaling. In this scenario, Log management tools rescue the DevOps and SRE teams in order to help them monitor and improve performance, debug errors, and visualize events.