NetXMS Support Forum

Actual theses are the policies:


"Agent Master Windows" policie:

<config>
   <agent>
      <MasterServers>XX.XX.XX.XX</MasterServers>
      <ConfigIncludeDir>C:\NetXMS\etc\nxagentd.conf.d</ConfigIncludeDir>
      <LogFile>{syslog}</LogFile>
      <FileStore>C:\NetXMS\var</FileStore>
      <SubAgent>winperf.nsm</SubAgent>
   </agent>
</config>



"Agent Config Eventlog Windows" policie:

<config>
   <agent>
      <SubAgent>logwatch.nsm</SubAgent>
   </agent>
   <logwatch>
      <Parser>c:\netxms\var\logwatch_win_eventlog_system_parser.xml</Parser>
      <Parser>c:\netxms\var\logwatch_win_eventlog_application_parser.xml</Parser>
   </logwatch>
</config>



In the "Agent Config Eventlog Windows" i tried to change the <agent> in <core>. This results in a agent crash and the logwatch subagent are still not showing, so i reverted back to <agent>.

In which section i must change the <agent> in <core>?


Best regards,
Marco

Hello @all,

since 2.1 the groups feature in performance tab is new designed. Since that change, the order field/function of dci's performance tabs is not working.

It makes a difference in order for the performance tab if a dci is belonging to a group or not. The order no 200 is sorted between dci's with a order no <200. I made the performance tab config in multiple templates.

I fill the order no field in each dci belonging to a group with the same order no. Is this correct?

Have anyone else this problem/behaviour?


Greetings
Marco

With the config in my first post (with <agent>)  nxagentd.exe -C  shows:

config
+- CORE
|   +- MasterServers
|   |    value: XX.XX.XX.XX
|   +- ConfigIncludeDir
|   |    value: C:\NetXMS\etc\nxagentd.conf.d
|   +- LogFile
|   |    value: {syslog}
|   +- FileStore
|   |    value: C:\NetXMS\var
|   +- SubAgent
|        value: winperf.nsm
+- agent
|   +- MasterServers
|   |    value: XX.XX.XX.XX
|   +- ConfigIncludeDir
|   |    value: C:\NetXMS\etc\nxagentd.conf.d
|   +- LogFile
|   |    value: {syslog}
|   +- FileStore
|   |    value: C:\NetXMS\var
|   +- SubAgent
|        value: logwatch.nsm
|        value: winperf.nsm
|        value: logwatch.nsm
|        value: filemgr.nsm
+- logwatch
|   +- Parser
|        value: c:\netxms\var\logwatch_win_eventlog_system_parser.xml
|        value: c:\netxms\var\logwatch_win_eventlog_application_parser.xml
|        value: c:\netxms\var\logwatch_win_eventlog_system_parser.xml
|        value: c:\netxms\var\logwatch_win_eventlog_application_parser.xml
+- filemgr
     +- RootFolder
          value: c:\

In the subagentlist of the management console only the winnt and winperf subagents are showing (see attachment, please).

I test the eventlog with:   eventcreate /T ERROR /ID 1000 /L APPLICATION /D "TestError"


Greetings
Marco

Hello Victor,

thanx for the info. Tryed the groupname as described and it workes...

Small question: Can a DCI be part of more then one Group? Can i add multiple groups in groupfild with a "," or ";" ?

Greetings
Marco

Hello Victor,

this does not help. Logwatch is still not shown in subagent list.

Greets
Marco

Hello @all,

wie use policys to deploy the agent configs. One "Master" policy:

<config>
   <agent>
      <MasterServers>XX.XX.XX.XX</MasterServers>
      <ConfigIncludeDir>C:\NetXMS\etc\nxagentd.conf.d</ConfigIncludeDir>
      <LogFile>{syslog}</LogFile>
      <FileStore>C:\NetXMS\var</FileStore>
      <SubAgent>winperf.nsm</SubAgent>
   </agent>
</config>

An one policy to get alarms from windows eventlog:

<config>
   <agent>
      <SubAgent>logwatch.nsm</SubAgent>
   </agent>
   <logwatch>
      <Parser>c:\netxms\var\logwatch_win_eventlog_system_parser.xml</Parser>
      <Parser>c:\netxms\var\logwatch_win_eventlog_application_parser.xml</Parser>
   </logwatch>
</config>


Until Agent 2.0.8 this works without problems. Since i upgraded the agents to 2.1 (64bit), the 2.1 agent is not loading the logwatch subagent.

All 2.0.8 agents have loaded the logwatch subagent and sending windows event is working.

We using NetXMS Server V2.1 64bit on Win7 64bit Host with MySQL 5.6.35 64bit.

Greetings
Marco

Hello @all,

since update from 2.0.8 to 2.1 the Grouping from perfomance tab is broken. Group field in performance in settings dialog tab only shows bracket and numbers (ex.: '##1485') and there is no button to select the group dci.

The groups in the perfomance tab are splitt in a graph for each dci.

How can i get this to work as expected? There are no errors at the upgrade from 2.0.8 to 2.1.

Using Windows 7 64-bit (German) as NetXMS Host and MySQL 5.6.35 (64bit) at the same Host as DB.


Greetings
Marco

Meanwhile i figured out that one system spams NetXMS with thousands and thousand of windows eventlog entrys.

I killed the agent on that system and restored the NetXMS database from yesterday. Now, NetXMS runs like before... :-)

Hello @all,

since yesterday i can't login into NetXMS ( V2.0.8 ). I tried to restart the service (Win7, 64bit) but the windows service console always says: starting... netxmsd.exe is always running at 24% cpu. I killed the process and check the db (nxdbmgr check), but there are no error or anything else. All checks are green.

Then i started netxms core with debug log (please see log in attachment) but there are, in my opinion, no errors or so. The last two lines are always:

[13-Mar-2017 09:23:58.177] [DEBUG] AccountStatusUpdater: wakeup
[13-Mar-2017 09:23:58.177] [DEBUG] ConfigReadStr: (cached) name=BlockInactiveUserAccounts value="0"


I don't know what i can further do... I would be grateful for any little help or advice...

Thanx.

Greets
Marco

Ok. Thanks for the Info.

Greets
Marco

Hello @all,

is there currently a way to create a graph or a line chart from a DCI summary table? I want to visualise the CPU utilization from our servers. I created a summary table but i didn't find a way to create a graph from it...

Thanx for help.

Greets
Marco

I found a solution myself. I'm using following filter script in events to filter the message text with wildcards:

if($event->message ~= "(.*)ERP Basis System(.*)") return false;
else return true;

Greets
Marco

Thanks for the reply. I understand this.

But i think that the code from above is false. Can i use "*" als wildcard in filtering code? Is the script above functional in NetXMS?

Hello @all,

i'd like to implement a filtering script in event processing:

-----
if ($event->message like "*ERP Basis System*"){
  return false; // Match rule
}
return true;
-----

Event processing should only throw a alarm, if there is NOT the text "ERP Basis System" in the message text of the event. How can/must i use wildcards in filtering scripts?

Thanks for helping me...

Greets
Marco

Hi Victor,

works perfect... thanks for the hint...

Greets
Marco