10:31 p.m.
Hello Everybody,
Here is a list of major features and enhancements planned for 0.3.2 and beyond:
1) REST API - the end-points will be separated based on the metric type. Current
availability and numeric, will be joined by counter and gauges metrics.
2) Counters and gauges - add two new specialized metric types to allow more flexibility
for clients.
3) Numeric Aggregates - Will allow long-term storage of numeric metrics at the expense of
losing some fidelity. The design is already in progress. Because this is a really complex
feature, the expectation is to start the work in 0.3.2 and publish a mini-roadmap.
4) Enhanced Availability - while the current model works, the goal would be expand this to
cover most of the use cases brought up in the community threads. We will start the design
in 0.3.2 with the implementation expected in future releases.
4) Go client - will help integrating with third party metrics collection framework. This
work is the foundation for the Heapster sink.
5) Public Java API - following the work done in 0.3.1 in the core of the project, the goal
is to separate the implementation from a public API and make that available to clients
6) Update REST testing - the current set of tests is a good gauge for regressions, but the
overall coverage is still low. The plan for 0.3.2 is to increase coverage.
Any discussion, suggestions or contributions are more than welcomed; so feel free to reply
to this email or join #hawkular on freenode.
Thank you,
Stefan Negrea
Software Engineer
10:32 p.m.
New subject: Hawkular Metrics - 0.3.2 & Beyond - Release Planning
Hello Everybody,
Here is a list of major features and enhancements planned for Hawkular Metrics 0.3.2 and
beyond:
1) REST API - the end-points will be separated based on the metric type. Current
availability and numeric, will be joined by counter and gauges metrics.
2) Counters and gauges - add two new specialized metric types to allow more flexibility
for clients.
3) Numeric Aggregates - Will allow long-term storage of numeric metrics at the expense of
losing some fidelity. The design is already in progress. Because this is a really complex
feature, the expectation is to start the work in 0.3.2 and publish a mini-roadmap.
4) Enhanced Availability - while the current model works, the goal would be expand this to
cover most of the use cases brought up in the community threads. We will start the design
in 0.3.2 with the implementation expected in future releases.
4) Go client - will help integrating with third party metrics collection framework. This
work is the foundation for the Heapster sink.
5) Public Java API - following the work done in 0.3.1 in the core of the project, the goal
is to separate the implementation from a public API and make that available to clients
6) Update REST testing - the current set of tests is a good gauge for regressions, but the
overall coverage is still low. The plan for 0.3.2 is to increase coverage.
Any discussion, suggestions or contributions are more than welcomed; so feel free to reply
to this email or join #hawkular on freenode.
Thank you,
Stefan Negrea
Software Engineer
10:33 p.m.
Really sorry but I missed the Metrics word in the title. This is the release planning for
Hawkular Metrics. I resent the email with the proper subject, so we can continue the
discussion in that context.
Thank you,
Stefan
----- Original Message -----
From: "Stefan Negrea" <snegrea(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Tuesday, April 7, 2015 3:31:34 PM
Subject: [Hawkular-dev] Hawkular 0.3.2 & Beyond - Release Planning
Hello Everybody,
Here is a list of major features and enhancements planned for 0.3.2 and
beyond:
1) REST API - the end-points will be separated based on the metric type.
Current availability and numeric, will be joined by counter and gauges
metrics.
2) Counters and gauges - add two new specialized metric types to allow more
flexibility for clients.
3) Numeric Aggregates - Will allow long-term storage of numeric metrics at
the expense of losing some fidelity. The design is already in progress.
Because this is a really complex feature, the expectation is to start the
work in 0.3.2 and publish a mini-roadmap.
4) Enhanced Availability - while the current model works, the goal would be
expand this to cover most of the use cases brought up in the community
threads. We will start the design in 0.3.2 with the implementation expected
in future releases.
4) Go client - will help integrating with third party metrics collection
framework. This work is the foundation for the Heapster sink.
5) Public Java API - following the work done in 0.3.1 in the core of the
project, the goal is to separate the implementation from a public API and
make that available to clients
6) Update REST testing - the current set of tests is a good gauge for
regressions, but the overall coverage is still low. The plan for 0.3.2 is to
increase coverage.
Any discussion, suggestions or contributions are more than welcomed; so feel
free to reply to this email or join #hawkular on freenode.
Thank you,
Stefan Negrea
Software Engineer
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3300
days inactive
3300
days old
2 comments
1 participants
participants (1)
-
Stefan Negrea