On Sat, Apr 9, 2011 at 9:26 PM, Tony Graziano <[email protected]>wrote:
> Are these logs going to be visible from the admin UI? It's nice to capture > the details, But it would be handy to have them readily visible without > having to dig them out manually. > We plan to highlight failures in the admin UI, corresponding to each node (if any). In addition, if it helps we can put a link there also, that will open the audit log, pick all logs that corresponds to the selected node and display them. > Rendering the successes/failures in a readable table with the > date/timestamps seems desirable (to me anyway). > > Is it reasonable to assume this is not possible given the > desisg/accessibility of the logs? > Well, it is possible to read logs and display, I remember there is a page: call history that reads admin logins and display. Mircea > ===================== > Tony Graziano, Manager Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: Telephone: > 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: http://support.myitdepartment.net > > Blog: http://blog.myitdepartment.net > > Linked-In Profile: http://www.linkedin.com/pub/ tony-graziano/14/4a6/7a4 > On Apr 9, 2011 1:51 PM, "Mircea Carasel" <[email protected]> wrote: > > On Sat, Apr 9, 2011 at 5:43 PM, George Niculae <[email protected]> wrote: > > > >> On Sat, Apr 9, 2011 at 4:50 PM, Mircea Carasel <[email protected]> > wrote: > >> > > >> > > >> > On Fri, Apr 8, 2011 at 10:45 PM, Douglas Hubler <[email protected]> > >> wrote: > >> > > >> > I vote for keeping the details in files, because I think that the > admin > >> can > >> > look in the files quicker and easier in disaster situations, to find > any > >> > potential error and it doesn't matter if configuration server is up or > >> down. > >> > > >> > Sipxconfig will read details from files and display on the servers > page > >> as > >> > specified above. > >> > > >> > >> IMO we should keep replication details in the audit logs we already > >> writing and node states in db (this could include also enabled / > >> disabled) > >> > > I was looking in sipxconfig-audit.log and noticed that there are written > > only successful replications, failed replications are not reported. > > > > We can extend a bit and log also failures there. In addition we can > create > > some sort of parsing mechanism to parse the audit log file > > and present details for each node in servers page. Nodes state can stay > in > > db as it is now, as you suggest, > > > > Thanks, Mircea > > > >> > >> George > >> > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
