Hi
Hawkular APM is currently built as a separate distribution independent from other Hawkular
components. However in the near future we will want to explore integration with other
components, such as Alerts, Metrics and Inventory.
Therefore I wanted to explore the options we have for building an integrated environment,
to provide the basis for such integration work, without impacting the more immediate plans
for Hawkular Services.
The two possible approaches are:
1) Provide a maven profile as part of the Hawkular Services build, that will include the
APM server. The UI could be deployed separately as a war, or possibly integrated into the
UI build?
2) As suggested by Juca, the APM distribution could be built upon the hawkular-services
distribution.
There are pros/cons with both approaches:
My preference is option (1) as it moves us closer to a fully integrated hawkular-services
solution, but relies on a separate build using the profile (not sure if that would result
in a separate release distribution).
Option 2 would provide the full distribution as a release, but the downside is the size of
the distribution (and its dependencies, such as cassandra), when user only interested in
APM. Unclear whether a standalone APM distribution will still be required in the future -
at present the website is structured to support this.
Thoughts?
Regards
Gary