Project

General

Profile

Actions
Copy link

Improvement #10117

closed

Improvements for custom loggers

Added by Kavin Prathaban over 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
None
Assignee:
Kavin Prathaban
Start date:
05/06/2023
Due date:
% Done:

0%

Estimated time:
Device Type:
Component:
Type:

Description

Description

Create custom loggers for following cases

1. Enrollment history events
2. Device-to-server connectivity events
3. Policy payload change events
4. Operation execution events
5. App install events

Files

Screenshot from 2023-06-21 14-55-38.png (102 KB) Screenshot from 2023-06-21 14-55-38.png [1] Arshana Atapattu, 21/06/2023 09:31 AM
Actions
Copy link
 #1

Updated by Kavin Prathaban over 1 year ago

  • Status changed from New to Implementation

Expected timeline

Subtasks 05/06 06/06 07/06 08/06 09/06 12/06 13/06 14/06 15/06 16/06
Create custom logs * * *
Create kibana dashboards * * * * *
Testing * *
Actions
Copy link
 #3

Updated by Kavin Prathaban over 1 year ago

  • Status changed from Implementation to QA
Actions
Copy link
 #4

Updated by Kavin Prathaban over 1 year ago

  • Status changed from QA to Staged

Test Instructions:

  • Check for appinstall.log, policy.log, deviceconnectivity.log, deviceenrolment.log in {PACK}/repository/logs/
  • Check following use cases are producing logs in the pattern mentioned in PR.
  1. policylogs - policy create, policy update, policy delete, apply changes to device, policy priority change
  2. app install logs - public,enterprise,webapp install and uninstall
  3. device enrolment logs - device enrolment, disenrolment
  4. device connectivity logs - check for pending operation logs and by adding new operations
Actions
Copy link
 #5

Updated by Arshana Atapattu over 1 year ago

After a device enrolled and disenrolled logs are published, but when again that same device is enrolled the logs are not published.
have enrolled and disenrolled the same device 4 times (without resetting), but only the disenrolling logs are published [1].

Device: samsung galaxy A04
Agent: 4.005.00.03
Enrolled method: BYOD manual

[1]
[1]

Actions
Copy link
 #7

Updated by Viranga Gunarathna over 1 year ago

  • Status changed from Needs Improvement to QA
Actions
Copy link
 #8

Updated by Arshana Atapattu over 1 year ago

  • Status changed from QA to QA Reject

Still same device enroll logs are not shown.

[2023-06-27 16:35:15,530] INFO - [144] [android] [arshana] [BYOD] [-1234] [carbon.super] [arshana] - Device enrolled successfully
[2023-06-27 16:37:23,625] INFO - [144] [android] [arshana] [BYOD] [-1234] [carbon.super] [arshana] - Device disenrolled successfully
[2023-06-27 16:38:31,613] INFO - [144] [android] [arshana] [BYOD] [-1234] [carbon.super] [arshana] - Device disenrolled successfully
[2023-06-27 16:38:56,527] INFO - [144] [android] [arshana] [BYOD] [-1234] [carbon.super] [arshana] - Device disenrolled successfully

Actions
Copy link
 #9

Updated by Inosh Perara over 1 year ago

  • Project changed from product-uem 5.3.0 GA to 32
Actions
Copy link
 #10

Updated by Kavin Prathaban over 1 year ago

  • Due date deleted (16/06/2023)
  • Status changed from QA Reject to Needs Improvement

Create custom loggers for following cases

6. Group modification events / Device group assignment events
7. User modification events
8. Role modification events
9. User login events

Actions
Copy link
 #12

Updated by Arshana Atapattu over 1 year ago

  • Project changed from 32 to product-uem 6.0.0 GA
Actions
Copy link
 #14

Updated by Kavin Prathaban 11 months ago

  • Status changed from Needs Improvement to QA
Actions
Copy link
 #16

Updated by Thilina Sandaruwan 10 months ago

  • Status changed from QA to QA Accept

This is working

  • Tested cases

1.Group modification events / Device group assignment events
2.User modification events
3.Role modification events
4.User login events
5.Device enrolling and disenrolling logs not publishing issue

  • Identifed issues

1. WARN, ERROR logs published in the separate Roles and groups log files.

This is fixed with pr: https://repository.entgra.net/proprietary/product-uem/pulls/57

2. Users Tag Returns Null Values

This is fixed with ticket: https://roadmap.entgra.net/issues/10516

  • Test results
    Pattern correct, tag details correct of each test cases in both sub-tenant and super-tenant environments
  • Future Improvement

Since it is possible to assign roles during the group creation event, add a 'roles' tag for the group modifications event log pattern, including the role details related to that group.

Related ticket: https://roadmap.entgra.net/issues/10530

  • Additional Notes
    Because there is a problem with the UEM staging server environment. All these tests were done in a local environment with recent modifications.
Actions
Copy link
 #17

Updated by Thilina Sandaruwan 10 months ago

  • Status changed from QA Accept to Closed

Closing due to QA accept

Actions
Copy link

Also available in: Atom PDF