Closed kikokikok closed 7 months ago
Hi, strange; I just tried to start a new Grafana instance, and it worked. Maybe it's related to the source that you create automatically. In the new 0.3.0 version, you don't have to set the timeField
and timeOutputFormat
.
Let me share my config; I'm using the Grafana helm chart 7.0.21, and here are my values.yaml
grafana:
resources:
requests:
cpu: 10m
memory: 128Mi
grafana.ini:
date_formats:
default_timezone: UTC
deploymentStrategy:
type: Recreate
persistence:
type: pvc
enabled: true
accessModes:
- ReadWriteOnce
size: 10Gi
datasources:
datasources.yaml:
apiVersion: 1
datasources: []
dashboards: {}
plugins:
- https://github.com/quickwit-oss/quickwit-datasource/releases/download/v0.3.0/quickwit-quickwit-datasource-0.3.0.zip;quickwit-quickwit-datasource
I will try later with your config.
Merci for the prompt response !
I am using the kube-prometheus-stack latest version 55.8.1 The grafana sub-chart is referenced as 7.1.x
Only other difference I know of is an nginx ingress with a ClusterIssuer and cert-manager configured
I updated the Grafana chart to 7.2, and it worked :/
The plugin 0.3.0 is signed so normally, you don't need the GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS
nor allow_loading_unsigned_plugins
.
I updated the Grafana chart to 7.2, and it worked :/
The plugin 0.3.0 is signed so normally, you don't need the
GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS
norallow_loading_unsigned_plugins
.
I didn't even think about trying to upgrade... I'll try that. For the unsigned, yes I figured it out once switching to debug grafana.
Thanks !
I was not able to make it work with grafana 7.2.1 subchart unfortunately. Would be curious to know if given the same packaged chart anyone could confirm or be more successful maybe which would be a sign that there might be a side effect of something else. FWIW, I am running on a local k3s running over a LimaVM on a arm64 architecture.
So I have rebundled the 55.8.1 to upgrade the grafana subchart to 7.2.x which translates into 7.2.1 kube-prometheus-stack-55.8.2.tgz
values.yaml is set with this option only ` plugins:
@kikokikok the 0.3.0 is now officially released: https://grafana.com/grafana/plugins/quickwit-quickwit-datasource/
Let me know if this is still not working.
Thanks @fmassot I do confirm it works now. Interestingly enough I kind of figured out how to make it work also with the one downloaded from github. The trick is to restart grafana pod after plugin initializaton. I haven't looked further into it since you released it to the Grafana plugin catalog.
Thanks for the help !
Hi,
Following the documentation to download and run external grafana plugins, I was able to see it was properly downloaded at helm deployment time as shown in the logs:
The plugin seems to be properly initialized:
Then for some reasons it gets stopped and the version 0.2.4 gets downloaded and installed instead
After that I have the Datasource creation automation as shown here
And here are the values.yml meaningful customization
And the datasources:
Jaeger:
Quickwit
Any idea of what I might be doing wrong here ?
Thank you !