NetXMS Support Forum

Quote from: Alex on August 03, 2008, 09:38:32 PM
Как пользоваться:
1. StatusThresholds
2. StatusTranslation
3. Custom Atrributes в настройках Node

StatusThresholds i StatusTranslation nuzno menjat' tol'ko esli hotite menjat' default algoritm dlja status propagation i status calculation.
Pro custom attributes ja uze pisal v etoj vetke.

Quote from: Alex on August 03, 2008, 09:38:32 PM
Что такое:
1. BeaconHosts

Spisok IP adresov (razdelennih zapjatimi), na kotorie NetXMS server periodicheski delaet ping. Esli ni odin iz nih ne otvechaet, to server schitaet chto propal ego sobstvennij link k seti, i generit sootvetstvujuschij event.

Quote from: Alex on August 03, 2008, 09:38:32 PM
2. DisableVacuum

Imeet smisl tol'ko esli baza dannih - PostgreSQL. Zapreschaet housekeeper'u davat' comandu VACUUM.

Quote from: Alex on August 03, 2008, 09:38:32 PM
3. FixedStatusValue
4. StatusShift
5. StatusThresholds
6. StatusTranslation

parametri dlja default algoritmov status calculation i status propagation - to, chto est' na zakladke Status Calculation v svojstvah ob'ekta.

Quote from: Alex on August 03, 2008, 09:38:32 PM
7. SyncInterval

Interval synhronizacii dannih - t.e. naskol'ko chasto izmenenija, nahodjaschiesja v pamjati, zapisivajutsja v bazu. V sekundah.

Quote from: Alex on August 03, 2008, 09:38:32 PM
8. StatusPropagationAlgorithm
9. StatusCalculationAlgorithm

Default algoritmi dlja status calculation i status propagation.

Quote from: Alex on August 03, 2008, 09:38:32 PM
10. HouseKeepingInterval

Interval zapuska housekeeper'a (v sekundah). Housekeeper udaljaet ustarevshie zapisi iz logov i sobrannie dannie dlja DCI, zachischaet udalennie ob'ekti, i delaet VACUUM v sluchae PostgreSQL bazi.

Quote from: Alex on August 03, 2008, 09:38:32 PM
11. PollCountForStatusChange

Skol'ko pollov podrjat dolzno vernut' oshibku, chtobi interfeis ili service bil pomechen kak CRITICAL.

Proshu proschenija, ja sejchas ne doma, podkljuchajus' redko i po nemnogu. Nachal s problemi padenija servera, i do ostal'nogo ne dobralsja

Ne vse veschi iz perechislennogo novie, mnogie bili uze ran'she. Budu otvechat' po punktam.

Quote from: Anth0ny on August 04, 2008, 12:05:06 PM
- Scripts now can be used to form event's message (via %[..] macro)

Mozno sozdat' skript v biblioteke scriptov (Control Panel -> Script Library), i podstavljat' stroku, vozvraschaemuju etimscriptom v teksti soobschenij. Naprimer, delaem script pod nazvaniem TEST:


sub main()
{
   return "my string";
}


Teper' esli napisat' v tekste naprimer alarma %[TEST], to eto budet zameneno na stroky my string.
Script imeet dostup k dannim tekuschej nodi cherez peremennuju $node, i k parametram obrabativaemogo eventa cherez peremennuju $event.
Takim obrazom mozno naprimer vidavat' perevedennie nazvanija statusov - vmesto %S ispol'zovat' svoj script, naprimer takoj:


sub main()
{
switch($event->severity)
{
case 0:
return "Normal";
case 1:
return "Warning";
// i tak dalee, podstavljaja svoi teksti ...
default:
return "error";
}
}


Quote from: Anth0ny on August 04, 2008, 12:05:06 PM
- Scripts in event processing policy now has access to node properties
  via $node variable and to event properties via $event variable

Script, kotorij vizivaetsja iz event processing policy, imeet dve opredelennie peremenie - $node i $event, dlja dostupa k atributam nodi i sobitija sootvetstvenno. Eti peremennie soderzat ob'ekti, t.e. dostup k atributam osuschestvljaetsja operaciej ->. Naprimer, esli ja hochu poluchit' imja uzla, mne nado napisat' $node->name.

Quote from: Anth0ny on August 04, 2008, 12:05:06 PM
- Added support of custom object attributes

U kazdogo ob'ekta teper' mozno opredeljat' svoi attributi - cherez zakladku "Custom Attributes" v svojstvah ob'ekta ili programmno cherez API. Znachenija etih attributov mozno potom ispol'zovat' v skriptah i tekstah soobschenij. Naprimer, esli ja opredeljaju attribut responsible_person, to mogo v tekste alarma napisat' skazem tak:

Node down; responsible person is %{responsible_person}

Vmesto %{responsible_person} budet podstavleno tekuschee znachenie attributa responsible_person.

Esche odna pros'ba - esli est' vozmoznost' esche raz zapustit' 0.2.22, dobavte v netxmsd.conf takie stroki:


CreateCrashDumps = yes
DumpDirectory = C:\dump


C:\dump dolzen suschestvovat' ili ego mozno zamenit' na ljuboj drugoj suschestvujushij katalog. Pri sboe tam dolzen pojavitsja dump. Otpravte ego na [email protected].

Ja sejchas v doroge, vecherom ili zavtra utrom vse raspishu podrobno, ok?

Voobschem soglasen, sdelaju. Edinstvenno chto pri konfiguracii ob'ekta klastera nado budet ukazivat', kakoj iz virtual'nih adresov eto adres Cluster Group.

A mozno bilo bi zapustit' v debug rezime server? Prosto s konsoli

netxmsd --debug=7

Pered etim v netxmsd.conf postavit' LogFile v kakoj-nibud' fail, i prislat' etot fail mne posle crash'a.

V ljubom sluchae budu segodnja razbiratsja. Sledujuschij raz v onlin'e budu vecherom.

Ja tak ponimaju chto vopros pro installer dlja agenta?
Chtobi vse vse ponimali odinakogo, davajte priderzivatsja ustojavshejsja terminologii: klient - eto konsol' administratora, agent - to, chto rabotaet na hostah i sobiraet informaciju.

V principe installer dostupen, v URL'e dlja 0.2.21 zamenit' na 0.2.22. No tam net nikakih principial'nih izmenenij po sravneniju s 0.2.21.

U ob'ekta klastera net IP adresa. Mozno konechno cht-nibud' podstavljat', vopros tol'ko - chto?

Change log:

- Scripts now can be used to form event's message (via %[..] macro)
- Scripts in event processing policy now has access to node properties
  via $node variable and to event properties via $event variable
- Implemented XML encoding for NXCP messages
- Added support of custom object attributes
- Minor map improvements
- Fixed issues: #196, #201, #216, #220, #221, #222, #225, #226, #230, #231

Dostupno dlja skachivanija:

Windows installer - https://www.netxms.org/download/netxms-0.2.22.exe
Source package - https://www.netxms.org/download/netxms-0.2.22.tar.gz

Oficial'nuj reliz budet chut' pozze.

Most likely schema name was changed on copy. For example, if you copy database as sa user, tables may have been created in dbo schema, like dbo.config. If after that you create database user netxms, and use it for connection NetXMS server to database, it expects to found tables in schema "netxms", like netxms.config.

Also, you should not check "initialize database" when connecting new NetXMS server installation to existing database.

Best regards,
Victor

Сделано в 0.2.22

Hello!

New installation should just take all information from existing database. Could you please describe step by step how you connect existing database to new installation?

Best regards,
Victor