Guest

Preview Tool

Cisco Bug: CSCvu26233 - ENH - ECE Should Have Better Trace Level Configuration Process

Last Modified

Jun 03, 2020

Products (1)

  • Cisco Enterprise Chat and Email

Known Affected Releases

11.6(1) 12.0(1) 12.5(1)

Description (partial)

Symptom:
Setting trace levels is currently a very manual, painful process. ECE has separate log configuration settings per process and per server.  For example, in a 1500-Agent, HA deployment, this means that there are 10 ApplicationServer processes.  Each Services server has process logging set individually as well.  This creates two issues.

First changing the process logging levels requires the user to do the following steps.
       1. Find the process in the list and select it.
       2. Change the Maximum trace level using the drop-down in the general tab.
       3. Click the save button.
    In the event that the user wishes to change the trace level into one of the higher settings, there is an additional step of choosing the value in the Extensive logging duration field before clicking save.  There is the concept of Process Groups in the classic admin page, but this is an under documented feature and doesn't seem to work exactly right.  It's useful for changing the Maximum trace level for several processes at once, but even though it shows that it will generate a single log file, this is really only true for processes on the same physical server.  There's no way to have a common log file for all of the application servers for instance.

Second, it is not easy for a customer to see which services server is currently active when setting trace levels.  If the customer sets the trace level on the incorrect server or sets it on the currently active server but that server then fails over to the standby, the trace levels are lost as is potentially the ability to diagnose the issue.

Packaged CCE 12.x integrated ECE installs makes this worse as there is no way to create Process Groups in SPOG.

Conditions:
Enterprise Chat and Email
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.