NetXMS Support Forum

Hi!

Quote from: Lostavar on October 02, 2008, 10:15:03 PM
1) Is it possible to send alerts using a time-schedule?
For example it want E-Mail notification Monday-Friday to person A, on Saturday and Sunday to person B.

Yes, you can create two rules with different e-mail actions, and use filtering script in each rule to match Monday-Friday or Saturday-Sunday. Script to match Monday-Friday will look like following:


sub main()
{
t = localtime();
return (t->wday >= 1) && (t->wday <= 5);
}


Best regards,
Victor

Hello!

This is because $1 .. $9 is a macros substituted by NetXMS agent itself - they represent arguments for a parameter. If you need to pass $ sign as part of a command, you should use $$.
So your command should looks like:
ExternalParameter = rootInodes:/usr/sbin/df -F ufs -o i / | /bin/tail -1 | /usr/local/bin/awk '{print $$4}' | /bin/sed -e 's/%//g'

First example works, because wc -l gives you only one word, so { print $1 } transformed to { print } doesn't actually affect anything.

Best regards,
Victor

Hello!

Are you running only NetXMS agent on Solaris or server too?

Best regards,
Victor

Hello!

It seems to be quite common problem. In upcoming release, I will change threshold configuration so you will be able to specify for what number of consecutive polls value should be above/below threshold to raise an event.

Best regards,
Victor

Probably most of this could be done via performance counters.
For example, to get number of ASP.NET errors, you need to get value of performance counter "\ASP.NET\Error Events Raised".
To get this counter's value into NetXMS, use parameter PDH.CounterValue, like below:

PDH.CounterValue("\ASP.NET\Error Events Raised")

I suppose that other data should be available as performance counters as well.

Best regards,
Victor

Контролировать время выполнения запросов можно, но не на уровне отдельных DCI.
В данный момент при помощи параметра AgentCommandTimeout можно задать максимальное время ожидания ответа от агента. Если ответ не пришел за указанный промежуток времени, то возвращается ошибка. На ошибки сбора данных для DCI можно делать threshold'ы.
Кроме того, если запрашиваемый параметр является внешним скриптом, то максимальное время выполнения скрипта контролируется параметром агента ExecTimeout.

PollCountForStatusChange - к DCI отношения не имеет (см. например здесь: https://www.netxms.org/forum/index.php/topic,427.0.html). Для решения вышеописанной проблемы сейчас можно использовать average(n) вместо last() в условии threshold'а - хотя это не совсем одно и то-же, как временная мера может использоваться. Я сделаю, что в last() можно будет указывать количество опросов, в течении которых условие должно выполняться, чтобы threshold сработал.

Hello!

Quote from: cjwallace on September 26, 2008, 04:08:54 PM
So can NetXMS do?

1) Monitor Windows disk space

2) Monitor Windows Memory?

3) Monitor CPU Usage?

4) Monitor Windows Services

Yes to all questions.

Quote from: cjwallace on September 26, 2008, 04:08:54 PM
5) Monitor Windows Event Viewer Logs? ( i think from something i was reading is was in the pipeline. Any ideas when this will be availabale?)

Not available yet, but planned for next release.

Quote from: cjwallace on September 26, 2008, 04:08:54 PM
6) Monitor Servers via SNMP

Yes.

Quote from: cjwallace on September 26, 2008, 04:08:54 PM
7) Monitor HP servers , disk array , temperature, failed fans , failed disk

Yes, through SNMP, and you need HP Insight Manager agent installed on server.

Quote from: cjwallace on September 26, 2008, 04:08:54 PM
Monitor servers uptime via ICMP or better

Yes, you can monitor server availablity with ICMP pings (or event monitor ping response times), or check availability of TCP services (like http).

Quote from: cjwallace on September 26, 2008, 04:08:54 PM
9) Network maps. Can i create a network map with icons the represent servers, switches , routers, workstations , internet etc etc

I would say partially yes Unfortunately, maps is not strongest part of NetXMS. You can create maps, add objects and links between them, but you cannot change pictures for them. There are also probably many bugs with the maps. However, you can try

There are also another maps implementation as standalone application, you can try it as well (see here: https://www.netxms.org/forum/index.php/topic,364.0.html).

Best regards,
Victor

Hello!

It's not a plain SQL script. Commands may vary between databases, so it's a set of static and dynamically created SQL queries encoded into nxdbmgr code.

I change the upgrade code to re-create tables instead of adding constraints, hopefully it will work.

Attached is a latest version of nxdbmgr.exe.

Best regards,
Victor

Hi!

Could you please do the following:

1. Post here your netxmsd.conf file
2. Run command


nxdbmgr check


and post here it's output?

Best regards,
Victor

Peresobrannij subagent dlja Windows.

Looks like a bug in handling MS SQL on upgrade (it works fine on my test system, but I have MS SQL 2005). Try to do an upgrade with attached nxdbmgr.exe.

Best regards,
Victor

Hello!

If you have two (or more) IP addresses on your management server, they all should be listed in agents' MasterServers parameter. In your case, all agents should have in nxagentd.conf


MasterServers = 172.28.7.29, 172.28.7.196


Best regards,
Victor

It's hard to implement in current console. However, we are working on completely new management console, where you will be able to detach views from main window. You can see how it will looks like by running nxmc.exe from NetXMS bin directory.

Best regards,
Victor

Icmp.Ping vipolnjaet ping v moment zaprosa. Icmp.PacketLoss, takze kak i Icmp.AvgPingTime i Icmp.LastPingTime, vozvraschajut znachenie, poluchennoe background ping processom dlja zaranee zadannih hostov. T.e. chtobi pol'zovatsja imi, snachala nado propisat' eti hosti v nxagentd.conf, naprimer tak:


*PING
Target = 10.0.0.2:host1
Target = 10.0.0.5:host2


Posle etogo mozno poluchat' parametri Icmp.AvgPingTime i ostal'nie, ispol'zuja libo IP adres, libo imja, zadannoe v konfige.
Sm. takze https://www.netxms.org/documentation/ping_subagent.shtml - neskol'ko ne polno pravda.