In this article I’m going to discuss table joins and the let statement in Log Analytics. Along with custom logs, these are concepts that really had me scratching my head for a long time, and it was a little bit tricky to put all the pieces together from documentation and other people’s blog posts. Hopefully this will help anyone else out there that still has unanswered questions on one of these topics.
In this article, I’m going to discuss custom logs in Log Analytics. Along with table joins and the let statement that I discuss in another blog, custom logs is a concept that I struggled to wrap my head around for a long time, as there don’t seem to be very many comprehensive guides out there as of yet. Here is a summary of everything I have managed to piece together from documentation and other people’s blog posts.
If productivity is the engine that helps optimize how a business operates then being proactive is the oil and knowing how to effectively maintain productivity is regularly checking and replacing said oil. Whenever a service outage occurs it throws a wrench into the whole process and can put an entire organization in flux, mainly because the outage.
Rapid Circle has been providing information and communication technology services to organizations since 2008. The company offers cloud workplace and managed cloud services like data center migration, adoption and change management, and other cloud solutions that help organizations cut costs, improve productivity, and contribute to innovation, internal communication, and collaboration.
Three years ago, Tom Wilkie and Frederic Branczyk sketched out the idea for Prometheus monitoring mixins. This is a jsonnet-based package format for grouping and distributing logically related Grafana dashboards with Prometheus alerts and rules. The premise was that the observability world needed a way for system authors to not only emit metrics, but also provide guidance on how to use those metrics to monitor their systems properly.
There are some things in life that seem too good to be true. So good, in fact, that they border on the edge of mythology. We see this often in the case of Cross-Domain Topology. Cross-Domain Topology ties together all the pieces of a hybrid, dynamic IT environment, so you can instantly see how changes impact your environment. It’s something that a lot of people didn’t even think was a possibility. While unicorns are myths, Cross-Domain Topology is very real. Here’s how it works.
Mixing your personal and work devices while connected to your home network and accessing the Internet is a risky proposition from a security and privacy standpoint. Why? I frequently monitor my firewall logs. What I observe on my WAN interface are blocked IP addresses sourced from adversarial nation states which makes the hair on the back of my neck stand up.
As many users of Icinga don’t know what the DSL has to offer, I’m going to show you how to use custom variables and apply for rules to make your life easier when writing configuration for your Icinga environment. In this example we will use custom variables on a host to configure a dynamic set of services to monitor multiple web services behind a reverse proxy. On the host we define a custom dictionary called http_vhosts and assign our virtual hosts to it.
