[ 
https://issues.apache.org/jira/browse/TC-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Durfey updated TC-299:
---------------------------
         Labels: change_log logs status  (was: )
    Description: 
Opened on bugs scrub, based on 
https://github.com/Comcast/traffic_control/issues/620

smalenfant:
Sometimes I've got a hard time following what Ops is doing. Having a better 
understanding from the Change log would help a long way... I can't tell what 
happened here without knowing that "6" is OFFLINE. We should be expand this 
easily.

Would also be nice to see the "From Status" to "To Status".

2015-09-15 12:27:04 UICHANGE    Update server edge04 status->6 user 
2015-09-15 12:26:52 UICHANGE    Update server edge03 status->6 user 
2015-09-15 12:26:41 UICHANGE    Update server edge02 status->6 user 
2015-09-15 12:26:28 UICHANGE    Update server edge01 status->6 user


Sometime we see the following.. probably different code path.

2015-09-18 13:20:23 UICHANGE    Update server edge04.kabletown.net new status = 
REPORTED user   
2015-09-18 13:20:18 UICHANGE    Update server edge02.kabletown.nett new status 
= REPORTED user


dewrich:
If you can make a list of all of the Change Log tweaks you'd like to see like 
this, I will put it in the backlog to enhance them.

  was:

Opened on bugs scrub, based on 
https://github.com/Comcast/traffic_control/issues/620

smalenfant:
Sometimes I've got a hard time following what Ops is doing. Having a better 
understanding from the Change log would help a long way... I can't tell what 
happened here without knowing that "6" is OFFLINE. We should be expand this 
easily.

Would also be nice to see the "From Status" to "To Status".

2015-09-15 12:27:04 UICHANGE    Update server edge04 status->6 user 
2015-09-15 12:26:52 UICHANGE    Update server edge03 status->6 user 
2015-09-15 12:26:41 UICHANGE    Update server edge02 status->6 user 
2015-09-15 12:26:28 UICHANGE    Update server edge01 status->6 user


Sometime we see the following.. probably different code path.

2015-09-18 13:20:23 UICHANGE    Update server edge04.kabletown.net new status = 
REPORTED user   
2015-09-18 13:20:18 UICHANGE    Update server edge02.kabletown.nett new status 
= REPORTED user


dewrich:
If you can make a list of all of the Change Log tweaks you'd like to see like 
this, I will put it in the backlog to enhance them.

        Summary: Change Log. Expand status to human readable string  (was: TO 
Change Log. Expand status to human readable string)

> Change Log. Expand status to human readable string
> --------------------------------------------------
>
>                 Key: TC-299
>                 URL: https://issues.apache.org/jira/browse/TC-299
>             Project: Traffic Control
>          Issue Type: Improvement
>          Components: Traffic Ops
>            Reporter: Nir Sopher
>              Labels: change_log, logs, status
>
> Opened on bugs scrub, based on 
> https://github.com/Comcast/traffic_control/issues/620
> smalenfant:
> Sometimes I've got a hard time following what Ops is doing. Having a better 
> understanding from the Change log would help a long way... I can't tell what 
> happened here without knowing that "6" is OFFLINE. We should be expand this 
> easily.
> Would also be nice to see the "From Status" to "To Status".
> 2015-09-15 12:27:04 UICHANGE    Update server edge04 status->6 user 
> 2015-09-15 12:26:52 UICHANGE    Update server edge03 status->6 user 
> 2015-09-15 12:26:41 UICHANGE    Update server edge02 status->6 user 
> 2015-09-15 12:26:28 UICHANGE    Update server edge01 status->6 user
> Sometime we see the following.. probably different code path.
> 2015-09-18 13:20:23 UICHANGE    Update server edge04.kabletown.net new status 
> = REPORTED user   
> 2015-09-18 13:20:18 UICHANGE    Update server edge02.kabletown.nett new 
> status = REPORTED user
> dewrich:
> If you can make a list of all of the Change Log tweaks you'd like to see like 
> this, I will put it in the backlog to enhance them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to