What’s the service desk ticket that finally broke the camel’s back? Andrew Cohen (Sr. Manager, Digital Workplace Services at Cox) never had to find out – because he transitioned to a proactive service desk. In other words: a service desk that isn’t weighed down by growing ticket counts, reoccurring issues, and non-responsive employees. In a recent BrightTALK-hosted webinar, Andrew shared some of his firsthand experiences with building a proactive IT team.

Last year I started an IoT project, Plant Buddy. This project entailed soldering some sensors to an Arduino, and teaching that device how to communicate directly with InfluxDB Cloud so that I could monitor those plants. Now I am taking that concept a step further and writing the app for plantbuddy.com. This app will allow users to visualize and create alerts from their uploaded Plant Buddy device data in a custom user experience.

Performance is not something you should compromise on, and it's important to have a healthy development process that improves as your application grows. If your PHP application is not super-fast, it will be much harder to scale and maintain. You need to identify errors in the early stage to fix them as soon as possible. And if you don’t know where your bottlenecks are, you can’t fix them.

As the complexity of software systems explodes, so does the amount of data that gets generated by instrumenting these systems. This poses a problem for our users — especially those who are in charge of observability teams and observability platforms at large enterprises. They have to strike the right balance between cost management and giving teams the freedom to instrument whatever they want. Often observability leaders are supporting dozens of teams that are using hundreds of dashboards.

While Healthcare IT leaders take great care in choosing the right Electronic Health Records system, some may overlook the critical role that a virtuali zed desktop delivery infrastructure like Citrix and VMwareHorizon plays in providing access to Cerner and other mission-critical applications.

Yes, time travel is possible...through data. My ability to time travel began when I started coding at age 10. Back then, all of my code ran on my own little computer. Like many ten-year-olds, I coded to create and play games. I also coded cool graphics to accompany music to impress my friends and utilities for copying. I launched my first commercial website in 1996 and made 25 guilders, which was good money for a 15-year old. Life was so easy.

Modern software services are expected to be highly available, and running a service with minimal interruptions requires a certain amount of reliability-focused engineering work. At the same time, teams also need to build new features and improve existing ones, so that users are delighted and don’t churn.

The ability for security teams to integrate threat data into their operations substantially helps their organization identify potentially malicious endpoint and network events using indicators identified by other threat research teams. In this blog, we’ll cover how to ingest threat data with the Threat Intel Filebeat module. In future blog posts, we'll cover enriching threat data with the Threat ECS fieldset and operationalizing threat data with Elastic Security.

Though invisible to most users, APIs are the backbone of modern web applications. Developers love them because they facilitate complex integrations between systems and services. The business loves them because integrating disparate systems to create new products and services drives innovation and growth. The challenge with this transformative connectivity is the dependencies that exist between systems. API failure can result in performance degradation, data anomalies, or even system-wide outages.