NetXMS Support Forum

thanks

Jasper Reports is a 3rd-party product. All custom extensions (parameter types for GUI, etc.) are described the repository i've shared earlier.

Report designer is unrelated to the NetXMS and you should see TIBCO's guides.
Check section "Resources" at https://www.jaspersoft.com/products/jaspersoft-studio, specifically this video: https://www.youtube.com/watch?v=yRLvJgz9Dxk.

Alternatively, we can offer you custom development or training on both NetXMS and reporting. Plese contact [email protected] for offer.

Quote from: blairmc96 on August 12, 2022, 06:23:49 PM
Can I please get some help with this?

Simplest way is to copy any sample report, change name in file .project, then import into jaspersoft studio. Another way - copy, import, then rename project in the studio.
Once done, edit pom.xml and change "buildUuid" to any other UUID (it's used to distinguish between deployed reports).

Then open main.jrxml and start designing.

DB connection is provided by the reporting server or jaspersoft studio during development phase.
Fields are either defined manually, or you can click "read" in query editor.

You need to copy just .jar (or .zip) files to definitions folder. These files will be unpacked by the reporting server and deployed automatically.

Check this repo: https://github.com/netxms/sample-report

in Script Library there is a script call Hook::CreateInterface. You can put any code there, which will be executed when new interface is about to be created. If you return "true" (or hook is empty) - interface will be created, if false - it will be ignored.

This will not affect existing interfaces, and you'll have to delete them either by hand (filter them by name, for example, and bulk delete) or using script

for (n : GetAllNodes()) {
    println(n->name . "(" . n->id . ")");
    for (i : n->interfaces) {
        println("\t" . i->name);
        if (...) { i->delete(); }
    }
}


Check NXSL documentation for more information: https://www.netxms.org/documentation/nxsl-latest/

Script-based DCI will be the best soluion here, I think.

Script should be something like (pseudo code):


value = null;
if (CURRENT_NAME@$node != null) { // custom attribute CURRENT_NAME on current node
  value = $node->readAgentParameter("..." . CURRENT_NAME@$node);
}
if (value == null) {
  for (item : $node->readAgentList("...")) {
    if (item match "...") {
      // correct element found
      $node->setCustomAttribute(CURRENT_NAME, item);
    }
  }

  if (CURRENT_NAME@$node != null) { // custom attribute CURRENT_NAME on current node
    value = $node->readAgentParameter("..." . CURRENT_NAME@$node);
  }
}

return value;


Hello, dear NetXMSers!

It's that moment when we ask something from you. Please, tell more people just about how powerful and flexible NetXMS system is and leave your review (big or small — anything counts) on Trustpilot and G2.

We hope it's not much and we also hope you can do it with pleasure, as NetXMS really deserves it!
>>> Stay cool and thank you so much in advance.

Sincerely,
Team NetXMS

try node #2277 (you can search by node id in object browser)

Latest (also a bit outdated) is here: https://www.netxms.org/documentation/datadictionary/ (https://www.netxms.org/documentation/datadictionary/netxms-data-dictionary.pdf)

On start agent reports list of protocols supported by libcurl (on debug level 3, I think):

2022.04.21 11:52:37.320 *D* [init.curl          ] cURL supported protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp

Check that you have pop3 available in this list.

nxmc is the webui package, you need this one instead

Check output of "apt-key list", most likely you have old key imported into another keystore.

Quote from: normalcy on April 06, 2022, 02:50:09 PM
Hi, I tried updating using the package, and using the netxms-keyring.gpg however I found I still got the old version expiring on the 24/3 with those.

As some of you already noticed – our signing key for deb repository is expired.
Normally we update the key and ship updated version of the netxms-release package, which transparently install correct version into trusted keys. This time we missed it and now most of you have expired key, which prevent further upgrades.

Error looks something like this:
...
Err:4 http://packages.netxms.org/debian bullseye InRelease
  The following signatures were invalid: EXPKEYSIG 179C0A80CDFADDB1 NetXMS Automatic Signing Key <[email protected]>
Reading package lists... Done
W: GPG error: http://packages.netxms.org/debian bullseye InRelease: The following signatures were invalid: EXPKEYSIG 179C0A80CDFADDB1 NetXMS Automatic Signing Key <[email protected]>
E: The repository 'http://packages.netxms.org/debian bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.


How to fix it:

1) If source and key was added by "netxms-release" package (recommended way), it's simple:


curl --proto '=https' --tlsv1.2 -O https://packages.netxms.org/netxms-release_1.10_all.deb
dpkg -i netxms-release_1.10_all.deb
apt update


2) If key was manually added to trusted.gpg.d


curl --proto '=https' --tlsv1.2 -o /etc/apt/trusted.gpg.d/netxms-keyring.gpg https://packages.netxms.org/netxms-keyring.gpg # adjust file location
apt update


I highly recommend you to migrate to netxms-release package.

3) If key was added with "apt-key add" command

apt-key del 179C0A80CDFADDB11 # repease until apt-key list shows no key
curl --proto '=https' --tlsv1.2 -sSf https://packages.netxms.org/netxms.gpg | apt-key add -


Again, I highly recommend you to migrate to netxms-release package.

Hello.

Yes, it in the works.