Prometheus Pushgateway Installation: Difference between revisions
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
==Pod and Services== | ==Pod and Services== | ||
<syntaxhighlight lang=' | <syntaxhighlight lang='bash'> | ||
namespace=prom | namespace=prom | ||
cat <<EOF | kubectl -n ${namespace} apply -f - | cat <<EOF | kubectl -n ${namespace} apply -f - |
Revision as of 05:57, 16 October 2020
Internal
Kubernetes Installation
Deploy the pod and associated services, and then configure it as a scraping target by deploying a ServiceMonitor. All descriptors are available in:
Pod and Services
namespace=prom
cat <<EOF | kubectl -n ${namespace} apply -f -
apiVersion: v1
kind: Pod
metadata:
name: 'pushgateway'
labels:
function: 'pushgateway'
spec:
containers:
- name: 'pushgateway'
image: prom/pushgateway
---
apiVersion: v1
kind: Service
metadata:
name: 'pushgateway'
labels:
function: 'pushgateway-target'
spec:
type: 'ClusterIP'
selector:
function: 'pushgateway'
ports:
# 'name' is important, it will be referred by ServiceMonitor configuration
- name: 'pushgateway'
protocol: 'TCP'
port: 9091
targetPort: 9091
---
apiVersion: v1
kind: Service
metadata:
name: 'pushgateway-lb'
spec:
type: 'LoadBalancer'
selector:
function: 'pushgateway'
ports:
- name: 'pushgateway'
protocol: 'TCP'
port: 9091
targetPort: 9091
EOF
ServiceMonitor
Expose it then as a Prometheus scraping target with a ServiceMonitor:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
name: pushgateway
namespace: prometheus
labels:
release: prometheus
spec:
endpoints:
- port: 'pushgateway' # must match the label from Service declaration
path: /metrics
interval: 15s
namespaceSelector:
matchNames:
- prometheus
selector:
matchLabels:
function: 'pushgateway-target'
Also see: