[Hawkular-dev] Status Report - Week 9 2015
Accomplishments and key updates:
- HWKBTM-342 Fix minor formatting inconsistency between BTM standalone and Hawkular
integration UI for the APM page. Also integrated UI dropdown defaults were incorrect on
the APM page.
- Test and released 0.7.1.FInal of BTM, and merged HWKBTM-312 to integrate BTM into
Hawkular.
- Test and release BTM 0.7.2.Final with changes required by parent 36 (relocation of
modules artifacts).
- Completed work on HWKBTM-268 to derive communication (latency) information and provide a
REST endpoint for obtaining graph nodes/links for creating a graphical representation of
the communication between distributed services.
- HWKBTM-353 When obtaining communication details, need to identify the initial fragment
as a client (previously based on same uri as the consumer)
- ENTESB-5040 Work with GSS to investigate and fix RTGov/Swyd classpath conflict around
drools
- Trying out node.js as possible next instrumentation environment. Found an interesting
project (https://github.com/ValYouW/njsTrace) that can instrument a nodejs app - quite
flexible but doesn't give access to all the information we would require, but
demonstrates the approach that can be taken to achieve the desired results
Next steps:
- HWKBTM-340 More accurately calculate the completion time across a business txn with
multiple fragments.
- More node.js investigation as a background task
Risks:
- none
Asks for Thomas:
- none