through various lists of monitoring systems but somehow got lost ...
Zabbix (http;//www.zabbix.com) may be worth a view. It has monitoring proxy
support. The monitoring server can be clustered (depending on the load).
regards
Petric
s
migration to get away from it. Same for Icinga, Shinken, Sensu and all
the other many nagios forks out there. Also Zabbix.
My current monitoring is snmp-based, and all I need monit for is as a
very narrowly-defined single-purpose watchdog.
--
Alan McKinnon
alan.mckin...@gmail.com
e:
> >> >> On 08/08/2016 19:20, Michael Mol wrote:
> >> >>> On Monday, August 08, 2016 06:52:15 PM Alan McKinnon wrote:
> >> >>>> On 08/08/2016 17:02, Michael Mol wrote:
> > I use Zabbix extensively at work, and have the Zabbix agent on my
of the Memory Management tasks, within
> acceptable confine . Then automate it for later checking on cluster
> test runs with various hardware setups. Eventually these test will be
> extended to a variety of memory and storage hardware, once the
> techniques are automated. No worries, I no
wrote:
On 08/08/2016 19:20, Michael Mol wrote:
On Monday, August 08, 2016 06:52:15 PM Alan McKinnon wrote:
On 08/08/2016 17:02, Michael Mol wrote:
I use Zabbix extensively at work, and have the Zabbix agent on my
workstation reporting back various supported metrics. There's a great
deal you can
ebuilds, like eg zabbix or other apps.
That said, and things being the way they are now, I'd make the suid
behavior the default, since it requires less changes in a running system
(a perl reemerge at most - assuming of course apache is already
installed). If the user wants the separate apache
but it does not support (AFAICT) for logging into a DB.(The FAQ states
answer is coming)
Zabbix is another package but seems like it too provides for
client/server availability etc. Doesn't do much for my needs.
I initially looked at ntop, then found out that it no longer uses a SQL
database
a
solution implemented rather quickly without having to write any of
your own code and the overhead/resources needed on your server would
just be proportional to the number of metrics collected and their
frequency.
My current monitoring tool of choice is zabbix, but there are many options.
Matt
uptly, its memory consumed would climb to fill all 8GB of my physical
memory. And if it happened over night, it'd be to about 1.4GB of swap before
the Zabbix agent stopped sending telemetry to my collector...
--
:wq
signature.asc
Description: This is a digitally signed message part.
gt;
https://www.comptia.org/blog/linux-distributions-for-ethical-hacking-and-pen-testing
>
Paul,
Thanks. I know of Kali but I'm not looking to hack, just to monitor my
network,
preferably with an app that has a GUI interface. One of the apps I've looked
is Zabbix for network monitoring but
the
> application(s) mix is concurrently running then the quick
> test+parameter settings is reasonably well behaved. So thats becomes a
> baseline for further automated tests and fine tuning for a system under
> study.
What kind of storage are you running on? What filesystem? If you're
reads this
list...)
Certainly wouldn't cover someone like me who has a family to support,
but still.
AS a side note, I put 32G of ram on my system and still at times it is
laggy with little processor load and htop shows little <30% ram usage.
What tools do you use to track d
sure someone who commits code to KDE reads this list...)
Certainly wouldn't cover someone like me who has a family to support, but still.
>
> AS a side note, I put 32G of ram on my system and still at times it is
> laggy with little processor load and htop shows little <30% ram usage.
> W
test runs with various hardware setups. Eventually these test will be
extended to a variety of memory and storage hardware, once the
techniques are automated. No worries, I now have enough ideas and
details (thanks to you) to move forward.
Perhaps Zabbix +TSdB can get me further down the path
e your system spending time in iowait swapping data in while
> > you're waiting on it?
> > * Do you notice your system spending time in iowait swapping data out
> > while
> > you're waiting on it? (I.e. as it tries to make room for new memory
> > allocations)
>
> I
this
way.
For deeper studies, I like trace-cmd/Ftrace/KernelShark, but those are
like zabbix on utilization and analytical studies. I use xgalaga as a
quick and dirty; but am surely open to new codes for that sort of quick
and easy feedback.
Ideal values for dirty_bytes and dirty_background_bytes w
16 matches
Mail list logo
