Hey all,
So I believe this is a simpler problem, however, I'm struggling to fix it even after reading through the man pages.
Lets take an example host from my hosts.cfg file, call it "myhost.site.secure". When I look at my Xymon webpage, I want to the header "testhost" instead of "myhost.site.secure" at the front of the system line. I can get the name to appear correctly, but when I do, all of my tests stop producing data. Here are the options I've tried:
NAME:testhost myhost.site.secure CLIENT:testhost myhost.site.secure testhost:myhost.site.secure testhost myhost.site.secure
All of them run into the same problem of data no longer showing up. Anyone have any idea why this is happening?
Also, as a side question: If I were to add the same host three times under 3 different aliases, with all the network tests disabled, would that cause any issues within Xymon?
Cheers all, Joshua
On Tue, 19 Jul 2016, 07:22 Joshua Hunt <joshuasocrates at gmail.com> wrote:
Hey all,
So I believe this is a simpler problem, however, I'm struggling to fix it even after reading through the man pages.
Lets take an example host from my hosts.cfg file, call it "myhost.site.secure". When I look at my Xymon webpage, I want to the header "testhost" instead of "myhost.site.secure" at the front of the system line. I can get the name to appear correctly, but when I do, all of my tests stop producing data. Here are the options I've tried:
NAME:testhost myhost.site.secure CLIENT:testhost myhost.site.secure testhost:myhost.site.secure testhost myhost.site.secure
All of them run into the same problem of data no longer showing up. Anyone have any idea why this is happening?
Try something like:
10.1.2.3 testhost # CLIENT:my host.site.secure
Also, as a side question: If I were to add the same host three times under
3 different aliases, with all the network tests disabled, would that cause any issues within Xymon?
I don't think so.
J
Try something like:
10.1.2.3 testhost # CLIENT:my host.site.secure
Don’t do that. That means the server will look for a client reporting in with that name instead of testhost. That’s not what you want as that will affect alerting, analysis, etc. You want to use the name tag as another post has pointed out.
Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: 734-384-6403 | | Mobile: 7349151444 | Email: Scot.Kreienkamp at la-z-boy.com Also, as a side question: If I were to add the same host three times under 3 different aliases, with all the network tests disabled, would that cause any issues within Xymon?
I don't think so.
The only consequence is Xymon will complain about multiple hosts entries. On the duplicates you need to put noconn or put prefer on one of the lines so it knows which of the duplicate lines to prefer for test configuration.
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
Excellent! I would like to mention that I do have the IP address included in all my hosts, I just left it out while typing up my question. I reformatted to put the alias after the pound sign instead of before, and now it works.
As for the multiple hosts, I am planning on disabling all normally enabled network tests. I do not need them for the monitoring I'm doing.
Thank you everyone for your help!
Joshua
On Mon, Jul 18, 2016 at 2:43 PM, Scot Kreienkamp < Scot.Kreienkamp at la-z-boy.com> wrote:
Try something like:
10.1.2.3 testhost # CLIENT:my host.site.secure
Don’t do that. That means the server will look for a client reporting in with that name instead of testhost. That’s not what you want as that will affect alerting, analysis, etc. You want to use the name tag as another post has pointed out.
*Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate* One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: 734-384-6403 | | Mobile: 7349151444 | Email: Scot.Kreienkamp at la-z-boy.com
Also, as a side question: If I were to add the same host three times under 3 different aliases, with all the network tests disabled, would that cause any issues within Xymon?
I don't think so.
The only consequence is Xymon will complain about multiple hosts entries. On the duplicates you need to put noconn or put prefer on one of the lines so it knows which of the duplicate lines to prefer for test configuration.
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
On 7/18/2016 1:43 PM, Scot Kreienkamp wrote:
Try something like:
10.1.2.3 testhost # CLIENT:my host.site.secure
Don’t do that. That means the server will look for a client reporting in with that name instead of testhost.
Ermmm. Not exactly.
Take this example line from hosts.cfg:
0.0.0.0 foo.com # CLIENT:foo NAME:bar
The host will be displayed (on the web page) on a line leading with the name "bar" rather than the expected "foo.com". Messages from clients "foo.com" OR "foo" will be matched to this host and displayed on its line.
CLIENT does not define an "instead of" relationship, rather an "in addition to" relationship.
Our most common use for this tag is the retirement of an old application. The old server was named "foo", but the new server is named something else. There may have been application-specific tests performed and reported to Xymon under the client name "foo". Rather than hunt down all the old scripts, 'tis simpler to just say "If you get a message for "foo", please include its results here."
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska
On 7/18/2016 1:21 PM, Joshua Hunt wrote:
Lets take an example host from my hosts.cfg file, call it "myhost.site.secure". When I look at my Xymon webpage, I want to the header "testhost" instead of "myhost.site.secure" at the front of the system line. I can get the name to appear correctly, but when I do, all of my tests stop producing data.
I would use a line that looked like:
0.0.0.0 myhost.site.secure # NAME:testhost
I am assuming my client is reporting messages to "myhost.site.secure". The message-matching is done to the name in the second field. The "NAME" tag is used only when generating web-pages.
The "CLIENT" tag is used to match messages sent by a client under a name different from its hostname. It doesn't affect the way the host is displayed on the web page.
Here are the options I've tried:
NAME:testhost myhost.site.secure
If you tried to put a line in the hosts.cfg with that format, I would not expect it to work. The "NAME" tag goes _after_ the hash.
From the hosts.cfg man file:
The format of an entry in the hosts.cfg file is as follows: IP-address hostname # tag1 tag2 ...
I use zeros for my IP-address because I assume myhost.site.secure is resolvable by DNS. If it isn't, you will need to provide the correct address and include the tag "TESTIP"
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska
participants (4)
-
jlaidman＠rebel-it.com.au
-
john.thurston＠alaska.gov
-
joshuasocrates＠gmail.com
-
Scot.Kreienkamp＠la-z-boy.com