Running script exporter on Kubernetes about script_exporter

[ricoberger]

Hi @pawelrys, if these logs are only available ~/var/app/log in your application container, then I would recommend to add the script_exporter as sidecar and share the volume with the log files between the two containers, like it is shown here: https://kubernetes.io/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/.

If these logs are also written to stdout / stderr then you can also run the script_exporter as privileged pod and run your scripts on the host, because these logs should be available at /var/logs/containers on the node where the application pod is running. I think the DaemonSet can then look similar to the following one:

---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: script-exporter
spec:
  selector:
    matchLabels:
      app: script-exporter
  template:
    metadata:
      labels:
        app: script-exporter
    spec:
      containers:
        - image: ricoberger/script_exporter
          name: script-exporter
          volumeMounts:
            - mountPath: /var/log
              name: varlog
            - name: config
              mountPath: /etc/script_exporter
      volumes:
        - hostPath:
            path: /var/log
          name: varlog
        - name: config
          configMap:
            name: script-exporter
            defaultMode: 0777

It just contains the basic fields to get an idea of it. You may also have to add some other fields from the example Deployment: https://github.com/ricoberger/script_exporter/blob/master/examples/kubernetes.yaml.

[ricoberger]

I would close this issue. If you still have some problems with running the exporter on Kubernetes please let me know.