The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
As technology evolves so do the needs of an organization that rely upon it; the ability to quickly adapt has become more important than ever, especially as of late. However, this doesn’t mean that adopting new technology isn’t without its own set of challenges. Take operating in the cloud for instance; one of the trade-offs is visibility.
Some devs use JavaScript in the browser; some use JavaScript on the server. What if you do both?
We recently ran a quick poll where we asked the audience, “When an IT incident occurs at your company, what TV show does it most resemble?” Twenty-three percent of respondents told us that CSI: Crime Scene Investigation resembled them the most. We needed to dig into that a little deeper. Let’s walk through the typical steps of figuring out the root cause, in CSI fashion: Photographs are critical in the world of CSI.
Two weeks ago, Icinga 2 Config Sync: Behind the Scenes explained how the config sync in Icinga 2 works and how you can look behind the scenes. Today, we will put our knowledge from that post to the test and try to manually replicate the config sync. The most important takeaways will be recapped in this post, but if you are interested and have the time, the other post is also worth a read.
The modern enterprise network is akin to the transcontinental railroad system in the United States in the early 20th century: it was far-reaching and commerce depended upon the reliability of the rail service connecting crucial goods with Americans in every town and city. Likewise, networks today are intrinsic to commerce (and daily life) yet they are entangled and multi-layered.
