HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bdeitte
hot-shots
JavaScript2022–2022
bdeitte / hot-shots

hot-shots

A Node.js client for Datadog's DogStatsD server, InfluxDB's Telegraf StatsD server, the OpenTelemetry Collector StatsD receiver, and Etsy's StatsD server.

2Distinct people
2Mentions
0Explicit recommenders
567GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A Node.js client for Datadog's DogStatsD server, InfluxDB's Telegraf StatsD server, the OpenTelemetry Collector StatsD receiver, and Etsy's StatsD server.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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 hour2 dated mentions

Observed mentions: 2022-10-21 13:28:31 UTC to 2022-10-21 14:59:10 UTC.

012022-10-21 13:00:00 UTC to 2022-10-21 14:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 21, 13:002022-10-21 14:00:00 UTC to 2022-10-21 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 21, 14:00

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
Oct 21, 13:002022-10-21 13:00:00 UTC2022-10-21 14:00:00 UTC101
Oct 21, 14:002022-10-21 14:00:00 UTC2022-10-21 15:00:00 UTC101

What Hacker News says

2 sources
Looking at the UDP code in question in brightcove/hot-shots [1]. The createUdpTransport() function creates an object with a send() method that forwards to socket.send(), calling the underlying function with the same host and port argument each time. It seems to me that this code should call socket.connect(args.host, args.port) once instead, and skip the host and port arguments to the send() calls. Presumably this would result in just a single DNS lookup. Bonus: the createUdpTransport() function also has a DNS cache, which the author of the article could have enabled with just "cacheDns: true". But if the library code used socket.connect(), this internal cache shouldn't be needed either. 1: https://github.com/brightcove/hot-shots/blob/564ac7bfdaaf366...
In Sending UDP Messages in Node.js Without DNS Lookups

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.