profile
viewpoint

crazyscience/ant-plus 0

A node module for ANT+

crazyscience/backblaze-b2 0

Node.js Library for the Backblaze B2 Storage Service

crazyscience/bumble 0

The CMS for Laravel

crazyscience/CodeIgniter 0

EllisLab's Open Source PHP Framework

crazyscience/gitlabhq 0

Project management and code hosting application. Follow us on twitter @gitlabhq

crazyscience/grafana 0

The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More

crazyscience/koding 0

KODING IS NOW OPEN SOURCE!

crazyscience/Laravel-Phone 0

Phone number functionality for Laravel and Lumen

crazyscience/outlayer 0

:construction_worker: the brains & guts of a layout library

crazyscience/projectnami 0

WordPress powered by Microsoft SQL Server

issue commentgrafana/grafana

Support for multiple organizations

I think that both "Teams" and "Orgs" have their place. We use a multi-tenancy setup because it allows members of multiple organizations to access data from their various companies with a single user login. It also provides proper isolation for data sources. I'm not sure that the "Teams" construct will allow for this degree of isolation. Sure, we could run 15 installs of grafana and manage all that and keep track of all of our various user accounts, but it just becomes cumbersome. I'd like to throw my name into the bucket for "please, for the love of all things holy, keep Orgs".

torkelo

comment created time in a month

PR opened grafana/grafana

Fixed grammar error

<!--

Thank you for sending a pull request! Here are some tips:

  1. If this is your first time, please read our contribution guide at https://github.com/grafana/grafana/blob/master/CONTRIBUTING.md

  2. Ensure you include and run the appropriate tests as part of your Pull Request.

  3. In a new feature or configuration option, an update to the documentation is necessary. Everything related to the documentation is under the docs folder in the root of the repository.

  4. If the Pull Request is a work in progress, make use of GitHub's "Draft PR" feature and mark it as such.

  5. If you can not merge your Pull Request due to a merge conflict, Rebase it. This gets it in sync with the master branch.

  6. Name your PR as "<FeatureArea>: Describe your change", e.g. Alerting: Prevent race condition. If it's a fix or feature relevant for the changelog describe the user impact in the title. The PR title is used to auto-generate the changelog for issues marked with the "add to changelog" label.

-->

What this PR does / why we need it:

Which issue(s) this PR fixes:

<!--

  • Automatically closes linked issue when the Pull Request is merged.

Usage: "Fixes #<issue number>", or "Fixes (paste link of issue)"

-->

Fixes #

Special notes for your reviewer:

+1 -1

0 comment

1 changed file

pr created time in 3 months

push eventcrazyscience/grafana

crazyscience

commit sha 99d368c1821123af9c60b3df5b9c2fc947b63c18

Fixed grammar error

view details

push time in 3 months

fork crazyscience/grafana

The tool for beautiful monitoring and metric analytics & dashboards for Graphite, InfluxDB & Prometheus & More

https://grafana.com

fork in 3 months

more