Closed
Making Remote Logging Easier?
Trying to get our developers to avoid use of InfoForced for logging applications.
Following up on Compilation of Popular Pega OOTB Classes/Loggers that helps in Troubleshooting Issues
Are any of these in the plans by Pega or 3rd-party tool providers:
- Maybe it's possible to simply cache or otherwise display popular loggers?
- Change the dropdown to an AutoComplete?
- For logging activity rules, why not select from within the Developer Studio on a given ruleform?)
- For that matter, can we while we're logged (we did build a menu item for this in v6/v7 by calling an internal API)
- Can we have logging clients defined in prlogging.xml, to be re-enabled when server is started? (or otherwise start by first-use agent using above API)
- Ever turn on a logger on DEBUG and then leave it on?
- This is where adding process would be nice -- you could specify a fixed amount of time to start/stop a log level.
- When clicking "ResetAll", does this:
- reset all of the loggers do what were specified in prlogging.xml (I assume so...)
- Remove all logging clients (it appears like that happens as well?)