aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-01-03Add script for sending messages from multiple xNFsFilip Krzywka8-68/+390
Change-Id: I9acd3278929c30a3036f97f403a31a8817723d27 Issue-ID: DCAEGEN2-1027 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-27Rename of metricskjaniak2-105/+65
Names of metrics were a bit misleading e.g. total and count addition to name of metrics. Clean up in unit tests. Change-Id: I339c8824f31a226bdbe648027b114321e3fd9858 Issue-ID: DCAEGEN2-1046 Signed-off-by: kjaniak <kornel.janiak@nokia.com>
2018-12-21Merge "Enable setting log level from command line"Piotr Jaszczyk9-164/+316
2018-12-21Enable setting log level from command lineIzabela Zawadzka9-164/+316
Change-Id: I8397e0134d254cd5b6be79ed2b847ce265fc775c Signed-off-by: Izabela Zawadzka <izabela.zawadzka@nokia.com> Issue-ID: DCAEGEN2-1045
2018-12-21Fix misleading logs when obtaining consul configJakub Dudycz2-22/+49
Change-Id: Idaccc954a0fdc03c6336e6f126f8c7e99010956d Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1048
2018-12-20There should be one KafkaSender per configurationPiotr Jaszczyk27-113/+297
We should keep only one instance of KafkaSender per instance. However, as the configuration might be changed (Consul update) it cannot be a strict singleton. Hence there should be 1to1 relationship beetween ConsulConfiguration and KafkaSender. Change-Id: Ie168028c4427741254b8c2fe316b82cca72d7668 Issue-ID: DCAEGEN2-1047 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-18Add metrics for active connections countJakub Dudycz8-77/+177
* Fix and refactor gauges tests in MicrometerMetricsTests as they were not executing * Fix client disconnection handler in NettyTcpServer * Add metrics gauge and counters required to measure active connections Change-Id: I5620d398525c6859679cd5a49dc55a9fefd8b592 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1041
2018-12-18Metric: Message latencyPiotr Jaszczyk5-29/+167
Defined as a difference between now and vesHeader.lastEpochTime. Change-Id: I4aa97e8efc13cb0039fde38b4fd2aa6411c7b89a Issue-ID: DCAEGEN2-1036 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-18Add metric for rejected clients countFilip Krzywka8-40/+155
- renamed few counters to be more verbose about what they count - removed not needed 'total' suffix in metrics name Change-Id: I6be0201e5f39f1298706c536b12410413d49df19 Issue-ID: DCAEGEN2-1043 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-17Metric: Processing timePiotr Jaszczyk20-74/+258
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-17Merge "Add metrics for dropped messages"Piotr Jaszczyk12-99/+269
2018-12-17Add metrics for dropped messagesJakub Dudycz12-99/+269
Add counters for messages dropped due to validation or undefined routing Slight refactoring Change-Id: Ibe4e38445e81babc745d7a7d95356910845293ce Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-1037
2018-12-14Merge "Use SHA-256 for detecting changes in Consul config"Piotr Wielebski1-7/+11
2018-12-14Create component tests skeleton for metricsFilip Krzywka5-22/+157
Change-Id: I5acc919171953a4bb428585a7b8420b3223aa556 Issue-ID: DCAEGEN2-1032 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-14Use SHA-256 for detecting changes in Consul configPiotr Jaszczyk1-7/+11
String.hashCode is probably not strong enough and was not designed to be used in that way. Change-Id: Iecb75dcdc742d1673b81cbaa213cff69297ff6f4 Issue-ID: DCAEGEN2-1034 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-14Merge "Add all required and reasonable MDCs"Piotr Wielebski19-91/+459
2018-12-14Merge "Expose Prometheus metrics"Piotr Wielebski11-97/+204
2018-12-14Merge "Allow to specify JVM options by means of env-var"Piotr Wielebski3-3/+8
2018-12-14Add all required and reasonable MDCsPiotr Jaszczyk19-91/+459
Change-Id: I34beb32a7c53da97c6945ec8d0022ac37059b7c5 Issue-ID: DCAEGEN2-670 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-14Merge "Don't escape in component tests"Piotr Jaszczyk2-2/+14
2018-12-13Expose Prometheus metricsPiotr Jaszczyk11-97/+204
Expose both JVM and HV-VES metrics by means of HealthCheckApiServer in Prometheus format. Change-Id: I81b74cd945c67569703a4a74f5a2683ede18d64a Issue-ID: DCAEGEN2-1029 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-13Merge "Log details about header validation failure"Piotr Jaszczyk4-50/+197
2018-12-13Log details about header validation failureIzabela Zawadzka4-50/+197
Change-Id: I836dcbee47bc2c2bfecc9486f6f8344a5bd8cd65 Signed-off-by: Izabela Zawadzka <izabela.zawadzka@nokia.com> Issue-ID: DCAEGEN2-1019
2018-12-13Don't escape in component testsFilip Krzywka2-2/+14
We want our test output to be readable, so we should not escape \n or \t in console output. Change-Id: I4c673760ea0cd55007b47b7490036c0693887eda Issue-ID: DCAEGEN2-1026 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-13Merge "Align logback configuration"Piotr Jaszczyk9-214/+371
2018-12-13Align logback configurationFilip Krzywka9-214/+371
- 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-13Merge "Add of adapter fun with param ClientContext"Piotr Jaszczyk9-28/+61
2018-12-13Add of adapter fun with param ClientContextkjaniak9-28/+61
Change-Id: Ib9ac6ab16c51ddf40ae849f4ce04ab7e25609f56 Issue-ID: DCAEGEN2-1031 Signed-off-by: kjaniak <kornel.janiak@nokia.com>
2018-12-13Allow to specify JVM options by means of env-varPiotr Jaszczyk3-3/+8
Change-Id: I042e022d650a07804096b397c31abc82a9633089 Issue-ID: DCAEGEN2-1025 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-12Add helper scriptsFilip Krzywka11-0/+458
Change-Id: I8d5b48511e1b7f9cb7d1f65e8605ebe4cf1b17fc Issue-ID: DCAEGEN2-1027 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-10Add Markers logsFilip Krzywka6-7/+85
Change-Id: I5d3c9e1e4659782719e4847c5bcedbca39c173a0 Issue-ID: DCAEGEN2-669 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-12-10Add log diagnostic contextPiotr Jaszczyk37-328/+469
As it's not trivial to use MDC directly from logging framework in reactive application, we need to do some work manually. The approach proposed is an explicit MDC handling, which means that context is kept as an object created after establishing client connection. Next, new instance of HvVesCollector (and its dependencies) is created. Every object is propagated with ClientContext so it can use it when calling logger methods. In the future ClientContext might be used to support other use-cases, ie. per-topic access control. As a by-product I had to refactor our Logger wrapper, too. It already had too many functions and after adding MDC number would be doubled. Change-Id: I9c5d3f5e1d1be1db66d28d292eb0e1c38d8d0ffe Issue-ID: DCAEGEN2-671 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-12-06Update INFO.yamlJessica Wagantall1-3/+16
Add Piotr Jaszczyk and Piotr Wielebski Remove Przemyslaw Wasala Change-Id: I2b8fae7a3f3423dd9877e38d3ddc765d6b343291 Issue-ID: CIMAN-33 Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
2018-12-05Enhance of logging in test partkjaniak15-47/+164
Change-Id: Ibdec0ac5cead7e46ada4c32983b9ccf962df703b Issue-ID: DCAEGEN2-1004 Signed-off-by: kjaniak <kornel.janiak@nokia.com>
2018-12-04Harmonize logging and add new logsFilip Krzywka22-84/+398
- 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 Jaszczyk168-133/+600
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>
2018-11-28Bump checkstyle versionFilip Krzywka27-65/+41
- changed plugin invocation due to backwards incompatible changes made in detekt's RC9 version - disabled few rules that we actually don't follow in our code and we seem to be fine with it - turned on UnusedPrivateMember as it actually is a code smell/debt - supressed warnings in where it was plausible (according to common sense) - fixed warnings wherever possible Change-Id: I7be97f471ff46786ef1fca3432b759e7820ac681 Issue-ID: DCAEGEN2-996 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-27Merge "Remove Consul configuration decoding"Vijay Venkatesh Kumar2-43/+16
2018-11-27Merge "Fix tagging for CSITs"Vijay Venkatesh Kumar1-1/+2
2018-11-27Merge "Add healthcheck script"Vijay Venkatesh Kumar2-0/+5
2018-11-22Fix tagging for CSITsFilip Krzywka1-1/+2
- latest tag should not be used to prevent confusion with casablanca, instead 1.1-SNAPSHOT should when referring to latests (Dublin) build - this allows for less frequent changes in CSIT repository after code freeze (when changes need to update service version) Change-Id: I4c94a5a2e90d0c77d51110ed97c9e28c30130f10 Issue-ID: DCAEGEN2-983 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-22Remove Consul configuration decodingFilip Krzywka2-43/+16
Change-Id: I36a6aea55507abfb61613806c93257b049d6eea4 Issue-ID: DCAEGEN2-827 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-22Add healthcheck scriptFilip Krzywka2-0/+5
To be used in HV-VES deployment template Change-Id: I87e1d52db2bb530e131837052f55a29adb5d524b Issue-ID: DCAEGEN2-794 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-21Fix xNF simulator sslContextFilip Krzywka1-6/+7
If --ssl-disable flag is specified in command line arguments, we shouldn't put sslContext into TcpClient as this results in IllegalArgument. Change-Id: I2e2d2ea89736f1e372e1b408c8f3cbe50bf1ecea Issue-ID: DCAEGEN2-985 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-20Update proto file to v14Jakub Dudycz3-15/+29
- update proto file - update vesEventListenerVersion validation regex to match new requirements Change-Id: Ic0bd855fd03caa3ca3120b2c49d5fa4f53de2540 Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-984
2018-11-19Merge "Fix Common Event Header fields validation"Przemyslaw Wasala4-8/+27
2018-11-19Fix Common Event Header fields validationJakub Dudycz4-8/+27
- "sequence" is no longer a required parameter, since deafult value "0" is acceptable - "vesEventListenerVersion" has to match the regular expression "7\.[0-9]+\.[0-9]+" Signed-off-by: Jakub Dudycz <jakub.dudycz@nokia.com> Issue-ID: DCAEGEN2-976 Change-Id: I2f9fd6f375ccca3255cc9e035918dc37cc97bd6a
2018-11-15Update project and dependenciesPiotr Jaszczyk35-359/+280
* Changed version from 4.0.0-SNAPSHOT to 1.1.0-SNAPSHOT as per Vijay suggestion * Updated Reactor to BOM Californium-SR2 * Updated mockito-kotlin to 2.0.0 * Introduced some fixes to support OpenJDK 11 compilation Change-Id: Ib25979ef50c7241a019bf98efd9759e0b8792d58 Issue-ID: DCAEGEN2-961 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
2018-11-13Handle stream error earlyFilip Krzywka5-10/+37
Should fix inconsistent logging due to Reactor Signal sometimes propagating from WireChunkDecoder stream to VesHvCollector stream as Signal.CANCEL instead of Signal.ERROR and thus not being handled correctly. As a drawback however we will log error twice in case it comes from WireChunkDecoder as we want to terminate connection in such case and so we need to propagate error. In WireChunkDecoder `doOnTerminate` was changed to `doFinally` as this method handles also cancellation signals and not only terminal signals. Also fixed minor checkstyle reported issues. Change-Id: I6e91d96c5a1a3ecf30603db9a71e032c770d507f Issue-ID: DCAEGEN2-955 Signed-off-by: Filip Krzywka <filip.krzywka@nokia.com>
2018-11-09Merge "Switch to JRE 11 in Dockerfiles"Przemyslaw Wasala4-19/+6