|
|
| Author |
Message |
spoofiz
Joined: 28 Feb 2006 Posts: 39 Location: Koeln - D
|
Posted: Tue Dec 05, 2006 11:53 am Post subject: |host_description| as input field |
|
|
Hi,
I've made a data input method with a shell script using an input parameter.
It works fine however every times i create a graph that refered to this script I have to put manually a custom data (the input parameter).
Actually the host description could be this input parameter but putting |host_description| in the "Input Fields" doesn't seem to work.
What could I do to automatically put the host_description value for the input parameter of my script ?
Do i have to use a script query for that ?
Thanks for answer. |
|
| Back to top |
|
 |
rony Developer/Forum Admin
Joined: 17 Nov 2003 Posts: 5453 Location: Wisconsin, USA
|
Posted: Tue Dec 05, 2006 11:55 am Post subject: |
|
|
Moved to General.
Try |hostname| instead of host description. |
|
| Back to top |
|
 |
spoofiz
Joined: 28 Feb 2006 Posts: 39 Location: Koeln - D
|
Posted: Wed Dec 06, 2006 5:30 am Post subject: |
|
|
Thanks, I did what you said (replaced host_description by hostname in the Special Type Code field), and the "hostname" is automatically specified as input parameter.
However, it would be easier for me to get the hostname_description as I specify the hostname and something else that i both need as input parameter in the host description field.
I read the "Special Type Code part" where it is mentionned that only valid keywords in a list are allowed but why is host_description not in this list ? |
|
| Back to top |
|
 |
gandalf Developer
Joined: 02 Dec 2004 Posts: 12295 Location: Muenster, Germany
|
Posted: Wed Dec 06, 2006 2:58 pm Post subject: |
|
|
| spoofiz wrote: | | I read the "Special Type Code part" where it is mentionned that only valid keywords in a list are allowed but why is host_description not in this list ? | IMHO, because the description is in general not of great use as an input parm to scripts. So, no code has been created for such a "cacti builtin variable"
Reinhard |
|
| Back to top |
|
 |
spoofiz
Joined: 28 Feb 2006 Posts: 39 Location: Koeln - D
|
Posted: Thu Dec 07, 2006 3:48 am Post subject: |
|
|
| Quote: | | the description is in general not of great use as an input parm to scripts |
That makes sense ... anyway using hostname value finally works for me.
Thanks again. |
|
| Back to top |
|
 |
appodictic
Joined: 10 Jul 2008 Posts: 3
|
Posted: Tue Aug 26, 2008 1:08 pm Post subject: It would actually be helpful |
|
|
| In my deployment hostnames are long FQDN. But I kept the description short. In my aggregate graphs |host_name| is too big and causes the legends to wrap around. while my host_description is very short. Unless it is hard to do having it an an input parameter could be useful. To some. Like me who made a choice and 400 hosts later kick myself. |
|
| Back to top |
|
 |
gandalf Developer
Joined: 02 Dec 2004 Posts: 12295 Location: Muenster, Germany
|
Posted: Fri Aug 29, 2008 2:27 pm Post subject: |
|
|
To me, that sounds more like an AGGREGATE plugin feature that's missing. I was already thinking about making the "prefix" selectable ...
Reinhard |
|
| Back to top |
|
 |
|