aboutsummaryrefslogtreecommitdiffstats
path: root/sources/hv-collector-domain
AgeCommit message (Collapse)AuthorFilesLines
2019-06-27JJB alignment across DCAE components - DCAE HV-VESrajendrajaiswal1-1/+1
Change-Id: I815c32a91a3e710d9076495dbafcba420bde4da5 Issue-ID: DCAEGEN2-1578 Signed-off-by: rajendrajaiswal <rajendra.jaiswal@ericsson.com>
2019-05-06Update versions for El Alto releasePiotr Jaszczyk1-1/+1
Change-Id: If86dcbf8695cc50a540fe892a4f70b3ad24ac5d1 Issue-ID: DCAEGEN2-1474 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2019-04-12Creation of server modulekjaniak11-1/+503
Issue-ID: DCAEGEN2-1390 Change-Id: I07410b16ed6566b933d5f1efa35bddb965225794 Signed-off-by: kjaniak <kornel.janiak@nokia.com> Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-04-04Get rid of arrow-effects usagePiotr Jaszczyk1-1/+1
Also clean-up dependencies + use Kotlin BOM to force single kotlin-stdlib on classpath. Issue-ID: DCAEGEN2-1392 Change-Id: I447c4686707de81f35f7734255ce0b13c997c4a4 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2019-03-28Redefine RoutingFilip Krzywka1-2/+7
As all needed information to route messege is contained inside of KafkaSink message, we can simply put this object as part of single Route. Change-Id: I2e7df2e0193eb2af5283980d4d5c8df03ac94df9 Issue-ID: DCAEGEN2-1347 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-03-14Extract HV-VES configuration moduleFilip Krzywka3-10/+24
To avoid cyclic dependency between "modules trio" configuration-core-ssl some classes from core.model were also extracted. Change-Id: Ie11029ae3500964f67f4d72279ddd68cdb2a1f0c Issue-ID: DCAEGEN2-1332 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2019-03-11Assure coverage is checked for all modulesPiotr Jaszczyk1-4/+0
Change-Id: Ia9bb6cef9154d64cfa45455e38c9fe7603a64c74 Issue-ID: DCAEGEN2-1328 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2019-02-19Use SDK/SSL in HV-VESPiotr Jaszczyk2-22/+6
Issue-ID: DCAEGEN2-1226 Change-Id: I7cfc09001f7315c1b6f4fcf150ad631630c810ef Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2019-02-18Merge "Generate VesEvents in hv-ves/message-generator"Piotr Jaszczyk1-1/+2
2019-02-15Generate VesEvents in hv-ves/message-generatorJakub Dudycz1-1/+2
- Split message generator on two specialized generators for VesEvent and WireFrame related message types - Refactor whole message-generator module Change-Id: I1266b549a9a4d27213d03e8921298deab2dacb59 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1162
2019-02-14Use protobuf definitions from SDKFilip Krzywka3-111/+5
Change-Id: I22163f3239769070e1e04c8d0e8f0da179069632 Issue-ID: DCAEGEN2-1218 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-17Metric: Processing timePiotr Jaszczyk1-1/+4
Add processing time metric measured as difference between "sent to DMaaP" and "WTP decoded" events. Change-Id: I73bb665145019fcca5ae36e2199ed0e1cc088fdf Issue-ID: DCAEGEN2-1036 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-13Align logback configurationFilip Krzywka1-54/+0
- followed current logging guidelines in regard of format - in simulators currently very simple (minimalistic) pattern will be used as they do not contain any MDCs or Markers - in main logbacks included three patterns varying on verbosity and human-readability (for production full logging, ie. ONAP_LOG_PATTERN, should be used) - removed logback-test from domain module as it was not enabled anyway (no dependency on logback) and we should never have need for logging in this module - made logback-tests consistent (using simple pattern) except in component-tests, where it might be useful to have more verbose output (including MDCs etc.) Change-Id: Ifd851d12a77d5303b836a25c0e168e18a3a804e9 Issue-ID: DCAEGEN2-1026 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-04Harmonize logging and add new logsFilip Krzywka4-12/+36
- corrected docker-compose consul url Change-Id: I78df868e0dd51008ef39d01553e6a0a3b8273a54 Issue-ID: DCAEGEN2-1003 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-29Custom detekt rule for logger usage checkPiotr Jaszczyk13-0/+992
Check if logger invocations don't use unoptimal invocations, eg. concatenation `debug("a=" + a)` instead of lambda use `debug {"a=" + a}` Unfortunately to avoid defining dependencies in many places and having circural dependencies it was necessarry to reorganize the maven module structure. The goal was to have `sources` module with production code and `build` module with build-time tooling (detekt rules among them). Issue-ID: DCAEGEN2-1002 Change-Id: I36e677b98972aaae6905d722597cbce5e863d201 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>