Nagios Support Forum

On Thu, 16 Jan 2003, Ethan Galstad wrote:

> On 17 Jan 2003 at 0:17, Subhendu Ghosh wrote:
>
> > On Fri, 17 Jan 2003, Federico Mennite wrote:
> >
> > > Subhendu Ghosh wrote:
> > >
> > > >On 15 Jan 2003, Karl DeBisschop wrote:
> > > >
> > > >
> > > >>Plugin internationalization would be wanted too, I would guess?
> > > >>
> > > >>
> > > >>
> > > Yes, unless it doesn't cause troubles to addons and misc. But it
> > > shouldn't be the case if the only parsed parts are performance stats.
> > >
> > > >Long term - yes (are there any issues - perf: disk i/o - or security with
> > > >passing possibly unicode strings through pipes)
> > > >
> > > I guess it could be made optional.
> > >
> > > >
> > > >Short term - move the "OK/WARN/CRIT/UNKWN" tags to be prepended to the
> > > >plugin output based on the i18n of return code.
> > > >
> > > >
> > > >
> > > I'm not sure to understand what you mean here. Could you please elaborate?
> > >
> >
> > Currently a number of the plugins output is written out as "OK: status"
> >
> > We could remove the OK - leave the status - and have the web interface
> > prepend the OK in i18n to the status before display.
> >
>
> Perhaps the OK/WARN/CRIT/UNKWN tags should be stripped altogether?
> Relying on the web interface to generate the tags is okay when using
> a web browser, but they'll be missing in the logs, notifications,
> etc.

Perhaps another mod to the logs to add field for a status code - not the
tag - allowing the web interface to i18n.

May be another macro that is available to the notification/perfdata for
status code..

--
-sg






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]