The latest News and Information on DevOps, CI/CD, Automation and related technologies.
We’re excited to announce the public beta of the LogDNA Terraform Provider, allowing organizations to manage Views and Alerts programmatically via Terraform. Today, more teams than ever are adopting Infrastructure as Code (IaC) to reduce human error and create efficiently scaled workflows for their infrastructure. Additionally, teams are looking to bring the same benefits of scalability and predictability into their SaaS-based observability stack.
Here at MetricFire we’re moving some huge rocks to get more benefits for our customers. Our tech team is migrating our Graphite backend from a Riak database to TimescaleDB. This will drive huge benefits for our customers stemming from the new ability to access their database through PostgreSQL querying. Simultaneously, we’ll be migrating our cloud provider from Hetzner to AWS. This drives further benefits surrounding latency, uptime and security requirements for our customers.
In this blog we’ll share the journey we went on to solve a not-so-easy customer problem: a critical Windows services restart during Puppet agent upgrades. As with most software fixes, it starts with a customer ticket: component DHCP Server service restarts after an upgrade. This troubleshooting journey goes from analyzing Windows installer logs, to using undocumented Windows API calls, and back to the Windows installer logs, until we eventually found a solution.
If you require a way to download your Azure Virtual Machine to either your on premise VMware or Hyper-V environment, perhaps because the cost of running that Azure VM is too high, or even for some compliance reason this blog will show you how to quickly download your Azure VM easily with Carbon. No need to download your Azure VM via powershell, or even downloading the VHD from the Azure portal. Carbon will download and convert your Azure VM to your hypervisor of choice with just a few clicks.
Let’s talk through a scenario: You have a Linux-based VM running on DigitalOcean (aka a Droplet), and you install Netdata on it using our recommended kickstart script. As the installation process winds down, the Droplet starts up the Netdata Agent’s web server and serves the local Agent web dashboard on port 19999.