Some extraConfigOptions not working in helm chart
See original GitHub issueI have this helm config:
elasticsearch:
extraConfigOptions:
# Common slack alert settings
generate_kibana_discover_url: True
kibana_discover_app_url: "https://kibana.digitalnz.org/app/discover#/"
kibana_discover_version: "7.14"
slack_attach_kibana_discover_url: True
However the kibana URL is not showing under my alerts.
Putting them in every rules makes the URL to show again.
According to README, those extraConfigOptions should be propagated to every rules.
Also it looks like it should work? https://github.com/jertel/elastalert2/blob/02b8393de25ccb0a4fcac0163f259ea1f2cfb433/chart/elastalert2/templates/config.yaml#L46-L47
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
jertel/elastalert-docker · GitHub - Helm Chart for Kubernetes
Parameter Description Default
image.repository docker image jertel/elastalert‑docker
image.tag docker image tag 0.2.4
image.pullPolicy image pull policy IfNotPresent
Read more >elastalert 1.8.3 · jertel/codesim - Artifact Hub
Parameter Description Default
image.repository docker image jertel/elastalert‑docker
image.tag docker image tag 0.2.4
image.pullPolicy image pull policy IfNotPresent
Read more >NixOS 23.05 manual
Using the old names will print a warning but still work. pkgs.cosign does not provide the cosigned binary anymore. The sget binary has...
Read more >Installing Praeco (ElastAlert GUI) into Kubernetes with Helm ...
This is my first Helm Chart and has not been put into production yet, and onl has been tested in k3s local Kubernetes...
Read more >Write Points From CSV to InfluxDB | by Anais Dotis - Medium
Similarly, if Telegraf is running, you can use brew to stop that service with ... not to include those rows and columns in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oooh! You’re right. Thanks for your help.
Did you mean to put
extraConfigValues
inside ofelasticsearch
block? If you look at the values.yaml you’ll see there’s already anextraConfigValues: {}
block lower down after the elasticsearch block.extraConfigValues:
block must not be inside of theelasticsearch:
block.