Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

POLL: Help us choose a new name for this project #243

Closed
akulkarni opened this issue Sep 5, 2020 · 17 comments
Closed

POLL: Help us choose a new name for this project #243

akulkarni opened this issue Sep 5, 2020 · 17 comments

Comments

@akulkarni
Copy link
Member

akulkarni commented Sep 5, 2020

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!

@akulkarni
Copy link
Member Author

Prombase

@akulkarni
Copy link
Member Author

Promscale

@akulkarni
Copy link
Member Author

Hestia

@akulkarni
Copy link
Member Author

Lantern

@akulkarni
Copy link
Member Author

FireTiger

@Harkishen-Singh
Copy link
Member

Harkishen-Singh commented Sep 5, 2020

Promscale

I was about to say this in the meeting yesterday. Happy to see the option 😊.

@akulkarni
Copy link
Member Author

Thanks everyone for the votes so far! Question: Which one is your favorite, and why?

@Harkishen-Singh
Copy link
Member

Harkishen-Singh commented Sep 11, 2020

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!

@cevian
Copy link
Contributor

cevian commented Sep 11, 2020

I like FireTiger because of the bold visual it evokes

@niquola
Copy link

niquola commented Sep 11, 2020

@JLockerman
Copy link
Contributor

@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.

@JLockerman
Copy link
Contributor

JLockerman commented Sep 11, 2020

Some pros+/cons- for the current suggestions:

  • Prombase
    • + sounds prometheus related
    • - kinda sounds like the backend for prometheus, I'd expect something with that name to be a prometheus-internal project no one else ever looks at
  • Promscale
    • + If you've heard of Prometheus and Timescale, you can probably figure out what it is
    • + sounds like what it does
  • Hestia
    • + obviously a proper noun
  • Lantern
    • pretty neutral, something like "Timescale Lantern" or "Prometheus Lantern" might be better
  • FireTiger
    • + great imagery
    • - sounds like a kind of thing, not like the name of a thing

@recollir
Copy link

Portunus - the Roman god that originally protected warehouses. It also starts with a “P”.

@SuperQ
Copy link

SuperQ commented Sep 12, 2020

I like the "Timescale Lantern", the url being github.com/timescale/lantern seems nice.

@bwplotka
Copy link

Timeus ! (:

While Promscale sounds cool, I am not sure how Timescale actually scales Prometheus - while it claimed to be "scalable" looks like the selling point is that it offers unique usability features with SQL queries + analytics. But it's only my humble opinion.

PromSQL sounds cool also 😉

@nvtkaszpir
Copy link

nvtkaszpir commented Sep 23, 2020

Chonker.

Sorry I just couldn't resist:

  • Timescale already has a cat in the logo (tiger)
  • timescaledb supports big amount of data, that is usually sliced in chonks, erm chunks
  • everyone loves cats
  • this is a type of the cat you just let it rest in cozy place and keep feeding it with what it likes
  • cats will throw items from the counters, we can reference it as 'data' retention ;)
  • timescaledb when not queried will loaf around, just like cat does it
  • even though some are big ones, they tend to fit into even the smallest boxes

;D

cevian added a commit that referenced this issue Sep 24, 2020
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.
cevian added a commit that referenced this issue Sep 24, 2020
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.
cevian added a commit that referenced this issue Sep 24, 2020
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.
cevian added a commit that referenced this issue Sep 25, 2020
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.
cevian added a commit that referenced this issue Sep 25, 2020
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.
cevian added a commit that referenced this issue Sep 25, 2020
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.
cevian added a commit that referenced this issue Sep 25, 2020
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.
@cevian
Copy link
Contributor

cevian commented Sep 25, 2020

Thanks for the votes everyone. We decided to go with Promscale as seen in issue #267

cevian added a commit that referenced this issue Sep 25, 2020
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.
@cevian cevian closed this as completed in 40d466f Sep 25, 2020
timflannagan pushed a commit to timflannagan/promscale that referenced this issue Sep 30, 2020
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.
timflannagan pushed a commit to timflannagan/promscale that referenced this issue Sep 30, 2020
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.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants