HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
phaistos-networks
TANK
C++2016–2020
phaistos-networks / TANK

TANK

A very high performance distributed log service

4Distinct people
12Mentions
0Explicit recommenders
941GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A very high performance distributed log service

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2016-07-16 13:32:28 UTC to 2020-02-24 00:09:11 UTC.

02468102016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1019
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202

What Hacker News says

2 sources
> The reason people use it is that nothing else exists. Maybe https://github.com/grafana/loki , but haven't yet tried it. (Or https://github.com/phaistos-networks/TANK ..?) > I think a better strategy is to store logs in flat files with several replicas Agreed. We just used beats + logstash and put the files into Ceph. > x-request-id and maybe a trigram index of messages, and actually be able to debug full request cycles in a handful of milliseconds when necessary. Yes, yes, yes. That would be great.
In Guide to running Elasticsearch in production
Our (https://bestprice.gr/) services/“programs” generate three different types of events: - Short events (no longer than ~1k in size) where the cost to generate and transmit is very low(sent to dedicated service via UDP). We can generate dozens of them before we need to care about the cost to do so. They are binary-encoded. The service that receives those datagrams generates JSON representations of those events and forwards them to all connected clients(firehose) and also publishes them to a special TANK partition. - Events of arbitrary size and complexity, often JSON encoded but not always -- they are published to TANK(https://github.com/phaistos-networks/TANK) partitions - Timing samples. We capture timing traces for requests that may take longer-than-expected time to be processed, and random samples from various requests for other reas
Read the rest
ons. They capture the full context of a request(complete with annotations, hierarchies, etc). Those are also persisted to TANK topics So, effectively, everything’s available on TANK. This has all sorts of benefits. Some of them include: - We can, and, have all sort of consumers who process those generates events, looking for interesting/unexpected events and reacting to them (e.g notifying whoever needs to know about them, etc) - It’s trivial to query those TANK topics using `tank-cli`, like so: tank-cli -b <tank-endpoint> -t apache/0 get -T T-2h+15m -f "GET /search" | grep -a Googlebot This will fetch all events starting 2 hours ago, for up to 15 minutes later, that include “GET /search” All told, we are very happy with our setup, and if we were to start over, we’d do it the same way again.
In Ask HN: How do you manage logs for your backend services?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.