--=-gSEtEeMGkJ1xGAZMyNaJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2006-02-28 at 11:59 -0600, Ethan Galstad wrote:
> A common request in the past has been to add a new field to host and=20
> service definitions that overrides the host_name/service_description=20
> fields for display purposes in the web interface.
>=20
> I am considering adding a 'display_name' (or similiarly named)=20
> variable to host and service definitions to allow for this in Nagios=20
> 3.x. This would also allow you to change the "name" of the=20
> host/service that is viewable for customers/staff, while leaving the=20
> underlying host_name/service_description the same for reporting=20
> purposes.
>=20
> Of course, corresponding $HOSTDISPLAYNAME$ and $SERVICEDISPLAYNAME$=20
> macros will be added as well, to allow you to use the new names in=20
> notification scripts, etc.
>=20
> What are the general thoughts on this? Is there a better name than=20
> 'display name' that should be used?
'Display Name' seems appropriate.
I would prefer it be an optional tag (then, defaulting to the host_name
if missing).
On a somewhat related note:
Any chance "Alias" can be renamed to "Description" (or "Desc")?
For me, at least, getting Infrastructure to submit enough information to
make a valid host entry is a hassle, as the "Alias" concept consistently
eludes them.
--=-gSEtEeMGkJ1xGAZMyNaJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
iD8DBQBEBJNj2Lh5h/NRnWwRAozOAJ9NQaKtQ1xSBOkjLvXEA2hjkLOG4QCghpO9
9k7iiPgXXsYWE7zg8upZZT8=
=LF8F
-----END PGP SIGNATURE-----
--=-gSEtEeMGkJ1xGAZMyNaJ--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]