Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

about.gitlab.com

Post reply on HN
Print view View original

1–10 of 36 posts

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#3

Post by why-el »

I am curious why you'd need to run monitoring on your own instances, since the assumption is that given a set of resources (say X RAM and Y CPU), you can support Z users. At least I remember they advertised such a number.

Now, if they somehow get to have these monitoring numbers automatically sent back to a centralized server where they can gather more insights about various installations, that would be killer, but I am not sure about the feasibility, giving the privacy implications (although plenty of open source software does it).

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#6

Post by sytse »

why-el wrote: post #3

I am curious why you'd need to run monitoring on your own instances, since the assumption is that given a set of resources (say X RAM and Y CPU), you can support Z users. At least I remember they advertised such a number. Now, if they somehow get to have these monitoring numbers automatically sent back to a centralized server where they can gather more insights about various installations, that would be killer, but I…

> I am curious why you'd need to run monitoring on your own instances, since the assumption is that given a set of resources (say X RAM and Y CPU), you can support Z users. At least I remember they advertised such a number.

We indeed publish a list of requirements https://docs.gitlab.com/ce/install/requirements.html

But this is not enough. Not all hardware is created equal (one core is faster than another) and not all users are created equal (one might push many more branches per day). So to help people with the performance of their GitLab server we think the integrated metrics will be a large benefit.

But another important reason to add this is to ensure that GitLab has metrics about applications that are deployed with GitLab.

> Now, if they somehow get to have these monitoring numbers automatically sent back to a centralized server where they can gather more insights about various installations, that would be killer, but I am not sure about the feasibility, giving the privacy implications (although plenty of open source software does it).

We're very conscious of the privacy implications of sending data about GitLab usage back. We're doing that not with Prometheus but with a usage ping in GitLab EE. We're working on bringing that usage ping to CE, for our reasoning see https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

BTW People can use Prometheus monitoring in three forms: on-premise centralized, on-premises federated, and as a SaaS

On-premises centralized is what we just shipped.

Prometheus is easy to federate, where some of the metrics of a server are included in another one. In the future we might give every deployed application its own Prometheus server in a pod.

If you want to use Prometheus as a SaaS we recommend Weaveworks https://www.weave.works/solution/prometheus-monitoring/

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#7

Post by sytse »

wldcordeiro wrote: post #5

I really love Gitlab but there's this one thing that's been niggling me about Gitlab.com and it's that every time the app is updated my sessions are invalidated and I need to go through 2FA login all over again.

Mmm, that is not the case for me. We updated to 8.16.0 a few hours ago https://twitter.com/gitlabstatus/status/823219479287107585 and I didn't have to login today. Can you please email support@gitlab.com to figure out what is wrong? Please include a link to this comment.

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#9

Post by sashk »

wldcordeiro wrote: post #5

I really love Gitlab but there's this one thing that's been niggling me about Gitlab.com and it's that every time the app is updated my sessions are invalidated and I need to go through 2FA login all over again.

Are you on Chrome by any chance? I have exactly same behaviour, which I can't track down.

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#10

Post by why-el »

sytse wrote: post #6
why-el wrote: post #3

I am curious why you'd need to run monitoring on your own instances, since the assumption is that given a set of resources (say X RAM and Y CPU), you can support Z users. At least I remember they advertised such a number. Now, if they somehow get to have these monitoring numbers automatically sent back to a centralized server where they can gather more insights about various installations, that would be killer, but I…

> I am curious why you'd need to run monitoring on your own instances, since the assumption is that given a set of resources (say X RAM and Y CPU), you can support Z users. At least I remember they advertised such a number. We indeed publish a list of requirements https://docs.gitlab.com/ce/install/requirements.html But this is not enough. Not all hardware is created equal (one core is faster than another) and not al…

Great, thank you for the detailed answer. We use and love Gitlab. ;)
Post reply on HN