Dependency sytem in Hobbit
list Etienne Marganne
Hello all,
I am Etienne Marganne, a new comer in TI Automotive, a society which uses
Hobbit as a monitoring tool, I will be in charge of Hobbit tool. We would
like to enhance our monitoring tool in order to get more detailed
informations through it.
One of the first thing we would like to do is to create a dependency system
between monitored hosts across our network. For all the further discussion,
please keep in mind that we have a very large network and two Hobbit servers
where we would like to keep the same "hh-hosts" file.
The idea of the dependency system is the following one: once we have a host
that fails on a network path in our network all the hosts further that one
will be very likely unreachable. This will cause a lot of alerts to be
triggered because of one failure. This is not interesting because our team
will be flooded by those alerts. Therefore it could be useful to create
dependencies so that those further devices on the same path will not trigger
alerts (basically turning red).
There is a specific tag that can be used to do such a work, the "route" tag.
In our case with two Hobbit servers, we would tune that with the
"route_BBLOCATION" tag. Knowing that there are Hobbit clients on all the
network nodes between the two endpoints, the simplest idea would be to list
all the nodes in the description of those tags. This could work even if it
would generate of job. A little bit further here, let's say that one node
fails on a path, it is very probable that if you know that the following
nodes are unreachable, you may not want to test them anymore (to forbid them
to turn red).
Now think of a big network with a lot of redundancy, it is very probable
that there will be indeed a lot of network paths between a server and one
final host. If on one path one node fails, it does not mean that the final
client is not reachable. But with the "route" tag, that client would be
signal as unreachable since a member of the "route" has failed. This is not
comfortable at all.
What we would like to know, or to get, if there is a way to get this
dependency system work:
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| |
| --------- 5 ------------6 ----------- |
There are two paths to reach the Final Client, one composed by 1, 2, 3, 4
and another one composed by 5, 6.
With the current "route" tag we would have such a list of nodes:
route_HobbitServerA:1,2,3,4,5,6 then if 1 fails and the path 1-2-3-4 would
not work anymore but the 5-6 one would still.
A good dependency system would to have such a thing: Final Client depends on
4, 4 depends on 3, 3 depends on 2, 2 depends on 1 but Final Clients also
depends on 6 which depends on 5. More over this would also solve that kind
of topology :
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| | |
| --------- 5 ------------6 ----------- | Where
there is a link between 2 and 5, 2 and 6, 5 and 3, 6 and 3.
Maybe that something could be set up with the "depends" tag, however I do
not know how the informations will propagate through the different
dependencies done that tag.
Even further on the topic, the "route" tag performs only ping tests which
does not seem enough to me. I would like to add cpu, disks, ... tests to the
whole dependency system.
Thank you for your help and answers,
Regards,
Etienne Marganne
TI Automotive.
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
list Charles Goyard
Hi, try the bbcombotest to add HA logic and make the depend tag point to the aggregated dot. See bbcombotest.cfg -- Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31
list Greg L Hubbard
Etienne -- you are going to have to find someone to write that and add it to Hobbit. Path-based alarm suppression is one of the holy grails in the network management industry, and the reason it has not yet been solved is because it is a difficult problem. For small networks you can come up with a solution, but if you are using VLANs and WAN's and load balancers and all that other stuff it gets to be rather difficult. There are many commercial software vendors that claim to have this problem solved -- but sometimes even their demos do not work. The little bit of dependency specification that you can put into Hobbit does indeed work, but not across the board. GLH
▸
From: Marganne, Etienne [mailto:user-b63c96159c04@xymon.invalid]
Sent: Friday, January 19, 2007 5:58 AM
To: user-ae9b8668bcde@xymon.invalid
Cc: user-ce4a2c883f75@xymon.invalid
Subject: [hobbit] Dependency sytem in Hobbit
Hello all,
I am Etienne Marganne, a new comer in TI Automotive, a society
which uses Hobbit as a monitoring tool, I will be in charge of Hobbit
tool. We would like to enhance our monitoring tool in order to get more
detailed informations through it.
One of the first thing we would like to do is to create a
dependency system between monitored hosts across our network. For all
the further discussion, please keep in mind that we have a very large
network and two Hobbit servers where we would like to keep the same
"hh-hosts" file.
The idea of the dependency system is the following one: once we
have a host that fails on a network path in our network all the hosts
further that one will be very likely unreachable. This will cause a lot
of alerts to be triggered because of one failure. This is not
interesting because our team will be flooded by those alerts. Therefore
it could be useful to create dependencies so that those further devices
on the same path will not trigger alerts (basically turning red).
There is a specific tag that can be used to do such a work, the
"route" tag. In our case with two Hobbit servers, we would tune that
with the "route_BBLOCATION" tag. Knowing that there are Hobbit clients
on all the network nodes between the two endpoints, the simplest idea
would be to list all the nodes in the description of those tags. This
could work even if it would generate of job. A little bit further here,
let's say that one node fails on a path, it is very probable that if you
know that the following nodes are unreachable, you may not want to test
them anymore (to forbid them to turn red).
Now think of a big network with a lot of redundancy, it is very
probable that there will be indeed a lot of network paths between a
server and one final host. If on one path one node fails, it does not
mean that the final client is not reachable. But with the "route" tag,
that client would be signal as unreachable since a member of the "route"
has failed. This is not comfortable at all.
What we would like to know, or to get, if there is a way to get
this dependency system work:
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| |
| --------- 5 ------------6 ----------- |
There are two paths to reach the Final Client, one composed by
1, 2, 3, 4 and another one composed by 5, 6.
With the current "route" tag we would have such a list of nodes:
route_HobbitServerA:1,2,3,4,5,6 then if 1 fails and the path 1-2-3-4
would not work anymore but the 5-6 one would still.
A good dependency system would to have such a thing: Final
Client depends on 4, 4 depends on 3, 3 depends on 2, 2 depends on 1 but
Final Clients also depends on 6 which depends on 5. More over this would
also solve that kind of topology :
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| | |
| --------- 5 ------------6 ----------- |
Where there is a link between 2 and 5, 2 and 6, 5 and 3, 6 and 3.
Maybe that something could be set up with the "depends" tag,
however I do not know how the informations will propagate through the
different dependencies done that tag.
Even further on the topic, the "route" tag performs only ping
tests which does not seem enough to me. I would like to add cpu, disks,
... tests to the whole dependency system.
Thank you for your help and answers,
Regards,
Etienne Marganne
TI Automotive.
The information contained in this transmission may contain privileged
and confidential information. It is intended only for the use of the
person(s) named above. If you are not the intended recipient, you are
hereby notified that any review, dissemination, distribution or
duplication of this communication is strictly prohibited. If you are not
the intended recipient, please contact the sender by reply email and
destroy all copies of the original message.
list Stef Coene
▸
On Friday 19 January 2007 15:56, Hubbard, Greg L wrote:
Etienne -- you are going to have to find someone to write that and add it to Hobbit. Path-based alarm suppression is one of the holy grails in the network management industry, and the reason it has not yet been solved is because it is a difficult problem. For small networks you can come up with a solution, but if you are using VLANs and WAN's and load balancers and all that other stuff it gets to be rather difficult. There are many commercial software vendors that claim to have this problem solved -- but sometimes even their demos do not work. The little bit of dependency specification that you can put into Hobbit does indeed work, but not across the board.
As fas I know, the hobbit _server_ can do this for the network tests. All network tests are done in 1 run. The data is processed and dependencies are calculated and errors are generated. The problem is client checks. When an error is received, the hobbit server needs to check it's dependencies. But some of these dependencies are also client checks that are maybe not (yet) received. So the server can never know for sure if all dependencies are satisfied. The only way I can imagine this to work is if all checks are send every 5 minutes. So, when a red check is received, the server waits 5 minutes untill all checks are updated and it can starts checking the dependencies. But what with checks that are send every hour ? And do you really want to wait 5 minutes? s Stef
list Rich Smrcina
I wrote about this some time back, the depends tag doesn't appear to work properly. You can specify a router (which is just another host) that things depend on, and that works. But a multi-level dependency (which depends seems to try to provide) would also be a good thing.
▸
Stef Coene wrote:On Friday 19 January 2007 15:56, Hubbard, Greg L wrote:Etienne -- you are going to have to find someone to write that and add it to Hobbit. Path-based alarm suppression is one of the holy grails in the network management industry, and the reason it has not yet been solved is because it is a difficult problem. For small networks you can come up with a solution, but if you are using VLANs and WAN's and load balancers and all that other stuff it gets to be rather difficult. There are many commercial software vendors that claim to have this problem solved -- but sometimes even their demos do not work. The little bit of dependency specification that you can put into Hobbit does indeed work, but not across the board.As fas I know, the hobbit _server_ can do this for the network tests. All network tests are done in 1 run. The data is processed and dependencies are calculated and errors are generated. The problem is client checks. When an error is received, the hobbit server needs to check it's dependencies. But some of these dependencies are also client checks that are maybe not (yet) received. So the server can never know for sure if all dependencies are satisfied. The only way I can imagine this to work is if all checks are send every 5 minutes. So, when a red check is received, the server waits 5 minutes untill all checks are updated and it can starts checking the dependencies. But what with checks that are send every hour ? And do you really want to wait 5 minutes? s Stef
--
Rich Smrcina VM Assist, Inc. Phone: XXX-XXX-XXXX Ans Service: XXX-XXX-XXXX user-61add9955ef9@xymon.invalid Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
list Etienne Marganne
Hello,
Well yes indeed it could work well even though all the work necessary to
build the right configuration file will be huge for a network such as ours.
The idea, to explain everybody in the mailing list, would be to link the
different devices together by the means of the combo test. They work as
follow :
BigTest1 = hostA.test && hostB.test
BigTest2 = hostC.test || hostD.test
BigTest3 = BigTest1 || BigTest2
To propagate correctly the informations through a network path, do as
follow:
A - 1 - 2 - 3 - F
1' = A (to remember the test done on A)
2' = 1' and 1 (if you want to join 2 you must at least having 1', A let's
say and 1)
3' = 2' and 2 (same idea for 3)
F' = 3' and 3
Another kind of topology:
/- 1 -\
A /-- 2 -- F
\-- 3 -/
1' = A (useful to propagate surely the information)
2' = A
3' = A
F = (1' and 1) || (2' and 2) || (3' and 3)
Last kind of topology (full mesh):
/- 1 -\
/ | \
A /--- 2 -- F
\ | /
\-- 3 -/
1' = A (useful to propagate surely the information)
2' = A
3' = A
F = A and (1 || 2 || 3)
Here it is. If you think about network topology I forgot, feel free to tell
them (with the solution if available ;-)).
Of course this does not solve directly the alerts flood problem. I will try
to find out what could be possible with alerts based on the combo tests and
no more on simple tests.
If this solution can look pretty, at least to me, at the first read you have
to remember that it is still a lot work, even with scripts doing (you have
to write the scripts do not you ?). For the people with two ore more Hobbit
servers, this is even worse because the views are most likely not the same.
Thanks for reading and taking part,
Etienne Marganne,
TI Automotive
▸
-----Original Message-----
From: Charles Goyard [mailto:user-98f9625a7a59@xymon.invalid]
Sent: vendredi 19 janvier 2007 14:28
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Dependency sytem in Hobbit
Hi,
try the bbcombotest to add HA logic and make the depend tag point to the
aggregated dot.
See bbcombotest.cfg
--
Charles Goyard - user-98f9625a7a59@xymon.invalid - (+33) 1 45 38 01 31
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
list Jason Altrincham Jones
Ok, have just read this E-mail but I thought that if you did the route tag on a host it only went yellow (unreachable by proxy) if itself and a device in it's route entry failed (i.e. if the gateway fails but the host still responds to ping then it stays green) though Henrik would have to confirm this as I haven't had such a situation. Also I'm curious how the CPU, hard drive etc, dependencies would work? If CPU on host1 has a high load what effect would that have on host2? Unless of course a database was being hosted by host1... Also can I ask, how large is this network? Henrik's is ~4000 or something ours is about 400-500. Jason.
▸
From: Hubbard, Greg L [mailto:user-d970b5e56ec9@xymon.invalid]
Sent: 19 January 2007 14:56
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] Dependency sytem in Hobbit
Etienne -- you are going to have to find someone to write that and add
it to Hobbit. Path-based alarm suppression is one of the holy grails in
the network management industry, and the reason it has not yet been
solved is because it is a difficult problem. For small networks you can
come up with a solution, but if you are using VLANs and WAN's and load
balancers and all that other stuff it gets to be rather difficult.
There are many commercial software vendors that claim to have this
problem solved -- but sometimes even their demos do not work. The
little bit of dependency specification that you can put into Hobbit does
indeed work, but not across the board.
GLH
From: Marganne, Etienne [mailto:user-b63c96159c04@xymon.invalid]
Sent: Friday, January 19, 2007 5:58 AM
To: user-ae9b8668bcde@xymon.invalid
Cc: user-ce4a2c883f75@xymon.invalid
Subject: [hobbit] Dependency sytem in Hobbit
Hello all,
I am Etienne Marganne, a new comer in TI Automotive, a society
which uses Hobbit as a monitoring tool, I will be in charge of Hobbit
tool. We would like to enhance our monitoring tool in order to get more
detailed informations through it.
One of the first thing we would like to do is to create a
dependency system between monitored hosts across our network. For all
the further discussion, please keep in mind that we have a very large
network and two Hobbit servers where we would like to keep the same
"hh-hosts" file.
The idea of the dependency system is the following one: once we
have a host that fails on a network path in our network all the hosts
further that one will be very likely unreachable. This will cause a lot
of alerts to be triggered because of one failure. This is not
interesting because our team will be flooded by those alerts. Therefore
it could be useful to create dependencies so that those further devices
on the same path will not trigger alerts (basically turning red).
There is a specific tag that can be used to do such a work, the
"route" tag. In our case with two Hobbit servers, we would tune that
with the "route_BBLOCATION" tag. Knowing that there are Hobbit clients
on all the network nodes between the two endpoints, the simplest idea
would be to list all the nodes in the description of those tags. This
could work even if it would generate of job. A little bit further here,
let's say that one node fails on a path, it is very probable that if you
know that the following nodes are unreachable, you may not want to test
them anymore (to forbid them to turn red).
Now think of a big network with a lot of redundancy, it is very
probable that there will be indeed a lot of network paths between a
server and one final host. If on one path one node fails, it does not
mean that the final client is not reachable. But with the "route" tag,
that client would be signal as unreachable since a member of the "route"
has failed. This is not comfortable at all.
What we would like to know, or to get, if there is a way to get
this dependency system work:
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| |
| --------- 5 ------------6 ----------- |
There are two paths to reach the Final Client, one composed by
1, 2, 3, 4 and another one composed by 5, 6.
With the current "route" tag we would have such a list of nodes:
route_HobbitServerA:1,2,3,4,5,6 then if 1 fails and the path 1-2-3-4
would not work anymore but the 5-6 one would still.
A good dependency system would to have such a thing: Final
Client depends on 4, 4 depends on 3, 3 depends on 2, 2 depends on 1 but
Final Clients also depends on 6 which depends on 5. More over this would
also solve that kind of topology :
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| | |
| --------- 5 ------------6 ----------- |
Where there is a link between 2 and 5, 2 and 6, 5 and 3, 6 and 3.
Maybe that something could be set up with the "depends" tag,
however I do not know how the informations will propagate through the
different dependencies done that tag.
Even further on the topic, the "route" tag performs only ping
tests which does not seem enough to me. I would like to add cpu, disks,
... tests to the whole dependency system.
Thank you for your help and answers,
Regards,
Etienne Marganne
TI Automotive.
The information contained in this transmission may contain privileged
and confidential information. It is intended only for the use of the
person(s) named above. If you are not the intended recipient, you are
hereby notified that any review, dissemination, distribution or
duplication of this communication is strictly prohibited. If you are not
the intended recipient, please contact the sender by reply email and
destroy all copies of the original message.
list Maik Heinelt
Hello, We often use Network-volumes for backup. Is there a way to use Hobbit to check this Harddisks for free space? At the moment I`ve mounted this into linux for checking free space. This Network-HDD`s using also a linux OS, but I cannot install something. Regards M.Heinelt -- 愛知県一宮市富士２－２－２２ 株式会社 ベガシステムズ TEL ０５８６－７１－３９０３ FAX ０５８６－７１－４０７１
list Etienne Marganne
Hello all, After another deep look into Hobbit mechanisms, it looks like the idea of using the combo tests to create a tree structure is good and you can link that structure to the alerts. This is done by putting rules that are based upon combo tests since they are considered as standard tests (with an historic, statistics ...). Now the idea would to stop the alert floods triggered when a critical device on a path falls down. The tree structure helps gathering all the necessary informations into one test. We can now trigger alerts on those alerts preferably than on common bb-hosts tests, but the flood still remains. It remains because you have to trigger alerts on each combo tests to know exactly where it has failed. And since all your combo tests are involved whenever a failure occurs at some point the following nodes will be unreachable in this case: A - 1 - 2 - 3 - F If anybody has an idea he is welcome ... :-) Etienne Marganne, TI Automotive.
▸
From: Jones, Jason (Altrincham) [mailto:user-ee957b46acd2@xymon.invalid]
Sent: vendredi 19 janvier 2007 17:10
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] Dependency sytem in Hobbit
Ok, have just read this E-mail but I thought that if you did the route tag
on a host it only went yellow (unreachable by proxy) if itself and a device
in it's route entry failed (i.e. if the gateway fails but the host still
responds to ping then it stays green) though Henrik would have to confirm
this as I haven't had such a situation. Also I'm curious how the CPU, hard
drive etc, dependencies would work? If CPU on host1 has a high load what
effect would that have on host2? Unless of course a database was being
hosted by host1...
Also can I ask, how large is this network? Henrik's is ~4000 or something
ours is about 400-500.
Jason.
From: Hubbard, Greg L [mailto:user-d970b5e56ec9@xymon.invalid]
Sent: 19 January 2007 14:56
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] Dependency sytem in Hobbit
Etienne -- you are going to have to find someone to write that and add it to
Hobbit. Path-based alarm suppression is one of the holy grails in the
network management industry, and the reason it has not yet been solved is
because it is a difficult problem. For small networks you can come up with
a solution, but if you are using VLANs and WAN's and load balancers and all
that other stuff it gets to be rather difficult.
There are many commercial software vendors that claim to have this problem
solved -- but sometimes even their demos do not work. The little bit of
dependency specification that you can put into Hobbit does indeed work, but
not across the board.
GLH
From: Marganne, Etienne [mailto:user-b63c96159c04@xymon.invalid]
Sent: Friday, January 19, 2007 5:58 AM
To: user-ae9b8668bcde@xymon.invalid
Cc: user-ce4a2c883f75@xymon.invalid
Subject: [hobbit] Dependency sytem in Hobbit
Hello all,
I am Etienne Marganne, a new comer in TI Automotive, a society which uses
Hobbit as a monitoring tool, I will be in charge of Hobbit tool. We would
like to enhance our monitoring tool in order to get more detailed
informations through it.
One of the first thing we would like to do is to create a dependency system
between monitored hosts across our network. For all the further discussion,
please keep in mind that we have a very large network and two Hobbit servers
where we would like to keep the same "hh-hosts" file.
The idea of the dependency system is the following one: once we have a host
that fails on a network path in our network all the hosts further that one
will be very likely unreachable. This will cause a lot of alerts to be
triggered because of one failure. This is not interesting because our team
will be flooded by those alerts. Therefore it could be useful to create
dependencies so that those further devices on the same path will not trigger
alerts (basically turning red).
There is a specific tag that can be used to do such a work, the "route" tag.
In our case with two Hobbit servers, we would tune that with the
"route_BBLOCATION" tag. Knowing that there are Hobbit clients on all the
network nodes between the two endpoints, the simplest idea would be to list
all the nodes in the description of those tags. This could work even if it
would generate of job. A little bit further here, let's say that one node
fails on a path, it is very probable that if you know that the following
nodes are unreachable, you may not want to test them anymore (to forbid them
to turn red).
Now think of a big network with a lot of redundancy, it is very probable
that there will be indeed a lot of network paths between a server and one
final host. If on one path one node fails, it does not mean that the final
client is not reachable. But with the "route" tag, that client would be
signal as unreachable since a member of the "route" has failed. This is not
comfortable at all.
What we would like to know, or to get, if there is a way to get this
dependency system work:
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| |
| --------- 5 ------------6 ----------- |
There are two paths to reach the Final Client, one composed by 1, 2, 3, 4
and another one composed by 5, 6.
With the current "route" tag we would have such a list of nodes:
route_HobbitServerA:1,2,3,4,5,6 then if 1 fails and the path 1-2-3-4 would
not work anymore but the 5-6 one would still.
A good dependency system would to have such a thing: Final Client depends on
4, 4 depends on 3, 3 depends on 2, 2 depends on 1 but Final Clients also
depends on 6 which depends on 5. More over this would also solve that kind
of topology :
Hobbit Server A ---- 1 ---- 2 ---- 3 ---- 4 ---- Final Client
| | |
| --------- 5 ------------6 ----------- | Where
there is a link between 2 and 5, 2 and 6, 5 and 3, 6 and 3.
Maybe that something could be set up with the "depends" tag, however I do
not know how the informations will propagate through the different
dependencies done that tag.
Even further on the topic, the "route" tag performs only ping tests which
does not seem enough to me. I would like to add cpu, disks, ... tests to the
whole dependency system.
Thank you for your help and answers,
Regards,
Etienne Marganne
TI Automotive.
The information contained in this transmission may contain privileged and
confidential information. It is intended only for the use of the person(s)
named above. If you are not the intended recipient, you are hereby notified
that any review, dissemination, distribution or duplication of this
communication is strictly prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy all copies of the
original message.
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
list Alessandro Tinivelli
▸
Maik Heinelt ha scritto:
Hello, We often use Network-volumes for backup. Is there a way to use Hobbit to check this Harddisks for free space?
i have similar question: some of my linux server mount a nfs drive: can I include it in free space monitoring? by default the graphs don't show it. thanks
list Wolfgang Wutz
Hello, I'm not sure, but I think on linux machines Hobbit gathers information about free space on hard disks using the "df" command. Take a look at $BBHOME/client/bin, there are shell scripts for serveral OSes. Alter the df-command in "hobbitclient-linux.sh" by removing the "l" switch, to make it show all mounted file systems - also the network drives. It should look something like this: "df -P -x none -x tmpfs -x shmfs -x unknown -x iso9660 |..." Just give it a try... :)
▸
-----Original Message----- From: Alessandro Tinivelli [mailto:user-f57e46de7c58@xymon.invalid] Sent: Monday, January 22, 2007 2:04 PM To: user-ae9b8668bcde@xymon.invalid Subject: Re: [hobbit] Network-Volumes Maik Heinelt ha scritto:Hello, We often use Network-volumes for backup. Is there a way to use Hobbit to check this Harddisks for free space?i have similar question: some of my linux server mount a nfs drive: can I include it in free space monitoring? by default the graphs don't show it. thanks
list Alessandro Tinivelli
Wutz, Wolfgang ha scritto:
Alter the df-command in "hobbitclient-linux.sh" by removing the "l" switch Just give it a try... :)
tried.... works :) thank you!