console 1.35.0 → 1.35.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '0498b53c4327442b097e48fac79fdb92b4bcb12df58c80aa2a28490ff5d36738'
-  data.tar.gz: 7960eed0fca16ba4ce614837ac861925565053cb6694d0a6107d27f89ce9042d
+  metadata.gz: e161d51958a96742a44541c862e32c9354c04d3cdae04cfe57ef0a63b2ecfd36
+  data.tar.gz: 48afe3e18acbc12cd72b96c22a139fd9de69e852c0ba8e98a4367811ca1e916e
 SHA512:
-  metadata.gz: d1248d88a76092de60f134b6deea1cb066edf2abb6d3bb040c8eada3801338e4e5f2139ffec9ca9a12a29a1d4e13a4b3083760979a9b16f1a498742b1d255c70
-  data.tar.gz: a8bf531686c47214706d623d9169b6718c6fc72f7e7517dffe7d048fcac86db6f0f4aa7f3d97cb9053287f906b401c113bea601b796e94b9ea5b9007e8e287f8
+  metadata.gz: 2caf9a3c2520460b7a54489bf4ed68a9f0f37223a45917500884b8f5a1c531ebb602a1dda943994925c716d9af785c11c07f2263704572db3ed343f9858c75a6
+  data.tar.gz: aaf33117df4b08e942b8975128bb11a11b653580c85dfe93218d5a4af0a16db69385d4907a37d461a3d3e89c6ef6578ecef4aaca3ec07e3d1d63c56c66111283

data/context/command-line.md

@@ -0,0 +1,47 @@
+# Command Line
+
+This guide explains how the `console` gem can be controlled using environment variables.
+
+## Environment Variables
+
+The following program, `app.rb` will be used to explain the different environmet variables:
+
+~~~ ruby
+#!/usr/bin/env ruby
+
+require 'console'
+
+class MyApplication
+	def do_work
+		Console.logger.debug(self, "Doing some work.")
+	end
+end
+
+Console.logger.debug(self, "Creating the application.")
+application = MyApplication.new
+application.do_work
+~~~
+
+### `CONSOLE_LEVEL=debug`
+
+Control the default logger level. You can set it to any of the supported log levels: `debug`, `info`, `warn`, `error`, `fatal`.
+
+By default, the debug level is not enabled, but you can enable it using `CONSOLE_LEVEL=debug`:
+
+<pre>&gt; <font color="#00AFFF">CONSOLE_LEVEL</font><font color="#00A6B2">=</font><font color="#00AFFF">debug</font> <font color="#005FD7">./app.rb</font>
+<font color="#00AAAA">  0.0s    debug:</font> <b>Object</b> <font color="#717171">[oid=0x3c] [ec=0x50] [pid=990900] [2022-10-12 17:28:15 +1300]</font>
+               | Creating the application.
+<font color="#00AAAA">  0.0s    debug:</font> <b>MyApplication</b> <font color="#717171">[oid=0x64] [ec=0x50] [pid=990900] [2022-10-12 17:28:15 +1300]</font>
+               | Doing some work.
+</pre>
+
+### `CONSOLE_DEBUG=MyClass,MyModule::MyClass`
+
+Enable debug logging for the specified class names. You can specify one or more class names which will be resolved at runtime. This is specifically related to subject logging.
+
+By default, the debug level is not enabled, but you can enable it for the specific `MyApplication` class using `CONSOLE_DEBUG=MyApplication`:
+
+<pre>&gt; <font color="#00AFFF">CONSOLE_DEBUG</font><font color="#00A6B2">=</font><font color="#00AFFF">MyApplication</font> <font color="#005FD7">./app.rb</font>
+<font color="#00AAAA">  0.0s    debug:</font> <b>MyApplication</b> <font color="#717171">[oid=0x64] [ec=0x78] [pid=991855] [2022-10-12 17:30:56 +1300]</font>
+               | Doing some work.
+</pre>

data/context/configuration.md

@@ -0,0 +1,23 @@
+# Configuration
+
+This guide explains how to implement per-project configuration for the `console` gem.
+
+## Configuration File
+
+The `console` gem can load a configuration file, by default `config/console.rb`. This file is evaluated in an instance of {ruby Console::Config} which allows you to override methods that implement the default behaviour for a given project.
+
+Here is an example configuration file:
+
+```ruby
+# config/console.rb
+
+# Override the default log level
+def log_level
+	:debug
+end
+
+# Override the default output
+def make_output
+	Console::Output::Datadog.new(Console::Output::Default.new)
+end
+```

data/context/events.md

@@ -0,0 +1,71 @@
+# Events
+
+This guide explains how to log structured events with a well-defined schema.
+
+## Overview
+
+Logs often fall into two categories:
+
+- Free-form logs which include some structured data, but are primarily text-based and used for debugging or troubleshooting.
+- Structured logs which are designed to be machine-readable and can be used for monitoring, alerting, auditing and analytics.
+
+Events are a type of structured log which are designed to be machine-readable and have a well-defined schema. They are used to represent a specific occurrence within a system, such as a request, a response, an error, or a warning. You can create custom events to represent any structured data you like.
+
+## Core Concepts
+
+- {ruby Console::Event::Generic} is the base class for all events.
+- {ruby Console::Terminal::Formatter} includes a collection of formatters for rendering specific events in a human-readable format.
+
+## Emitting Events
+
+To emit an event, you can create an instance of a specific event class and call the `#emit` method. For example, to emit a failure event:
+
+```ruby
+def handle_request
+	begin
+		# ... user code ...
+	rescue => error
+		Console::Event::Failure.for(error).emit(self, "Failed to handle request!")
+	end
+end
+```
+
+This will emit a failure event with the error message and backtrace.
+
+### Emitting Events with Different Severity Levels
+
+Events can have different severity levels, such as `:info`, `:warn`, `:error`, and `:fatal`. You can specify the severity level when emitting an event:
+
+```ruby
+Console::Event::Failure.for(error).emit(self, "Failed to handle request!", severity: :debug)
+```
+
+## Custom Events
+
+You can create custom events by subclassing {ruby Console::Event::Generic} and defining the schema for the event. For example, to create a custom event for tracking user logins:
+
+```ruby
+class UserLoginEvent < Console::Event::Generic
+	def self.for(request, user)
+		self.new(user.id, request.ip)
+	end
+	
+	def new(id, ip)
+		@id = id
+		@ip = ip
+	end
+	
+	def to_hash
+		{
+			# Specifying a type field is recommended:
+			type: :login,
+			
+			# Custom fields:
+			id: @id,
+			ip: @ip
+		}
+	end
+end
+
+UserLoginEvent.for(request, user).emit(self, "User logged in.")
+```

data/context/getting-started.md

@@ -0,0 +1,170 @@
+# Getting Started
+
+This guide explains how to use `console` for logging.
+
+## Installation
+
+Add the gem to your project:
+
+~~~ bash
+$ bundle add console
+~~~
+
+## Core Concepts
+
+`console` has several core concepts:
+
+- A log message which consists of a set of arguments and options, which includes a timestamp, severity, and other structured data.
+- The {ruby Console} module which provides an abstract interface for logging.
+- A {ruby Console::Logger} instance which is the main entry point for logging for a specific system and writes data to a given output formatter.
+- An output instance such as {ruby Console::XTerm}, {ruby Console::Serialized::Logger} which formats these log messages and writes them to a specific output device.
+- An event instance, such as {ruby Console::Event::Progress} or {ruby Console::Event::Spawn} which represents a structured event within a system, which can be formatted in a specific way.
+
+## Basic Logging
+
+Out of the box, {ruby Console}  provides a logger interface that outputs to the current terminal via `stderr`.
+
+~~~ ruby
+require 'console'
+
+Console.info("Hello World")
+~~~
+
+<pre>
+<font color="#00AA00">  0.0s     info:</font> <b>Hello World</b> <font color="#717171">[pid=219113] [2020-08-08 12:21:26 +1200]</font>
+</pre>
+
+The method name `info` indicates the severity level of the log message. You can filter out severity levels, and by default, `debug` messages are filtered out. Here are some examples of the different log levels:
+
+~~~ ruby
+require 'console'
+
+Console.debug("The input voltage has stabilized.")
+Console.info("Making a request to the machine.")
+Console.warn("The machine has detected a temperature anomaly.")
+Console.error("The machine was unable to complete the request!")
+Console.fatal("Depressurisation detected, evacuate the area!")
+~~~
+
+From the terminal, you can control the log level using the `CONSOLE_LEVEL` environment variable. To log all messages including `debug`:
+
+~~~ bash
+$ CONSOLE_LEVEL=debug ./machine
+~~~
+
+Alternatively to restrict log messages to warnings and above:
+
+~~~ bash
+$ CONSOLE_LEVEL=warn ./machine
+~~~
+
+If otherwise unspecified, Ruby's standard `$DEBUG` and `$VERBOSE` global variables will be checked and adjust the log level appropriately.
+
+## Metadata
+
+You can add any options you like to a log message and they will be included as part of the log output:
+
+~~~ ruby
+duration = measure{...}
+Console.info("Execution completed!", duration: duration)
+~~~
+
+## Subject Logging
+
+The first argument to the log statement becomes the implicit subject of the log message.
+
+~~~ ruby
+require 'console'
+
+class Machine
+	def initialize(voltage)
+		@voltage = voltage.floor
+		Console.info(self, "The input voltage has stabilized.")
+	end
+end
+
+Machine.new(5.5)
+~~~
+
+The given subject, in this case `self`, is used on the first line, along with associated metadata, while the message itself appears on subsequent lines:
+
+<pre>
+<font color="#00AA00">  0.0s     info:</font> <b>Machine</b> <font color="#717171">[oid=0x3c] [pid=219041] [2020-08-08 12:17:33 +1200]</font>
+               | The input voltage has stabilized.
+</pre>
+
+If you want to disable log messages which come from this particular class, you can execute your command:
+
+~~~ bash
+$ CONSOLE_FATAL=Machine ./machine
+~~~
+
+This will prevent any log message which has a subject of class `Machine` from logging messages of a severity less than `fatal`.
+
+## Exception Logging
+
+If your code has an unhandled exception, you may wish to log it. In order to log a full backtrace, you must log the subject followed by the exception.
+
+~~~ ruby
+require 'console'
+
+class Cache
+	def initialize
+		@entries = {}
+	end
+	
+	def fetch(key)
+		@entries.fetch(key)
+	rescue => error
+		Console.warn(self, "Cache fetch failure!", error)
+	end
+end
+
+Cache.new.fetch(:foo)
+~~~
+
+This will produce the following output:
+
+<pre><font color="#C01C28">  0.0s    error:</font> <b>Cache</b> <font color="#8B8A88">[oid=0x848] [ec=0x85c] [pid=571936] [2024-05-03 10:55:11 +1200]</font>
+               | Cache fetch failure!
+               |   <font color="#C01C28"><b>KeyError</b></font>: <b>key not found: :foo (</b><u style="text-decoration-style:solid"><b>KeyError</b></u><b>)</b>
+               |   → <font color="#C01C28">test.rb:15</font> in `fetch&apos;
+               |     <font color="#C01C28">test.rb:15</font> in `fetch&apos;
+               |     <font color="#C01C28">test.rb:21</font> in `&lt;top (required)&gt;&apos;
+</pre>
+
+## Program Structure
+
+Generally, programs should use the global `Console` interface to log messages.
+
+Individual classes should not be catching and logging exceptions. It makes for simpler code if this is handled in a few places near the top of your program. Exceptions should collect enough information such that logging them produces a detailed backtrace leading to the failure.
+
+### Multiple Outputs
+
+Use `Console::Split` to log to multiple destinations.
+
+``` ruby
+require "console"
+require "console/output/split"
+
+terminal = Console::Output::Terminal.new($stderr)
+serialized = Console::Output::Serialized.new(File.open("log.json", "a"))
+Console.logger = Console::Logger.new(Console::Output::Split[terminal, serialized])
+
+Console.info "I can go everywhere!"
+```
+
+### Custom Log Levels
+
+`Console::Filter` implements support for multiple log levels.
+
+``` ruby
+require "console"
+
+MyLogger = Console::Filter[noise: 0, stuff: 1, broken: 2]
+
+# verbose: true - log severity/name/pid etc.
+logger = MyLogger.new(Console.logger, name: "Java", verbose: true)
+
+logger.broken("It's so janky.")
+```

data/context/index.yaml

@@ -0,0 +1,28 @@
+# Automatically generated context index for Utopia::Project guides.
+# Do not edit then files in this directory directly, instead edit the guides and then run `bake utopia:project:agent:context:update`.
+---
+description: Beautiful logging for Ruby.
+metadata:
+  documentation_uri: https://socketry.github.io/console/
+  funding_uri: https://github.com/sponsors/ioquatix/
+  source_code_uri: https://github.com/socketry/console.git
+files:
+- path: getting-started.md
+  title: Getting Started
+  description: This guide explains how to use `console` for logging.
+- path: command-line.md
+  title: Command Line
+  description: This guide explains how the `console` gem can be controlled using environment
+    variables.
+- path: configuration.md
+  title: Configuration
+  description: This guide explains how to implement per-project configuration for
+    the `console` gem.
+- path: integration.md
+  title: Integration
+  description: This guide explains how to integrate the `console` output into different
+    systems.
+- path: events.md
+  title: Events
+  description: This guide explains how to log structured events with a well-defined
+    schema.

data/context/integration.md

@@ -0,0 +1,37 @@
+# Integration
+
+This guide explains how to integrate the `console` output into different systems.
+
+## Output Redirection
+
+The `console` is primarily an interface for logging, with a general purpose implementation which can log to a terminal (human readable) or a file (JSON by default). Output can also be augmented, redirected or manipulated by adding output wrappers. The output wrappers are generally configured using environment variables.
+
+### `Console::Output::Datadog`
+
+This output wrapper augments log messages with trace metadata so that the log messages can be correlated with spans. Note that the default output is still used `Console::Output::Default`.
+
+~~~ bash
+$ CONSOLE_OUTPUT='Console::Output::Datadog,Console::Output::Default' ./app.rb
+~~~
+
+The `Console::Output::Datadog` is a wrapper that augments the metadata of the log message with the `trace_id` and `span_id`.
+
+### Custom Output Wrapper
+
+It's straight forward to define your own output wrapper:
+
+~~~ ruby
+# Add a happy face to all log messages.
+class HappyLogger
+	def call(subject = nil, *arguments, **options, &block)
+		arguments << "😊"
+		
+		@output.call(subject, *arguments, **options, &block)
+	end
+end
+~~~
+
+## Adapters
+
+- [Console::Adapter::Rails](https://github.com/socketry/console-adapter-rails)
+- [Console::Adapter::Sidekiq](https://github.com/socketry/console-adapter-sidekiq)

data/lib/console/version.rb

@@ -4,5 +4,5 @@
 # Copyright, 2019-2026, by Samuel Williams.
 
 module Console
-	VERSION = "1.35.0"
+	VERSION = "1.35.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: console
 version: !ruby/object:Gem::Version
-  version: 1.35.0
+  version: 1.35.1
 platform: ruby
 authors:
 - Samuel Williams
@@ -98,6 +98,12 @@ extensions: []
 extra_rdoc_files: []
 files:
 - bake/console.rb
+- context/command-line.md
+- context/configuration.md
+- context/events.md
+- context/getting-started.md
+- context/index.yaml
+- context/integration.md
 - lib/console.rb
 - lib/console/adapter.rb
 - lib/console/capture.rb
@@ -136,11 +142,13 @@ files:
 - license.md
 - readme.md
 - releases.md
-homepage: https://socketry.github.io/console
+homepage: https://github.com/socketry/console
 licenses:
 - MIT
 metadata:
   documentation_uri: https://socketry.github.io/console/
+  funding_uri: https://github.com/sponsors/ioquatix/
+  source_code_uri: https://github.com/socketry/console.git
 rdoc_options: []
 require_paths:
 - lib