Skip to content
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

Information to collect #5

Open
mbax opened this issue Aug 14, 2014 · 4 comments
Open

Information to collect #5

mbax opened this issue Aug 14, 2014 · 4 comments

Comments

@mbax
Copy link

mbax commented Aug 14, 2014

Before plugin/reports/api/website can continue much further we need a defined plan on what information will be collected and how it will be collected.

Do we just want collecting values, and then have the developer define what they mean website-side?

@mbax mbax added the question label Aug 14, 2014
@gdude2002
Copy link
Contributor

Well I'm assuming what we're collecting with to start with is basic system stuff, like..

  • CPUs
  • RAM

And then we have the actual Bukkit stuff..

  • List of plugins using Statik
  • Bukkit, Java versions

On top of that, I think we were going to allow developers to submit their own metrics values, which they'd define the graphs for on the site.

@mbax
Copy link
Author

mbax commented Aug 14, 2014

I wasn't clear enough, I guess. I'm referring to what type of data we're tracking.

Data like java version is static content where you'd be measuring how many servers have $version.

Data like "Number of uses of $feature in last half hour" is a situation where we're incrementing a value until the data is sent and then starting from 0 again.

What other types of data am I missing? I want to make sure everything's fairly well covered before I dive into the plugin code and write myself into a corner. Plus, we need to make sure the API's capable of outputting it in a useful manner, and the website is capable of displaying it in a useful manner, and reports is capable of processing it in a useful manner, etc:3

@Ribesg
Copy link
Member

Ribesg commented Aug 15, 2014

I think that we should let the user define this. For example, we could have:

  • The maximum value of X since the last data sent
  • The minimum value of X since the last data sent
  • The average value of X since the last data sent
  • The amount of X in the last data sent

But that list isn't complete and will never be. We can't think about everything, that's what I think that the user should be responsible of this. When we ask the user for data to send, he just gives us a Map<String, Object>, Object being one of the primitives types or String.

The user should be responsible of what he sends.

I think each data value's String should be an id (maybe enforce single word), and everything like Title, Description etc should be configured on the Website. Also, a data id could be used multiple times.

@gdude2002
Copy link
Contributor

Maybe it would be easier to implement based on what Highcharts supports? Though, that might make it hard to extend later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants