-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change 'enterprise-client' to 'usage-client' #83
Conversation
@timraymond Thanks this looks good, yeah when I heard things were changing I realized I was going to need to do some rework. It won't be too hard. Can we get together for chat soon to make sure I understand the direction so I can make appropriate changes? |
@nathanielc Certainly! I'll find you in Slack and we'll set something up. |
client := client.New(token) | ||
client.URL = c.EnterpriseURL | ||
func NewService(c Config, l *log.Logger) *Service { | ||
client := client.New("") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timraymond I don't need the token any more correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nathanielc Yep, that's fine ✂️ . The empty string token is the same approach we've taken in Chronograf and Core for usage-only reporting.
@timraymond Overall is this what you expected? |
Enterprise Client will soon become something else entirely, so the existing enterprise-client has become 'usage-client'. The existing enterprise service now only records usage data, and discards everything else. This changes Kapacitor to use 'usage-client'.
2703b65
to
7b63a4e
Compare
@nathanielc Yep! This looks good to me 👍 |
Change 'enterprise-client' to 'usage-client'
enterprise-client
will soon be repurposed for the on-prem solution, so we have renamed the existingenterprise-client
tousage-client
. It provides the same interface, but the backend endpoints for everything except anonymous usage reporting have been no-oped. I attempted to remove stats reporting from Kapacitor, however it seems thatclient.StatsData
is used internally to facilitate writing TICK scripts against Kapacitor's own stats. Since this will require a bit more care than originally thought, for the time being this patch only switches the repos so that everything is reported tousage.influxdata.com
instead ofenterprise.influxdata.com
(since we are repurposing that subdomain as well).