Namespaces
Table of contents
What is a “namespace”
Namespaces are labels for your events that you send to us. We use the namespace to determine if the user can ingest data, or if the user can view the data later. This makes it really easy to submit data to our API, all you need to do is send a HTTP GET request to:
Example
curl https://api.constellations.tech/v2/my-namespace?value=1234
Now my-namespace will have the value 1234 recorded for the millisecond the event arrived at the API. No need to set up TCP/UDP channels, or manage a global network of ingest stations. Our API is built to withstand millions of events per day so you don’t have to worry about scaling.
Due to batching, your new data may not show for a maximum of 1 minute.
Tagging events
Tags are a secondary way of filtering events that are ingested to Constellations. It allows you to break down data by tag and namespace. In custom dashboards and embeds, you can add multiple lines based on the tag value or you can create bar/pie charts breaking down the percentages of tags.
Example
curl https://api.constellations.tech/v2/my-namespace?value=1234&tag=my-tag
Below is a great example of how to use tags to display different data in the same namespace. This graph will allow you to collect all the tags together to generate a larger “database latency” graph, while also allowing you to see the latency per command.
All of these visualizations provided without needing to overhaul your code. How cool is that?