Operations | Monitoring | ITSM | DevOps | Cloud

Latest News

Industry best practices for endpoint security

Lately, hackers on the lookout for vulnerable systems have kept the IT industry busy. While various OS and software vendors strive to keep their users’ data intact by providing timely updates, manually securing endpoints by applying these updates is challenging due to factors such as time, staffing, and IT budgets. To help admins out, we’ve compiled a list of some industry best practices you can implement to stay vigilant against cyberattacks and data theft.

timeShift(GrafanaBuzz, 1w) Issue 66

All Things Open, a conference focused on open source technologies, was held in Raleigh, NC this week and was bursting at the seams with over 4,500 attendees. Grafana Labs’ own Tom Wilkie gave his RED Method: How to instrument your services talk to a standing-room only crowd. We were excited to speak at and sponsor ATO and look forward to next year.

How we improved our React Native cold start for Android

About two years ago here at Mattermost, we decided to start building a prototype for our mobile apps in React Native (RN for short). We were so impressed with how easy it was to build our app for both platforms that we ultimately decided that RN was the way to go for mattermost-mobile apps. Thanks to RN, we can focus exclusively on ensuring feature parity between our mobile apps and our webapp.

The Language of Incident Management

Language used across the high technology ecosystem is dynamic to say the least. Nowhere else can you find a mixture of technical jargon seamlessly intertwined with references from science fiction, mythology, pop-culture, literature, and more. While this makes conversations heard across technical environments colorful and engaging, it also makes communications allegorical and metaphorical— opening them to variable interpretation.

EC2 Packets per Second: Guaranteed Throughput vs Best Effort

Remember the customer who reported a hard-coded packet per second (PPS) limit in AWS? His use case was a reverse-proxy server to a very active database cluster, complete with heartbeats, keep-alive connections, and a heavy load of queries and traffic. When the network throughput was sustained for an hour or so, the throughput would drop despite increasing demand.