1.1.2 • Published 5 years ago

phat-event v1.1.2

Weekly downloads
2
License
MIT
Repository
github
Last release
5 years ago

PLEASE NOTE Phat-event is a beta library, currently under development.

Phat Event

phat-event is a JavaScript-based library designed for easier creation of "phat", one-per-service log events.

phat-event works well in serverless environments.

Motivation

There are no (that I'm aware of) opinionated log event construction libraries.

What's the difference between this and Winston, Bunyan, X

phat-event is not a logging library. The library takes a configuration function which is called with the constructed event.

Phat event is primarily for the opinionated construction of a fat single log line entry, it is not for the act of logging.

Getting Started

Install: npm install phat-event

const PhatEvent = require("phat-event");
const phatEvent = new PhatEvent();
const mockLog = jest.fn();

phatEvent.configure({ log: console.log })

phatEvent
    .addKey('key', true)

phatEvent
    .emit();

What is a log event?

A log event is a form of structured log, that is updated throughout the lifecycle of a service and a single structured event is emitted at the end of the service.

Rather than this:

{ "timestamp": "X", "message": "Something" }

You have this:

{
    "timestamp": "X",
    "step1": {
        "input": {
            ...
        }
        "output": {
            ...
        }
    }
}

The difficulty with log events

But log events have downsides.

  • If the service fails unexpectedly, the event might not be emitted.
  • Each emitted property is not timestamped by default
  • Poor naming of properties makes it harder to understand property meanings
  • There is no "standard" way to structure these fat log events

Why log events > individual structure logs

Log events allow you to analyse across datapoints without clever tooling that rolls up based on a log property, such as a correlation ID.

API

Documentation for the public API of phat-event.

.configure({ log })

The configure method takes an object of configuration properties, such as:

  • log — The method that is called when the emit event is triggered.

.addKey(String, Any)

Adds a key and value to the event object.

Nested properties can be passed by using dot delimiters between keys prop.prop.prop.

.sanitise(String)

Convers

.emit()

Invokes the configured log method and applies the event as the first argument.

This method allows the log entry to be emitted at the end of service processing.

Releases

1.1.2

  • Return the constructor, rather than the object instance

1.1.1

  • Bugfix to allow .sanitise to access deeply nested properties.

1.1.0

  • Implements .sanitise
    • A helper method which implements method to block out large or sensitive properties.

1.0.0

  • Implements push method

Where does the name come from?

Naming things is hard. And something dry like "event emitter" or similiar isn't noteworthy enough.

As a topic discussed heavily by Charity Majors, I stole the name from her tweet thread: this tweet thread comment where she refers to the event objects as "phat", which made me laugh and is now the name of this library.