https://github.com/mokiat/preftime

Add timestamp prefixes to command outputs
https://github.com/mokiat/preftime

command-line golang timestamp tool

Last synced: 3 months ago
JSON representation

Add timestamp prefixes to command outputs

• Host: GitHub
• URL: https://github.com/mokiat/preftime
• Owner: mokiat
• License: apache-2.0
• Created: 2017-06-09T06:48:18.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-03-21T21:20:50.000Z (almost 2 years ago)
• Last Synced: 2024-04-14T12:48:17.467Z (10 months ago)
• Topics: command-line, golang, timestamp, tool
• Language: Go
• Homepage:
• Size: 11.7 KB
• Stars: 6
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# preftime

![Build Status](https://github.com/mokiat/preftime/workflows/Go/badge.svg)

[![Go Report Card](https://goreportcard.com/badge/github.com/mokiat/preftime)](https://goreportcard.com/report/github.com/mokiat/preftime)

Preftime is a tool that allows you to prefix the output of another program with timestamp information.

Ideally, the program you are running should have the capability to log timestamps on its own. Alternatively, you could check whether you terminal supports such a feature. However, I have been in situations where neither option was available. I ended up writing these few lines of code and decided to share it with anyone who may need it.

If you have a Go development environment set up, you can use the following command to acquire the tool.

```sh

go install github.com/mokiat/preftime@latest

```

Otherwise, there are pre-built versions of the tool available in the [Releases](https://github.com/mokiat/preftime/releases) section of this project.

You would use the tool as follows.

```sh

 2>&1 | preftime

```

The `2>&1` part is optional. It just assures that both stdout and stderr go through `preftime`.

As an alternative, you could do the following.

```sh

 > >(preftime) 2> >(preftime)

```

This redirects both stdout and stderr to preftime. The `>(preftime)` part makes `preftime` behave like a writable file.

Following the same logic, you could have your bash script redirect it's output to preftime.

```sh

#!/bin/bash -e

exec > >(preftime)

exec 2> >(preftime)

```

For example, here is a real-life simple usage scenario.

```sh

$ host example.org | preftime

[2017-06-25 15:42:00.664] example.org has address 93.184.216.34

[2017-06-25 15:42:00.665] example.org has IPv6 address 2606:2800:220:1:248:1893:25c8:1946

```