Influx Database features

Hi,Need some help on the basic Influx Questions.
1.Does Influx support Views Concept as RDBMS?
2.How can i come to know Which User id created/owner of the measurement?
3.What is the restriction on naming measurement/field/tag length?
4.how to know on a daily basis which user ran how many queries?
5.How to check which query taking what amount of memory during run.I have seen EXPLAIN shows few stats but that shows before the query execution.
6.How can i achieve the Joins between measurements other than Flux?
7.What is the limit on databases creation per cluster?
8.Any detailed documentation on v_internal schema?
9.Retention Policies internal architecture?
10.How can we restrict users not to create un-necessary measurements?

  1. You can store your Flux query in variables which can make querying easier. You can also save dashboards with specific queries and build upon those. You can also write tasks that write a portion of your data to a new bucket if you need to isolate a portion of your data.
  2. Please take a look at this documentation if you haven’t already. Manage users in InfluxDB | InfluxDB OSS 2.0 Documentation
    You can give users read and write permissions/token that are scoped to individual buckets. I don’t think there’s a way to know who was responsible for writing data to a specific measurement.
  3. I’m not sure what the restriction is (I know you can have a pretty long name) However, best practice is not to encode data in a single measurement or tag. Instead split that data up into several tags. Please read this for more information (especially the last section): Data Layout and Schema Design Best Practices for InfluxDB | InfluxData for an example.
  4. You can use the cardinality now dashboard to help you monitor your series cardinality and the tasks you ran:
    TL;DR InfluxDB Tech Tips - Monitoring Tasks and Finding the Source of Runaway Cardinality | InfluxData
    You can also monitor your usage in the usage tab in the UI, including query count.
  5. I’m not sure, but you might find value in: telegraf/plugins/inputs/influxdb at master · influxdata/telegraf · GitHub
  6. You can’t achieve joins other than Flux out of the box. Otherwise you can use any client library and perform the data transformation with the language of your choosing. You might also want to look at the execd processor plugin if you need to do this type of transformation upfront.
  7. I’m not sure what the limit is on bucket or database creation. I’ll make sure to share this question with experts. I appreciate your patience while they get back to you.
  8. What type of detailed documentation are you looking for specifically? Or what do you think needs improvement?
  9. Can you describe what you mean here? Or what you’re looking for exactly? This blog might be useful to you though: Simplifying InfluxDB: Shards and Retention Policies | InfluxData
  10. You can give them read permissions only. Or scope their write permissions to specific buckets. TL;DR InfluxDB Tech Tips: Creating Tokens with the InfluxDB API

Does that help?
Thanks for your question :slight_smile: and please let me know.

(Assuming OSS) For 7, the system doesn’t enforce a limit on the number of DB/buckets, but we’ve found that system performance starts to decline if > 20 buckets are being actively queried/written to at a time.