News for hackers. Stuff that matters.

copperlight

Re:Making Beautiful API Keys on Friday January 10, 2025 @09:33AM (#42655854)
https://www.crockford.com/base32.html

> We chose a symbol set of 10 digits and 22 letters. We exclude 4 of the 26 letters: I L O U.

I had never heard of Base32 Crockford before. The whole rationale is clever.

Re:The Sweet Spot for Buying Used Cars on Saturday January 21, 2023 @08:40PM (#34473170)
Here is a list of 10 new (2023) cars that you can buy for prices ranging from 17,600 to 22,115:

https://www.cars.com/amp/articles/here-are-the-10-cheapest-n...

Re:The djb way (2007) on Sunday September 13, 2015 @12:41PM (#10211915)
Netflix uses daemontools in their BaseAMI[1] for starting up core services such as Apache and Tomcat. I think this choice was originally made to ensure consistency in process startup methods across CentOS and Ubuntu. Support for automatically creating daemontools scripts is baked into nebula-ospackage-plugin[2].

[1] http://techblog.netflix.com/2013/03/ami-creation-with-aminat...

[2] https://github.com/nebula-plugins/nebula-ospackage-plugin

Re:Introducing Atlas: Netflix's Primary Telemetry Platform on Saturday December 13, 2014 @12:23AM (#8744267)
Telemetry traffic is a small fraction of the the total traffic running through a region, partially due to the use of the Smile data format (binary JSON) for delivering metrics from the client to the Atlas backend.

When you give developers tools for creating and aggregating highly dimensional metrics, they tend to create lots of metrics so that they can answer interesting business questions about the use of their applications. We have some developers who have written code that produces up to 150,000 metrics per instance and the vast majority of these metrics are application-level. We typically see 3-5% of the metrics delivered from an instance are system-level performance metrics.

Re:Introducing Atlas: Netflix's Primary Telemetry Platform on Friday December 12, 2014 @11:34PM (#8744165)
Interesting - I had not heard of Fnordmetrics before. There are not many monitoring systems that implement dimensionality for metrics tagging. It looks like Fnordmetrics goes about it slightly differently, but it seems to achieve the same end goal of arbitrary grouping by like characteristics.

In the Atlas eco-system, Servo and Atlas client eliminate the need for StatsD. The combination of these products allow for code-level instrumentation and delivery of metrics. The Prana sidecar is available for non-Java applications to deliver metrics to the Atlas backend as formatted JSON objects.

Atlas supports multiple backend storage systems, although this is not easily pluggable just yet. Earlier iterations of Atlas had support for MongoDB and Cassandra as storage backends, but there were issues obtaining enough IOPS to satisfy the read and write performance requirements at scale, so storage was switched to in-memory.

Atlas can return data in JSON format (?format=json) which is suitable for JS or SVG based rendering systems such as Highcharts. There is also a streaming API that trades response time for increased data payloads.

It takes some time to learn the Atlas Stack Language, but the fact that it is URL-based means that the browser is the interactive query editor. Using tools like Chrome's Edit URL to help handle long strings, you can make small changes to queries iteratively and see the results in less than 2 seconds in many cases. Average PNG render time is typically less than 10 seconds; slow rendering can take around 30 seconds.

Re:Introducing Atlas: Netflix's Primary Telemetry Platform on Friday December 12, 2014 @05:54PM (#8743201)
There are several different data sources for Atlas:

* There is a poller cluster that gathers SNMP and HTTP healthcheck metrics and forwards them to the Atlas backend.

* There are on-instance log parsers written in Perl and Python that count events in Apache HTTPd and Tomcat logs and send data to the Atlas backend.

* The Servo library [0] is used to instrument Java code with counters, timers and gauges. There is a separate client implementation that handles forwarding metrics to the Atlas backend. The client also polls and reports JMX metrics from the JVM that it runs inside. Spectator [1] is a new library that provides cleaner abstractions of Servo concepts.

* The Prana sidecar [2] was extended to provide REST endpoints for Servo and the client, so that metrics can be delivered from non-Java code.

[0] https://github.com/Netflix/servo

[1] https://github.com/Netflix/spectator

[2] https://github.com/Netflix/prana