Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] Enable to drop monitor #145

Open
monaka opened this issue May 14, 2021 · 1 comment
Open

[feature request] Enable to drop monitor #145

monaka opened this issue May 14, 2021 · 1 comment
Assignees

Comments

@monaka
Copy link

monaka commented May 14, 2021

As a monitoring service is provided on managed K8s, some users will want to drop monitor functions.
(And in my case, telegraf pods didn't work on my AKS cluster.)

My suggestion is here: https://dev.azure.com/pizzafactory/bancarella/_git/hephy-workflow-chart/commit/01bd78ff38d8a3c7a9cefc354ddff306cb98b722?refName=refs%2Fheads%2Fmain

@Cryptophobia
Copy link
Member

This is a good idea. I have been thinking about this also recently. The monitoring stack should be easily replaceable with whatever stack the users want to use. Also telegraf/grafana/influxdb have their own charts that are a maintained by their own communities. Also prometheus is a nice replacement in this architecture also.

Maybe it is best to add a flag in the workflow values.yaml to disable to whole monitoring stack from being installed.

https://docs.teamhephy.com/managing-workflow/platform-monitoring/

@kingdonb , do you have some time to add a flag to disable the installation of the monitor components? I think we want to disable everything in monitor (except fluentd, redis-logger, and nsqd). Disable grafana, telegraf, and influxdb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants