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

Can we have this plugin support for Data Center #41

Open
Trivikramreddy opened this issue Dec 12, 2018 · 6 comments
Open

Can we have this plugin support for Data Center #41

Trivikramreddy opened this issue Dec 12, 2018 · 6 comments

Comments

@Trivikramreddy
Copy link

We moved towards data center and need this plugin support data center. This would be very helpful. Thanks for all you do.

@ohanainfo
Copy link

More 1+

@AndreyVMarkelov
Copy link
Owner

Hi. It will work on DC. I will try to increase atlassian part to verify it. It is marketplace thing

@dsmorse
Copy link

dsmorse commented Apr 3, 2019

I can confirm this I have it running on some of my DC instances. With the caveat, that you have to have the Prometheus end point scrape each backend node and then aggregate the metrics in grafana. (the same way I do with bitbucket) If you have your config goes via the LB you will be betting metrics from different hosts at different times and your charts will look weird

@AndreyVMarkelov
Copy link
Owner

Btw
Atlassian took approving dc version in progress. I hope soon will be on marketplace

@Zauxst
Copy link

Zauxst commented Oct 23, 2019

I can confirm this I have it running on some of my DC instances. With the caveat, that you have to have the Prometheus end point scrape each backend node and then aggregate the metrics in grafana. (the same way I do with bitbucket) If you have your config goes via the LB you will be betting metrics from different hosts at different times and your charts will look weird

How are you actually scraping each node in jira and bitbucket?

@dsmorse
Copy link

dsmorse commented Oct 23, 2019

If your config looks like jira.example.com but that is a load balancer for jira-node1.example.com and jira-node2.examples.com you would want to configure Prometheus to scrape metrics from jira-node1 and jira-node2. This most likely will require you to set up new networking rules, because in general you don't want anything walking around the LB and going to a node directly... but we make exceptions for prometheus in our networking rules.

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

5 participants