[ZBXNEXT-2752] Add an option to redirect stderr errors to eventlog on Windows Created: 2015 Mar 19 Updated: 2015 Mar 23 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent (G) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Andris Zeila | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 0 |
Labels: | eventlog, logging, stderr | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Windows |
Description |
Until agent opens log file all critical errors are written into standard error output (stderr). When started as a service those messages are lost and debugging the error is quite problematic. The idea is to use eventlog for critical messages if agent has been started as a service. However detecting if agent has been started as a service is another problem.The simplest solution would be to add a command line parameter that would redirect to eventlog all error messaes originally written to stderr. When installing itself as service agent would automatically add this parameter to service launch parameters. |
Comments |
Comment by Andris Zeila [ 2015 Mar 23 ] |
(1) also the -m command line parameter should be accepted only when working with services (-i, -d, -s, -x options). |