You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2023. It is now read-only.
First wanted to say this looks like a cool project and thank you for the @librato support! If there's anything we can do on our side to help out, let us know.
IMHO including graphite in the name here is somewhat limiting in terms of marketing/branding this project. Monitoring is moving towards a more component-based approach, particularly in the separation between collecting the metrics and consuming/analyzing them. AFAIK there's nothing in this project that's specific to Graphite, Librato, or any other backend you might want to point it at?
The text was updated successfully, but these errors were encountered:
True, current name is of little relevance at this point indeed.
I've actually considered the idea (not without some prompting on irc), dunno if there's any sane way to change it short of forking the project though.
Entry points can be supported both from old name and a new one, but there doesn't seem to be a way to rename the project properly, making old name into a link to a new one, neither on github nor on pypi.
Guess I'll fork the thing next time I'll be adding or fixing something, leaving the old repo/pypi entry with some deprecation warning.
I'll keep the issue open until then as a reminder, if you don't mind.
Oh, and then of course there's a problem of coming up with a new name...
There are 2 hard problems in computer science: caching, naming, and off-by-1 errors.
First wanted to say this looks like a cool project and thank you for the @librato support! If there's anything we can do on our side to help out, let us know.
IMHO including graphite in the name here is somewhat limiting in terms of marketing/branding this project. Monitoring is moving towards a more component-based approach, particularly in the separation between collecting the metrics and consuming/analyzing them. AFAIK there's nothing in this project that's specific to Graphite, Librato, or any other backend you might want to point it at?
The text was updated successfully, but these errors were encountered: