Sha256: 5ea9280bc0de88033a484661cb61d610b0fffb2a866677fe418267fff9ab35ce
Contents?: true
Size: 1.42 KB
Versions: 5
Compression:
Stored size: 1.42 KB
Contents
require "timber/context"
require "timber/util"
module Timber
module Contexts
# Custom contexts allow you to add application specific context not covered elsewhere.
# Any data added this way will be included in your logs. A good example is worker job
# IDs. When processing a job you might add the job ID to the context, allowing you to
# view *all* logs generated while processing that job, not just the logs that contain
# the ID.
#
# Note in the example below all custom contexts must contain a root key. This is to
# ensure attribute names and types never clash across your contexts. It gives you
# much cleaner pallete to organize your data on.
#
# @example Adding a custom context
# logger.with_context(build: {version: "1.0.0"}) do
# # anything logged here will have the custom context above
# # when this block exits the context will no longer be included
# end
class Custom < Context
@keyspace = :custom
attr_reader :type, :data
def initialize(attributes)
@type = attributes[:type] || raise(ArgumentError.new(":type is required"))
@data = attributes[:data] || raise(ArgumentError.new(":data is required"))
end
# Builds a hash representation of containing simply objects, suitable for serialization.
def as_json(options = {})
{Timber::Util::Object.try(type, :to_sym) => data}
end
end
end
end
Version data entries
5 entries across 5 versions & 1 rubygems