Operations | Monitoring | ITSM | DevOps | Cloud

Following our Identification and Reconciliation post in this series, I wanted to briefly introduce the Identification Rule, a key part of the IRE system. We’ll continue to dig into IRE with this series, check back for more soon. Now that you’ve decided to funnel all of your Configuration Items (CIs) into ServiceNow via IRE, we need to sort out what each item is, and how it should be marked as unique. Identifications Rules perform this step with two distinct parts.

HTTP, which stands for Hypertext Transfer Protocol, is a communication protocol used by your browser to connect to the web server of the site you're looking for. When HTTP data transfer between the browser and the web server is shared via unencrypted hypertext, anybody connected to your network can intercept the data you're transferring. To combat this, it's best to switch to HTTPS, the more secure extension of HTTP. You can't verify data integrity with HTTP

In Part 1, we looked at some best practices for getting started with creating effective test suites for critical application workflows. In this post, we’ll walk through best practices for making test suites easier to maintain over time, including: We’ll also show how Datadog can help you easily adhere to these best practices to keep test suites maintainable while ensuring a smooth troubleshooting experience for your team.

We are excited to announce the availability of the Splunk App for HashiCorp Vault. Using this app, organizations can seamlessly ingest and visualize performance metrics and audit logs in Splunk to investigate, monitor, analyze and act on Vault data across DevSecOps use cases.

Our team recently discovered an exposed endpoint without authentication enabled, though we know it had previously been required. The root cause was a missing configuration as a result of a recent upgrade a few weeks earlier, and was easy to fix by simply enabling the configuration parameter correctly. We needed a way to catch this type of issue quickly going forward, for this and for other public endpoints, which should be secure by default. Here is how we solved it.

When developers think of log files and log analysis, their minds typically transports into the world of contributing factors and incident remediation. However, analyzing log events doesn’t always need to be about a specific bug and its corresponding resolution. In fact, log analysis can be a very useful resource for organizations looking to develop a more high-level and large-scale plan for their application moving forward.

Nexthink is incredibly proud to be able to present yet another installment of our Through the Crisis series, in which our customers share their IT challenges and successes from the COVID-19 crisis. In this installment, Yves Habersaat (software engineer, BG Consulting Engineers) explains how his organization leveraged Nexthink to affect a significant update of their IT estate during the early stages of the pandemic.

In the late afternoon of a beautiful June day, a last-minute customer error was threatening to derail the end of my work day. We received communication from the customer that was simply titled, “There’s a weird error message happening.” The customer included a screenshot of the interface with a nasty SQL error that was propagating to the surface.

An IT director and an MSP walk into a bar… Well, it wasn’t actually a bar, it was a panel session on the second day of the Protect & Streamline Summit for IT Leaders. And they didn’t so much walk in as hit join meeting from their respective home offices. Nevertheless, the discussion between Bryan Schultz and Bob Coppedge, moderated by Datto’s Rob Rae, felt a lot like a candid conversation between friends.