forked from RemoteSync/grafana-meta-monitoring-chart
Compare commits
6 Commits
v0.0.3
...
fix_traces
Author | SHA1 | Date | |
---|---|---|---|
|
ad96f09600 | ||
|
090f1ef91a | ||
|
b2957d90f0 | ||
|
f8aea814c5 | ||
|
91c19f07d3 | ||
|
315b203082 |
@@ -346,7 +346,7 @@ data:
|
|||||||
{{- if .Values.local.traces.enabled }}
|
{{- if .Values.local.traces.enabled }}
|
||||||
otelcol.exporter.otlphttp "local" {
|
otelcol.exporter.otlphttp "local" {
|
||||||
client {
|
client {
|
||||||
endpoint = "http://{{- .Release.Name -}}-tempo-distributor.svc:4318"
|
endpoint = "http://{{- .Release.Name -}}-tempo-distributor.{{- .Release.Namespace -}}.svc:4318"
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
{{- end }}
|
{{- end }}
|
||||||
|
@@ -45,7 +45,12 @@ grafana:
|
|||||||
paths:
|
paths:
|
||||||
- path: /
|
- path: /
|
||||||
# -- pathType (e.g. ImplementationSpecific, Prefix, .. etc.) might also be required by some Ingress Controllers
|
# -- pathType (e.g. ImplementationSpecific, Prefix, .. etc.) might also be required by some Ingress Controllers
|
||||||
# pathType: Prefix
|
pathType: Prefix
|
||||||
|
# backend:
|
||||||
|
# service:
|
||||||
|
# name: TODO
|
||||||
|
# port:
|
||||||
|
# number: TODO
|
||||||
# -- TLS configuration for the gateway ingress. Hosts passed through the `tpl` function to allow templating
|
# -- TLS configuration for the gateway ingress. Hosts passed through the `tpl` function to allow templating
|
||||||
#tls:
|
#tls:
|
||||||
# - secretName: grafana-tls
|
# - secretName: grafana-tls
|
||||||
|
@@ -187,7 +187,11 @@ For each of the dashboard files in charts/meta-monitoring/src/dashboards folder
|
|||||||
|
|
||||||
1. JAEGER_ENDPOINT: http address of the mmc-alloy service installed by the meta-monitoring chart, for example "http://mmc-alloy:14268/api/traces"
|
1. JAEGER_ENDPOINT: http address of the mmc-alloy service installed by the meta-monitoring chart, for example "http://mmc-alloy:14268/api/traces"
|
||||||
1. JAEGER_AGENT_TAGS: extra tags you would like to add to the spans, for example 'cluster="abc",namespace="def"'
|
1. JAEGER_AGENT_TAGS: extra tags you would like to add to the spans, for example 'cluster="abc",namespace="def"'
|
||||||
1. JAEGER_SAMPLER_TYPE: the sampling strategy, for example to sample all use 'const' with a value of 1 for the next environment variable
|
1. JAEGER_SAMPLER_TYPE: the sampling strategy, we suggest setting this to `ratelimiting` so at most 1 trace is accepted per second. See these [docs](https://www.jaegertracing.io/docs/1.57/sampling/) for more options.
|
||||||
1. JAEGER_SAMPLER_PARAM: 1
|
1. JAEGER_SAMPLER_PARAM: 1.0
|
||||||
|
|
||||||
1. If Loki is installed in a different namespace you can create an [ExternalName service](https://kubernetes.io/docs/concepts/services-networking/service/#externalname) in Kubernetes to point to the mmc-alloy service in the meta monitoring namespace
|
1. If Loki is installed in a different namespace you can create an [ExternalName service](https://kubernetes.io/docs/concepts/services-networking/service/#externalname) in Kubernetes to point to the mmc-alloy service in the meta monitoring namespace
|
||||||
|
|
||||||
|
## Configure external access using an Ingress in local mode
|
||||||
|
|
||||||
|
When using local mode by default a Kubernetes [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) object is created to access the Grafana instance. This will need to be adapted to your cloud provider by updating the `grafana.ingress` section of the `values.yaml` file provided to Helm. Check the documentation of your cloud provider for available options.
|
Reference in New Issue
Block a user