h4. What is it?
* OpenShift - Logging & Metrics - (Elasticsearch + Fluentd + Kibana)
* https://www.youtube.com/watch?v=RMDX3YC0CSQ
* https://docs.openshift.com/container-platform/3.11/install_config/aggregate_logging.html
h4. Aerogear Metrics
Shows that the Aerogear Metrics is the aerogear component/service which will create data for the openshift logs and what should be used here.
* https://docs.aerogear.org/aerogear/latest/mobile-metrics.html#setting-up-mobile-metrics-service-sdk
h4. How to log the device info when the /init is called?
* Shows that any client app which is using the SDK has the aerogear metrics already on it.
* Shows that the required info will already be tracked by default. See [here|https://github.com/aerogear/aerogear-app-metrics/blob/c37fb04460868d64a5b6a1ab22860b1b55b848d4/pkg/mobile/metrics_test.go#L32] and [here|https://github.com/aerogear/aerogear-android-sdk/blob/72995e37ac674c35f26f387c0ffbe5109c4af260/security/src/test/java/org/aerogear/mobile/security/metrics/DeviceCheckResultMetricTest.java#L21]
h5. Questions that need to be raised:
1. Confirm our understand over it. Shows that one of the requirement tracked here requirements is to log the device info via EFK. In this way, could you confirm that it means to use the aerogear-metrics to do it? Also, shows that by default it is already implemented and done /implemented for any client application with the SDK device which is indeed a pre-requirement to use using the mobile-security-service in order to call the /init SDK, see here[1][2][3] . In this way So , shows appears that nothing this need to be done to attend it is already attended without any further implementation . Could you please help us by confirming this understanding?
PS.: [technical confirmation with Aerogear team]
2. Should the mobile-security-service use the aerogear-metrics to log/track all events and info etc as it is done for aerogear-keycloak? If yes, what is the best way to do it? Should we create a an mobile-security-service-metrics-spi like as it was done for [ keycloak |https://github.com/aerogear/keycloak-metrics-spi [4 ] and add rules to deploy it with the future mobile-security-service in the catalogue as it is -apb project similar to what was done in the [ keycloak-apb | [5]?
[1] - https:// docs.aerogear.org/aerogear/latest/mobile-metrics.html#setting-up-mobile-metrics-service-sdk
[2] - https:// github.com/ aerogear/aerogear-app-metrics/blob/c37fb04460868d64a5b6a1ab22860b1b55b848d4/pkg/mobile/metrics_test.go#L32
[3] - https://github.com/aerogear/aerogear-android-sdk/blob/72995e37ac674c35f26f387c0ffbe5109c4af260/security/src/test/java/org/aerogear/mobile/security/metrics/DeviceCheckResultMetricTest.java#L21
[4] - https://github.com/aerogear/keycloak-metrics-spi
[5] - https://github.com/ aerogearcatalog/keycloak-apb/search?q=metrics&unscoped_q=metrics ]?
PS.: [business requirements confirmation] and [technical confirmation with Aerogear team]
|
|
