Right now influxdb stores everything from UDP into a single database named like "udp". Is it possible and reasonable to add some routing based on the metrics tag, so that we can route different metrics to different databases instead of put everything in a single database?
It is possible, but I am not sure if and when we'll do it. However there is nothing stopping you running multiple UDP services, and routing traffic from each to different databases. Perhaps that would work?
PRs for your proposed feature welcome, of course.
Thanks. Multiple UDP services would work if I have limited and defined number of databases. Maybe I will think about making a PR.
For resource management we'd love a feature where we can setup a UDP config that allows us to route certain metric names (via regexp) to a specific DB. This would give us good insights into resource requirements downstream and I think it will also make accessing Influx from Grafana more controlled in that we can allow certain users to access certain DBs depending upon the type of metrics they are working with.
I am wonder what was a reason to tie udp and database? Why I can't use fully qualified name (database."rp".measurement) in line protocol?
@acmnu Here is the reason.
Disclaimed: It's issue #6037
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.
Most helpful comment
I am wonder what was a reason to tie udp and database? Why I can't use fully qualified name (database."rp".measurement) in line protocol?