Live data from Hacker News

Show HN: Monitoror – Unified monitoring wallboard

monitoror.com

41–50 of 125 posts

Re: Show HN: Monitoror – Unified monitoring wallboard

#41
Hello

Do you need financial support?

Sign up for all kinds of loans and get the money urgently!

* Get a stress-free loan today! * No Contest Qualifying! * No credit check, no faxing! * Instant online approvals! * Completely confidential! * Cash in 48 hours!

* Appointment between $5,000 and $100,000,000 USD (only one hundred million USD) * Interest rate of 3% * Choose between 1-25 years repayment. * Choose between monthly and annual repayment plan. * Flexibility of loan terms.

All these plans and more, please contact us via: catrinaprestamo@outlook.com

Enter your data as needed. Name, address, date of birth, monthly income, loan amount required, desired loan term.

Administration Catrinaprestamo@outlook.com

WHATSAPP: +1(863)410-6179

Re: Show HN: Monitoror – Unified monitoring wallboard

#42
post #6

I know people like wallboards and monitors but we found them anti-pattern. If you find yourself looking at a wallboard/dashboard, it should already be an automated alert.

Not at all. Alerts serve a different purpose.

One of the most important things a team needs over the long haul is a feel for their system. Many people refer to this as mechanical sympathy. And the way you develop that is long-term exposure to rich data.

Alerts are the red and yellow lights on your dashboard. But you get mechanical sympathy by listening to the sound of the engine, feel of the road, and the smell of things when you take a peek under the hood.

There are a lot of ways to achieve mechanical sympathy, of course. And information radiators are easily misused; you have to have the right information shown in the right ways for people to develop a correlative, intuitive understanding of what they've built. But nobody develops mechanical sympathy by looking at dashboard lights alone.

Re: Show HN: Monitoror – Unified monitoring wallboard

#44

Earlier quoted context omitted.

I got it to run on a different port just fine with the MO_PORT environment variable, FWIW.

Turns out its just too early in the day. I wasn't saving the variable beyond setting it. So when I switched terminals it didn't exist. Put it in my bash profile and all is well.

You can use .env file too, or even put it before the command like that:

MO_PORT=8888 ./monitoror

:)

Re: Show HN: Monitoror – Unified monitoring wallboard

#45
post #21
post #12

Earlier quoted context omitted.

What would your alert be for # open PRs (an example in the demo linked from posted page)? How often would it fire? Whatever the answer, that's a different thing from this. Both have their place.

Why do you want a display of open PRs at all? I think the fundamental question of all such tools is "Why are we watching this, and what are we looking for," and there are limited but nonzero good reasons to have a display. "Someone should look at open PRs if there are too many" is a bad one - the number doesn't tell you about the urgency of the existing PRs. If you want to respond promptly, respond to all of them pro…

> Why do you want a display of open PRs at all?

All PRs are WIP, and minimizing WIP is very valuable in product development processes. See Reinertsen's The Principles of Product Development Flow for the math, but basically high/unpredictable latency drastically limits the pace of learning and causes a lot of upstream thrash and waste.

I remember talking with one team at the bird-themed social media company that was frustrated with slow PRs; they dropped average delay from 3-4 days to under 4 hours. They said it made a huge experiential difference and they loved the change.

Re: Show HN: Monitoror – Unified monitoring wallboard

#47
post #6

I know people like wallboards and monitors but we found them anti-pattern. If you find yourself looking at a wallboard/dashboard, it should already be an automated alert.

By that logic a speedometer is an anti pattern and your car should just send up an alert when you're speeding... since when is getting accurate real-time information a bad thing?

Re: Show HN: Monitoror – Unified monitoring wallboard

#48
Panic used to have an iOS app that did this. It was called Status Board, and was magnificent.

You could put it on an old iPad on an easel on your desk and watch everything from RSS feeds to ping statistics. In an office setting, you'd hook the 'Pad up to a cheap flat screen TV so everyone could see.

Sadly, Panic discontinued it when it decided to go after the video game market.

Re: Show HN: Monitoror – Unified monitoring wallboard

#49
post #45
post #21

Earlier quoted context omitted.

Why do you want a display of open PRs at all? I think the fundamental question of all such tools is "Why are we watching this, and what are we looking for," and there are limited but nonzero good reasons to have a display. "Someone should look at open PRs if there are too many" is a bad one - the number doesn't tell you about the urgency of the existing PRs. If you want to respond promptly, respond to all of them pro…

> Why do you want a display of open PRs at all? All PRs are WIP, and minimizing WIP is very valuable in product development processes. See Reinertsen's The Principles of Product Development Flow for the math, but basically high/unpredictable latency drastically limits the pace of learning and causes a lot of upstream thrash and waste. I remember talking with one team at the bird-themed social media company that was f…

Yes, I understand why you'd want to focus on solving the number of open PRs. I agree that keeping that number down is good. My question is why do you want to put this on a TV screen.

If you want people to focus on open PRs, tell them to open GitHub on their computers, don't tell them to look up at a TV screen periodically. Treat it like alerts: you have a list of open things to deal with and you need to get that number to zero. There's no threshold greater than zero of a long-term acceptable number of open PRs.

If the problem is that they have other things to look at too, installing yet another TV screen won't solve that, your team needs to make the management decision of what to prioritize. Options include making a unified dashboard of incidents/alerts/PRs/support tickets (and encoding which ones sort to the top), setting up a PR review rotation (i.e., for one week, completing reviews is your top priority barring all-hands-on-deck incidents), treating open PRs as alerts and escalating them if nobody replies within 4 hours, removing other work by deciding you'll deprioritize low-impact alerts (and hope that the increased development velocity ends up solving problems), etc.

Re: Show HN: Monitoror – Unified monitoring wallboard

#50

Panic used to have an iOS app that did this. It was called Status Board, and was magnificent. You could put it on an old iPad on an easel on your desk and watch everything from RSS feeds to ping statistics. In an office setting, you'd hook the 'Pad up to a cheap flat screen TV so everyone could see. Sadly, Panic discontinued it when it decided to go after the video game market.

But why do you need an app where webpage is more than enough?
Post reply on HN