On Wed, Nov 23, 2016 at 3:24 AM, Marco B. <[email protected]> wrote:
> > > Il giorno martedì 22 novembre 2016 17:56:38 UTC+1, Sean Beckett ha scritto: >> >> >> >> On Tue, Nov 22, 2016 at 7:44 AM, Marco B. <[email protected]> wrote: >> >>> Hello everyone, >>> >>> I have a scenario with one InfluxDB and multiple users (belonging to the >>> same organization) writing metrics into it. >>> Each of these users should be able to access at least their own data, >>> but not necessarily someone else's data. >>> >>> I would like to know what the recommended ways are to deal with such >>> cases: >>> >>> 1) multiple databases? how many databases can one influxDB instance >>> handle? >>> >> >> This is what I would recommend, since user permissions are scoped by >> database. That way you can grant explicit read/write permissions for each >> user to only their own data. InfluxDB can handle thousands of databases, >> provided the overall series cardinality is not too high. >> >> > Great! > > >> >> >>> 2) tags? I have read that this is not recommended, due to the fact it's >>> not possible to join by measurements, etc. >>> 3) prefix the tenantId in the measurement (and one single db, multiple >>> tenants) >>> 4) fields? >>> >>> In the case of the "tenantID" as prefix to a measurement (which seems to >>> be one of the recommended ways >>> <https://groups.google.com/forum/#!searchin/influxdb/multi-tenant%7Csort:relevance/influxdb/-PsxC6Azl0U/n1EPXU3NpEkJ>), >>> how do I prevent a tenant from querying metrics that should be private? >>> >>> For example, with the following data: >>> >>> tenant1.cpu.load.avg >>>> tenant2.cpu.load.avg >>>> >>> >>> both tentants could be able to execute a query like "Show measurements" >>> and get data that they should not see. If I add a proxy to it, then I would >>> lose the advantages that Influx provides, right? >>> >> >> That's a terrible schema for InfluxDB 0.9+, anyway. Encode metadata in >> tags, not in the measurement name. Otherwise you will have serious >> limitations in what can be queried, and performance will be much worse. >> >> > > Oh, this explains a lot! I think I may have misunderstood the link I > posted, because there it's mentioned to use a prefix in the measurement. > Thanks for clarifying! > That discussion is about InfluxDB prior to version 0.9. In InfluxDB 0.8 and previous, metadata was encoded in the measurements, Graphite-style. That was changed in InfluxDB 0.9: https://docs.influxdata.com/influxdb/v0.9/concepts/08_vs_09/#schema > > >> >>> Assuming that the case (1) is feasible, how do you normally handle the >>> reloading of the Influx configuration file? >>> In one of my scenarios, this is necessary because you have to specify >>> the database in the [graphite] section, and if a new user/database is >>> created, then Influx needs to be restarted. Is there another way to do so? >>> >> >> If you change the config file, InfluxDB must be restarted to pick up >> those changes. >> > > Okay! > >> >> >>> >>> I would like to know how in general how to handle such use cases with >>> Influx and Grafana. Do you have any resources about it? >>> Thanks in advance! >>> >>> - Marco >>> >>> -- >>> Remember to include the version number! >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "InfluxData" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/influxdb. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/influxdb/2d0b9419-3b31-4d6b-be19-25c1f96a06c0%40googlegroups.com >>> <https://groups.google.com/d/msgid/influxdb/2d0b9419-3b31-4d6b-be19-25c1f96a06c0%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Sean Beckett >> Director of Support and Professional Services >> InfluxDB >> > -- > Remember to include the version number! > --- > You received this message because you are subscribed to the Google Groups > "InfluxData" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/818851b7-36f0-43f4-a278-9e12e6a58bc0%40googlegroups.com > <https://groups.google.com/d/msgid/influxdb/818851b7-36f0-43f4-a278-9e12e6a58bc0%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvOsK%3D9zVRkVE3haTXRY0EWO5bVoKjjdsikzM86Gx5_EEw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
