Wow. Reading comprehension is a tough.
To my knowledge we do not have any rules against talking about other communities. I will bring it up with the other mods. With the way Lemmy works there will be other subs of the same name with cross subs. I’m going to be subbed to any F1 sub I can find.
This is pretty accurate to what I do professionally.
The point made here about the Average user experience is super super important. It’s good to know what that is for several reasons. Mainly performance tuning. But when it comes to trying to prevent disasters the middle isn’t useful.
Another thing to add. This came to me recently. There are two kinds of graphs and dashboards, those for technical folks and those for managers and non-technical folks. You want to develop both or one with variables to then simplify the graphs/dashboard. Annotations and good titles IMHO are good. Some folks prefer to have technical graph titles. I get the draw but I have to deal with multiple leads, C levels, project managers, and managers that don’t care about the technical stat just where it is compared to where it should be
I can give a brief(ish) overview sure.
Monitor everything :P
But really monitor meaningfully. CPU usage matters but a high CPU usage doesn’t indicate an issue. High load doesn’t mean an issue.
High CPU for a long period of time or outside normal time frames does mean something. High load outside normal usage times could indicate an issue. Or when the service isn’t running. Understand your key metrics and what they mean to failures, end user experience, and business expectation.
Start all projects with monitoring in mind, the earlier to you begin monitoring the easier it is to implement. Re configuring code and infrastructure after the fact is a lot of technical debt. If you are willing and can guarantee that debt will be handled at a later time then good luck. But we know how projects go.
Assign flags to calls. If your application runs results in a response that’s started from and ends up at an end user, Send an identifying flag. Let that flag travel the entire call and you are able to break down traces and find failures.. Failures don’t have to be in error outs, time outs. A call that takes 10x longer than the rest of the calls can cascade and shows the inefficiency and realiability.
Spend time on log and error handling. These are your gatekeepers to troubleshooting. The more time spent upfront making them valuable, the less time you have to look at them when shit hits the fan.
Alerts and Monitors MUST mean something. Alert fatigue is real, you experience it everyday I’m sure. That email that comes in that has some kind of daily/weekly status information that gets right clicked and marked as read. That’s alert fatigue. Alerts should be made in a way that scales.
APM matters Collect that data, you want to see everything from processor to response times, latency, and performance. These metrics will help you identify not only alerting opportunities but also efficiency opportunities. We know users can be fickle. How long are people willing to sit and wait for a webpage to load…. Unlike the 1990’s 10-30 seconds is not groovy. Use the metrics and try to compare and marry them with business key performance indicators(KPI). What is the business side looking for to show things are successful. How can you use application metrics and server metrics to match their KPIs.
Custom scripts are great. They are part of the cycle that companies go through.
Custom scripts to monitor —>
Too much not enough staff —>
SAAS Solutions (Datadog, Solar Winds, Prometheus, Grafana, New Relic) —>.
Company huge SAAS costs high and doesn’t accurately monitor our own custom applications —>
and we’re back to custom scripts. Netflix, Google, Twitter all have custom monitoring tools.
Many of the SAAS solutions are low cost and have options and even free tiers. The open source solutions also have excellent and industry level tools. All solutions require the team to actively work on them in a collaborative way. Buy in is required for successful monitoring, alerting, and incident response.
Log everything, parse it all, win.
You got some monitoring in place? Can offer some assistance with monitoring ideas if you need, is part of what I do.
Also take care of yourself. We can go outside if we can’t log in. Or go back to work..
No. And to think otherwise is elitist. Ease of access is important. Advanced features are important.
Making UI easy to use for casual users is how you end up with power users or advanced users.
I need a UI that makes it easy to get started and then let me grow into it. I don’t need something that takes weeks to figure out and then I can lorde it over the un-initiated.
I’ve built several. They are worth every penny. Not only reduced pain in the hands, wrist, and forearms. Also in my shoulders. I’m a fairly wide human and split tented allows you to place the separate parts at a more natural distance for shoulder/arm width.
My mother eve ended up stealing my last build. She’s not complained since and travels with it for work.
Not a chance in this world I’ll join without them paying me money to do it.
There’s some cool vids of Sim racers being placed in real cars and it shows the skills are highly transferable with a small familiarity time window.
Max is for sure a versatile racer. I’m betting any of the greats could adapt pretty well to other style race content. Wonder if they see the thrill in comparison to F1 though.
Thanks a lot for the server.
What are the server specs for us nerds out there
Where do you see this information on their profits?
I think you don’t really have a point and are simply looking to argue.
It was very clearly stated in the comment what the intent of the comment was.