IN PROGRESS:
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 openshit logs.
* 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 installed 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 the required here to log the device info is already implemented and done for any client application with the SDK which is indeed a pre-requirement to use the mobile-service in order to call the /init. In this way, shows that nothing need to be done in this regards.
2. Check if is a requirement log the endpoint calls to the mobile security service. If yes, show that what is required just to add the listener in the future mobile-security-service-apb as it is done [here|https://github.com/aerogearcatalog/keycloak-apb/blob/2c3496cfbd90736039727b23fcab5d9964c29572/roles/provision-keycloak-apb/templates/keycloak_realm.json.j2#L8]
|
|
