Comments (2)
This proved to be a tougher nut to crack than expected, but after some experimentation and bouncing off some walls, here is what I came up with:
- The name "prefix" seems too implementation specific. I'd recommend going back to the "namespace" terminology as it's easier to explain without delving too much into the implementation.
- I did some research and it seems there is nothing against sending a query string in a POST request (ie. the HTTP spec does not specifically deny it and people seem to accept it as a viable solution). Why is a query string better? Easier to represent in the OpenAPI spec.
With those in mind:
- OpenMeter would create a "default" (empty) namespace on launch (In case of Kafka and KSQLDB this means the current behavior)
- Sending a
POST /api/namespaces
request will create a namespace (TODO: come up with a validation rule for the name) (In case of Kafka and KSQLDB, it means new events and detected_events topic/table) - Sending a
POST /api/ingest
request (without namespace) will land the event in the "default" (empty) namespace (ie. no topic name prefix) - Sending a
POST /api/ingest?namespace=asd
request will land the event in the "asd" namespace (ie. topic name will be om_asd_events)
It took me some time to figure out a way to even think about the prefix concept in a consistent way and I realized that it's not a good term we can easily explain or reason about, so I decided to change it.
Let me know what you think.
from openmeter.
This is done
from openmeter.
Related Issues (20)
- Refactor configuration
- Instrument redis
- Move log configuration under telemetry section
- Move configuration to its own package and split into smaller files (`config.go` is long as it is and not really readable)
- Write some basic tests to ensure configuration is properly loaded
- Create new meter query endpoint
- Create new subjects endpoint HOT 1
- Create new groupBys endpoint
- Process Messages in DQL (Dead Letter Queue)
- Create and configure DQL (Dead Letter Queue) topic programmatically
- Refactor Kafka Connect configuration
- Add CI check for generated code
- Python client HOT 5
- FinOps Open Cost & Usage Specification Support HOT 1
- Investigate query timeouts due to ClickHouse connection pool limit
- Improve Kafka Config around disabling IPv6 for OSX
- Introduce interface for deadlettering
- Integrate OTel with Sink Worker
- Detect OpenAPI breaking changes
- OpenMeter .NET 8 SDK HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openmeter.