Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
GitLab Community Edition
GitLab Community Edition
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 10,406
    • Issues 10,406
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 548
    • Merge Requests 548
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Community EditionGitLab Community Edition
  • Issues
  • #28916

Closed
Open
Opened Mar 02, 2017 by Joshua Lambert@joshlambert 
  • Report abuse
  • New issue
Report abuse New issue

Enhance Prometheus integration for managed deployments on Kubernetes

Description

We are now able to deploy Prometheus servers to connected Kubernetes clusters with a single button (#41053 (closed)). With GitLab's multi-cluster support, this can mean either a single or multiple Prometheus servers for a given project.

We now need to take this further to make the experience seamless:

  1. Automatically enable Prometheus integration, configured for each deployed Prometheus instance
  2. Logic to determine which Prometheus server to utilize for a given environment, if multiple clusters are connected.
  3. Utilize the Kubernetes API to securely query the Prometheus servers without requiring them to be externally reachable outside the cluster

The general user flow will be:

  1. User connects a Kubernetes cluster(s)
  2. Deploys Helm Tiller, then Prometheus
  3. At this point, Prometheus integration is now automatically enabled. Manually configuring the Prometheus URL is now disabled, instead showing that this is being automatically managed.
  4. Monitoring UI elements now appear, and will function as expected for environments which have had a Prometheus server deployed.
  5. In the event that the cluster for an environment does not have Prometheus deployed, they will see the empty state.

One note, the currently deployed Ingress does not have metrics enabled or proper annotations for Prometheus monitoring. This is being resolved in #39985 (closed).

Designs

Note: The general design and user experience for installing applications in the Cluster page is found in #38464

🔍 View design specs (for spacing, sizes, colors and text copying) — Hide notes in the top-right corner

Edited Feb 01, 2018 by Joshua Lambert

Related issues

Assignee
Assign to
Epic
10.5
Milestone
10.5
Assign milestone
Time tracking
None
Due date
No due date
11
Labels
Deliverable In review Monitoring UX ready backend direction docs-missing feature proposal frontend i2p-on-gke kubernetes
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ce#28916