In this article, see how to send InfluxDB line protocol to QuestDB.
Let’s be friends: Comment (0) Join the DZone community and get the full member experience. At QuestDB we’ve had a UDP version of the InfluxDB Line Protocol (ILP) reader in QuestDB for quite some time, but we’ve had customers ask for a TCP version of it, so we delivered! Using it, and configuring it, are relatively simple so don’t expect this to be a long post but I’ll walk you through the basics of how to set it up and use it. For an added bonus I’ll show you how to migrate from using InfluxDB to using QuestDB with a less than a line of configuration. Here’s the best part, at least for a basic implementation that you don’t need to performance tune at all: It’s already set up. That’s right, as soon as you start QuestDB both the UDP and TCP ILP listeners start automatically on port 9009. Yes, TCP and UDP both use the same port. No, that’s not a problem since one is UDP and one is TCP. There are a bunch of configuration options you can tune in your conf/server.conf file if you’re interested. I won’t go through them here, but you can read all about them in our docs. I hope they are relatively self-explanatory. If you have used ILP before, this should all be review. If you’re new to ILP, this will tell you how you should write your data to QuestDB. Pretty basic. So let’s dive into what each element actually is, and how to structure a line of ILP for writing. The first element is the table_name portion, which tells the ILP writer which database table to write values into. Next comes the set of tags you want to use. These are standard key=value pairs, and you can add as many of them as you want or need. Just separate them with commas.
