Operations | Monitoring | ITSM | DevOps | Cloud

As your apps scale, testing can become repetitive, manual, and time-consuming, leading to slower release cycles and lower-quality code. Sofy is a SaaS platform that enables you to create and run automated tests on your mobile apps without writing any code. Sofy will automatically test your mobile apps on real iOS and Android devices, so you can optimize their performance and debug end-user experiences without setting up or maintaining your own test infrastructure.

As a good technology superhero you will know that in the world of troubleshooting, there is an approach that goes beyond simply fixing superficial symptoms. We call this approach “Maximum Heroics” or Root Cause Analysis (ACR), a charming method that seeks to unravel the mysteries behind an incident. Through the RCA, the causal factors of an incident are examined, and why, how and when it happened are broken down in order to prevent it from repeating itself and ensure smooth continuity.

Each organization's IT environment has its own prerequisites and unique challenges. This also means that there are different needs for the monitoring and automation of every organization's critical applications. However, finding a monitoring solution that fits your unique needs is not always easy. Especially if your organization has particular regulations and demands that need to be taken into consideration.

Using Tracealyzer to view applications running on Zephyr RTOS comes with a special challenge: unlike some other microcontroller-oriented real-time operating systems, Zephyr exposes its kernel services via a syscall layer. A syscall is essentially a way to programmatically communicate with the operating system kernel from user level code.

Today we’re announcing the general availability of Icinga Web v2.12.0. You can find all issues related to this release on our Roadmap. Please make sure to also check the respective upgrading section in the documentation.

Anthony Leroy has been a software engineer at the Libraries of the Université libre de Bruxelles (Belgium) since 2011. He is in charge of the digitization infrastructure and the digital preservation program of the University Libraries. He coordinates the activities of the SAFE distributed preservation network, an international LOCKSS network operated by seven partner universities.

Technical folks in OSS communities often find themselves in permanent learning mode. Technology changes constantly, which means learning new things — whether it’s a new feature in the latest OSS release or an emerging industry best practice — is, for many of us, simply a natural part of our jobs. This is why it’s important to think about how we learn, and improve the skill of learning itself.

Any existing InfluxDB user will notice that InfluxDB underwent a transformation with the release of InfluxDB 3.0. InfluxDB v3 provides 45x better write throughput and has 5-25x faster queries compared to previous versions of InfluxDB (see this post for more performance benchmarks). We also deprioritized several features that existed in 2.x to focus on interoperability with existing tools. One of the deprioritized features that existed in InfluxDB v2 is the task engine.

As organisations strive to deliver seamless user experiences, maximise operational efficiency, and maintain a competitive edge, the need for comprehensive Application Performance Monitoring (APM) tools becomes increasingly evident. APM tools offer invaluable insights into the performance and behaviour of applications in real-time. They go further than the conventional monitoring approach by providing a holistic view of the entire stack, encompassing servers, databases and user interactions.

Being able to execute SQL performance tuning is a vital skill for software teams that rely on relational databases. Vital isn’t the only adjective that we can apply to it, though. Rare also comes to mind, unfortunately. Many software professionals think that they can just leave all the RDBMS settings as they came by default. They’re wrong. Often, the default settings your RDBMS comes configured with are far from being the optimal ones.