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

Jump to bottom

Feature: Utilizing existing monitoring stack setup #3068

Closed
2 tasks done
benjaminhuo opened this issue Nov 3, 2020 · 2 comments
Closed
2 tasks done

Feature: Utilizing existing monitoring stack setup #3068

benjaminhuo opened this issue Nov 3, 2020 · 2 comments
Assignees
@benjaminhuo
Labels
area/monitoring kind/feature-request Request a feature
Milestone
3.1.0

Comments

@benjaminhuo
Copy link
Member

benjaminhuo commented Nov 3, 2020 •
edited

  • Utilizing existing monitoring stack setup including existing:
  • Prometheus
  • Prometheus operator
  • Node Exporter
  • kube-state-metrics

Install these components if not present

  • Applying KubeSpere custom content such as: custom Prometheus recording & alert rules.

/assign @benjaminhuo
/kind feature-request
/area monitoring
/Milestone 3.1.0
@benjaminhuo benjaminhuo changed the title Feature: Utilizing existing monitoring stack setup Feature: Utilizing existing monitoring stack Nov 3, 2020
@benjaminhuo benjaminhuo changed the title Feature: Utilizing existing monitoring stack Feature: Utilizing existing monitoring stack setup Nov 3, 2020
@benjaminhuo benjaminhuo added this to the 3.1.0 milestone Nov 3, 2020
This was referenced Nov 3, 2020
Closed
Closed
@benjaminhuo
Copy link
Member Author

Similar issue #3078

@benjaminhuo
Copy link
Member Author

This has been implemented by kubesphere/ks-installer#1164 and https://kubesphere.io/docs/faq/observability/byop/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benjaminhuo benjaminhuo

Labels
area/monitoring kind/feature-request Request a feature
Projects
None yet
Milestone
3.1.0
Development

No branches or pull requests
2 participants
@benjaminhuo @ks-ci-bot