-
Notifications
You must be signed in to change notification settings - Fork 169
POLL: Help us choose a new name for this project #243
Comments
Prombase |
Promscale |
Hestia |
Lantern |
FireTiger |
I was about to say this in the meeting yesterday. Happy to see the option 😊. |
Thanks everyone for the votes so far! Question: Which one is your favorite, and why? |
I believe Promscale is the perfect name since Timescale-Prometheus enables Prometheus to run without any worries (from the database layer side, making it more of a stateless kind of service (excluding WAL since 2 hours of data in WAL is less to be considered when you have years of metrics data)). This allows Prometheus to scale to new heights where sky is the limit. Also do note that the Go-scheduler has to work (on the Prometheus side) less since the db layer is now decoupled into a much reliable and trusted Postgres storage. Not to forget, the power of joins! |
I like FireTiger because of the bold visual it evokes |
@cevian the thing about FireTiger is that the name gives no indication of what the project does. The others at least sound like proper nouns, and Promscale is kinda explanatory, if you already know what Prometheus and Timescale are. |
Some pros
|
Portunus - the Roman god that originally protected warehouses. It also starts with a “P”. |
I like the "Timescale Lantern", the url being |
While
|
Chonker. Sorry I just couldn't resist:
;D |
This PR renames the connector from Timescale-Prometheus to Timescale. The renaming of the extension is left to a future PR. This is inline with the poll in issue #243.
This PR renames the connector from Timescale-Prometheus to Timescale. The renaming of the extension is left to a future PR. This is inline with the poll in issue #243.
This PR renames the connector from Timescale-Prometheus to Timescale. The renaming of the extension is left to a future PR. This is inline with the poll in issue #243.
This commit renames the connector from Timescale-Prometheus to Promscale. The renaming of the extension is left to a future commit. This is inline with the poll in issue #243.
This is inline with the general renaming we are doing from Timescale-Prometheus to Promscale. Dropping the extra prefix as it is weird and redundant. This completes the rename. Fixes #243.
This commit renames the connector from Timescale-Prometheus to Promscale. The renaming of the extension is left to a future commit. This is inline with the poll in issue #243.
This is inline with the general renaming we are doing from Timescale-Prometheus to Promscale. Dropping the extra prefix as it is weird and redundant. This completes the rename. Fixes #243.
Thanks for the votes everyone. We decided to go with Promscale as seen in issue #267 |
This commit renames the connector from Timescale-Prometheus to Promscale. The renaming of the extension is left to a future commit. This is inline with the poll in issue #243.
This commit renames the connector from Timescale-Prometheus to Promscale. The renaming of the extension is left to a future commit. This is inline with the poll in issue timescale#243.
This is inline with the general renaming we are doing from Timescale-Prometheus to Promscale. Dropping the extra prefix as it is weird and redundant. This completes the rename. Fixes timescale#243.
Now that this project is getting a lot of usage, we are considering giving it a new name (partly to give it its own identity, partly because we're tired of typing "timescale-prometheus" all the time 😁).
Here is the vision for this project:
Serves as the analytics database for Prometheus metrics
Supports full PromQL and SQL natively, so compatible with all SQL-based tools (including ML libraries / tools)
Allows you to join Prometheus metrics with other data in your system
Built on top of TimescaleDB, so includes native compression, horizontal scaling, high-performance, reliability, etc
Summary: There are many long-term storage options available, but this one is uniquely focused on advanced analytics, enabled by the relational data model, in addition to basic PromQL, etc
We would really like feedback from Timescale-Prometheus users as well as from the general Prometheus community. In particular, we want to make sure that we are doing right by the Prometheus community and aren't breaking any public or unspoken naming guidelines.
There is a list of names below. Please give the one(s) you like with a 👍 emoji. Please also feel free to leave any comments on why you like or don't like certain names. (And if you feel so inclined - feel free to suggest any names you might have as well 😊.)
Thanks!
The text was updated successfully, but these errors were encountered: