Public/grafana-meta-monitoring-chart
2
0
Fork 0
forked from RemoteSync/grafana-meta-monitoring-chart
Code Pull Requests Activity

allow alloy to run in the same namespace it is monitoring and not require an entry for namespacesToMonitor

Browse Source
This commit is contained in:
Edward Welch 2024-10-25 19:45:27 +00:00
parent 9a3d0b51d8
commit bcac10ca74
No known key found for this signature in database
GPG Key ID: 9A98721A6BB4377B
2 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
charts/meta-monitoring/templates/validate.yaml
View File

@ -34,10 +34,6 @@
{{- end -}} {{- end -}}
{{- end -}} {{- end -}}
{{- if empty .Values.namespacesToMonitor -}}
{{- fail "No namespaces have been specified in namespacesToMonitor" -}}
{{- end -}}
{{- if empty .Values.metrics.retain -}} {{- if empty .Values.metrics.retain -}}
{{- fail "All metrics will be collected, please specify some in metrics.retain" -}} {{- fail "All metrics will be collected, please specify some in metrics.retain" -}}
{{- end -}} {{- end -}}

5
charts/meta-monitoring/values.yaml
View File

@ -1,6 +1,7 @@
# Specify the namespaces to monitor here # Specify the namespaces to monitor here
namespacesToMonitor: # By default the chart will monitor the namespace it is installed in
- loki # namespacesToMonitor:
# - loki
# The name of the cluster where this will be installed # The name of the cluster where this will be installed
clusterLabelValue: "meta" clusterLabelValue: "meta"
# Set to true to write logs, metrics or traces to Grafana Cloud # Set to true to write logs, metrics or traces to Grafana Cloud