Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #24807

N

NETWAYS

Company blog · netways.de/blogsystemsprogramming

NETWAYS is the company blog at netways.de, writing about systems and programming. Since 2012, 3 different Hacker News readers have linked it 5 times. It is still writing: the last post was on 2026-11-02, and you can follow it by feed.

Visit the blog
5mentions?
3HN people?
2012–2022first – last linked?
Links on Hacker News per year · peak 2 in 2020

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

HN readers link NETWAYS posts on git and monitoring. The comments point to a git rebase article and a Spotify monitoring slide deck hosted on the site, and do not assess the writing itself.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

NETWAYS – dein Partner für Enterprise Open Source: Beratung, Betrieb, Web Services, Schulungen und Hardware. Mache deine IT zukunftssicher. Jetzt beraten lassen.

What Hacker News says?

  1. Prometheus.io which is a modern fresh monitoring system that I would checkout if replacing a legacy system. Also take a look at Riemann which is system monitoring written in Clojure. Riemann should be good for monitoring latency of the system. If it helps here is Slidedeck from Spotify how they do their monitoring https://www.netways.de/fileadmin/images/Events_Trainings/Eve...

    Comment linking /fileadmin/images/Events_Trainings/Events/OSMC/2015/Slides_2015/Monitoring_at_Spotify_When_things_go_ping_in_the_night-Martin_Parm.pdf

    on “Ask HN: Best monitoring system?”
  2. Submitted From Monitoring to Observability: Distributed Tracing with Jaeger as a story · 1 points

    HN discussion
  3. Depending on the workflow and collaboration in branches in teams, amending may not be ideal. Amending changes to an existing commit will generate a new sha checksum, thus resulting in a diverging history if the branch is often pushed to the remote Git server. That's one of the rare cases where "git push --force" makes sense but also requires awareness for other collaborators on the branch - they need to run "git fet…

    Comment linking /en/blog/2018/05/24/releasing-our-git-and-gitlab-training-as-open-source/

    on “Take Advantage of Git Rebase”
  4. Submitted Automatic PDF Generation with Google Chrome as a story · 1 points

    HN discussion
  5. Submitted RRDCacheD -- how to escape the I/O hell as a story · 1 points

    HN discussion

Search all of HN for netways.de