In the previous post I talked about bottlenecks in organizations, with a view from the DevOps transformation perspective. This article will focus on the close relation between the organizational structure and the culture.
Years ago, there was a worldwide tendency to adopt ITIL in the IT departments of all organizations, big or small. This, together with the wide adoption (although misunderstood by most) adoption of COBIT led to big and small companies setting up clear pillars, where the focus was on the activity being done, instead of the product or service delivered to the customer.
Since the update to Prometheus 2.0, the documentation still has to catch up. Because I’ve been debugging a custom written exporter, some unwanted metrics landed in my Prometheus.
This is how to delete those series.
Enable the Prometheus Admin API
Deleting the metrics is only available over the Admin API. You can enable it with a flag. Just edit your Prometheus start-up script and add:
This guide will show you how to deploy Proxmox VE 5 with KVM Routing and NAT on a Hetzner server with focus on networking and DHCP/DHCPv6.
- The connected interface is
192.0.2.62/27is the public IP assigned by Hetzner
192.0.2.33is the default gateway for the network
10.1.1.0/24is the private block used on the VMs
2001:db8:1111:2222::/64is the IPv6 block assigned to the host
2001:db8:1111:2222:81::/80is the IPv6 block delegated to the VMs
- The domain name used in the VMs is
- The host name of the hypervisor is
- All the commands are run as
Ever since I’ve started hosting my own domains, I’ve searched for ways to automate the website provisioning.
Normally, the documentation includes the information on configuring your infrastructure based on roles. But if you have a webserver role for all your minions it doesn’t help with the individual provisioning I am aiming at.
Tired of always being afraid someone will hack into your Linux computer/server?
One of the most important steps is to make sure the attacker can’t log in with the “root” account.
In order to do this, you have to:
- Make sure you can “switch user” to root (you will need to be able to control your system, after all)
- Make sure that nobody can log in with root, neither remote nor local.
Article target: web developers
- OLDER POSTS
- page 1 of 2