can you use patterns in EXHOST ?
list Bakkies Gatvol
In analysis.cfg I have a CLASS=linux section that works fine. Fine for *our* hosts - the ones we built. Now I have to monitor a whole datacenter of other linux boxes that do not adhere to *our* standards. I added the new linux boxes into Xymon with longname ( host.yyy.xxx ) - my hosts are all shortname. Please tell me how I can exclude every linux host ending in yyy.xxx from CLASS=linux. It is not really practical to list 150 hosts by LONGname in EXHOST. Fingers crossed that this is possible! Bakkies
list Bakkies Gatvol
This seems to be working now. CLASS=linux EXHOST=%(a*.yyy.xxx) this did not work EXHOST=%a*.yyy.xxx ... do you need more () when you're using a * ? I hope EXHOST=%(*.yyy.xxx) works as well because that's what I really need! If anyone has a good set of RE pattern examples for HOST and EXHOST - or can point me too some - I would be VERY grateful. I have not quite got the hang of it. B
▸
From: Xymon <xymon-bounces at xymon.com> on behalf of Bakkies Gatvol <user-66e2e196cd54@xymon.invalid>
Sent: Wednesday, December 6, 2017 6:28 PM
To: Xymon Mailing List
Subject: [Xymon] can you use patterns in EXHOST ?
In analysis.cfg
I have a CLASS=linux section that works fine. Fine for *our* hosts - the ones we built.
Now I have to monitor a whole datacenter of other linux boxes that do not adhere to *our* standards.
I added the new linux boxes into Xymon with longname ( host.yyy.xxx ) - my hosts are all shortname. Please tell me how I can exclude every linux host ending in yyy.xxx from CLASS=linux.
It is not really practical to list 150 hosts by LONGname in EXHOST.
Fingers crossed that this is possible!
Bakkies
list Bakkies Gatvol
It dawned on me there are regex tools online! https://regexr.com/ [https://regexr.com/assets/card.png]<https://regexr.com/>; RegExr: Learn, Build, & Test RegEx<https://regexr.com/>; regexr.com Regular expression tester with syntax highlighting, PHP / PCRE & JS Support, contextual help, cheat sheet, reference, and searchable community patterns. I used above (on PCRE) and came up with this CLASS=linux EXHOST=%((a|u)*.yyy.xxx) that seems to be performing as required I even went back to another grouping and it looks like this is working - using a regexp in HOST and then using the same in EXHOST HOST=%(as(cop|tpt)hpux[0-9][0-9]) CLASS=hp-ux EXHOST=%(as(cop|tpt)hpux[0-9][0-9])
![https://regexr.com/assets/card.png]<https://regexr.com/>](https://regexr.com/assets/card.png]<https://regexr.com/>){kind=link}
▸
From: Xymon <xymon-bounces at xymon.com> on behalf of Bakkies Gatvol <user-66e2e196cd54@xymon.invalid>
Sent: Wednesday, December 6, 2017 7:31 PM
To: Xymon Mailing List
Subject: Re: [Xymon] can you use patterns in EXHOST ?
This seems to be working now.
CLASS=linux EXHOST=%(a*.yyy.xxx)
this did not work EXHOST=%a*.yyy.xxx ... do you need more () when you're using a * ?
I hope EXHOST=%(*.yyy.xxx) works as well because that's what I really need!
If anyone has a good set of RE pattern examples for HOST and EXHOST - or can point me too some - I would be VERY grateful. I have not quite got the hang of it.
B
From: Xymon <xymon-bounces at xymon.com> on behalf of Bakkies Gatvol <user-66e2e196cd54@xymon.invalid>
Sent: Wednesday, December 6, 2017 6:28 PM
To: Xymon Mailing List
Subject: [Xymon] can you use patterns in EXHOST ?
In analysis.cfg
I have a CLASS=linux section that works fine. Fine for *our* hosts - the ones we built.
Now I have to monitor a whole datacenter of other linux boxes that do not adhere to *our* standards.
I added the new linux boxes into Xymon with longname ( host.yyy.xxx ) - my hosts are all shortname. Please tell me how I can exclude every linux host ending in yyy.xxx from CLASS=linux.
It is not really practical to list 150 hosts by LONGname in EXHOST.
Fingers crossed that this is possible!
Bakkies
list Ian Diddams
we have a xymon 4.2.3 server running on centos 5 (X1) I am charged with migrating that toi a new centos 7 server. So I now have a xymon 4.3.28 server running on centos 7 (X2) So... how do i go about copying WHAT from X1 to X2, and how do I get around the "gotcha" that is the changes from 4.2 to 4.3. I see that there is an "upgrade" script, and a list of manual stuff as alternative actions... but they both rather assume you are staying on the same server to upgrade only xymon ie everything is in situ. It is not viable to upgrade on the existing server as its a live production environment nor is it viable to install 4.2/3 on the new server due to time constraints. I short I need to know how to efficiently migrate the 4.2.3 files and data and history etc from X1 to X2. Apologies of this is a FAQ! Ian
list Richard L. Hamilton
I would think that if you didn't already have xymon on the new server, it'd just be a matter of making a tarball of the xymon home directory including data and configuration files, copying it to the new system, extracting it in the appropriate place, and making the manual changes. But with both already running, it's not an upgrade, it's a merge. And I don't know that there are really tools for that, _unless_ no client appears in both, in which case I'd think it would be straightforward enough.
▸
On Dec 7, 2017, at 10:52, Ian Diddams via Xymon <xymon at xymon.com> wrote: From: Ian Diddams <user-7fbf34ed5219@xymon.invalid> Subject: migrating xymon Date: December 7, 2017 at 10:52:57 EST To: Xymon Mailing List <xymon at xymon.com> we have a xymon 4.2.3 server running on centos 5 (X1) I am charged with migrating that toi a new centos 7 server. So I now have a xymon 4.3.28 server running on centos 7 (X2) So... how do i go about copying WHAT from X1 to X2, and how do I get around the "gotcha" that is the changes from 4.2 to 4.3. I see that there is an "upgrade" script, and a list of manual stuff as alternative actions... but they both rather assume you are staying on the same server to upgrade only xymon ie everything is in situ. It is not viable to upgrade on the existing server as its a live production environment nor is it viable to install 4.2/3 on the new server due to time constraints. I short I need to know how to efficiently migrate the 4.2.3 files and data and history etc from X1 to X2. Apologies of this is a FAQ! Ian
list Ian Diddams
Cheers Richard, so in the case of new version running on X2, ie a merge what files/directories need copying from X1? anybody able to enlighten me? ian
▸
On Thursday, 7 December 2017, 19:56:00 GMT, Richard L. Hamilton <user-af55987f6d56@xymon.invalid> wrote:
I would think that if you didn't already have xymon on the new server, it'd just be a matter of making a tarball of the xymon home directory including data and configuration files, copying it to the new system, extracting it in the appropriate place, and making the manual changes.
But with both already running, it's not an upgrade, it's a merge. And I don't know that there are really tools for that, _unless_ no client appears in both, in which case I'd think it would be straightforward enough.
On Dec 7, 2017, at 10:52, Ian Diddams via Xymon <xymon at xymon.com> wrote:
From: Ian Diddams <user-7fbf34ed5219@xymon.invalid>
Subject: migrating xymon
Date: December 7, 2017 at 10:52:57 EST
To: Xymon Mailing List <xymon at xymon.com>
we have a xymon 4.2.3 server running on centos 5 (X1)
I am charged with migrating that toi a new centos 7 server.
So I now have a xymon 4.3.28 server running on centos 7 (X2)
So... how do i go about copying WHAT from X1 to X2, and how do I get around the "gotcha" that is the changes from 4.2 to 4.3. I see that there is an "upgrade" script, and a list of manual stuff as alternative actions... but they both rather assume you are staying on the same server to upgrade only xymon ie everything is in situ.
It is not viable to upgrade on the existing server as its a live production environment nor is it viable to install 4.2/3 on the new server due to time constraints.
I short I need to know how to efficiently migrate the 4.2.3 files and data and history etc from X1 to X2.
Apologies of this is a FAQ!
Ian