Слоёв и анимации на картах сейчас нет, завёл feature request: https://github.com/netxms/netxms/issues/3842 Из существующего ближе всего: на одной подложке (план ЦОДа как background image) можно совместить DCI Container с текущими значениями (температуры), DCI Image, который меняет картинку по значению DCI, и статусы объектов. Включать и выключать их по отдельности нельзя - для этого сейчас только отдельные карты с той же подложкой и drill-down между ними.

Not implemented at the moment - the Objects tab covers the Infrastructure tree only. Noted as a feature request, no date on it.

Thanks for the reply and information

Filed as https://github.com/netxms/netxms/issues/3480 for design discussion. Option 3 is the right shape, but one thing needs settling before you build on it: user custom attributes will not work as a backing store for ordinary users. CMD_UPDATE_USER is handled by ClientSession::updateUser() and requires SYSTEM_ACCESS_MANAGE_USERS, with no exemption for modifying your own account — password change and 2FA binding both special-case userId == m_userId, custom attributes do not. A non-admin operator saving their own date format gets access denied. So the per-user store needs a server-side change either way: a self-update path restricted to own custom attributes, or a separate per-user key/value store with its own command and access check. That choice determines the client API, so it should come before more work on the merge logic. Beyond that, option 3 needs an explicit rule for which preferences are machine-local and which are per-user. Without one, every preference added later is a judgement call and the split rots — your HTTP_* and window geometry cases are exactly what such a rule has to answer. Your points 3 and 4 are a separate problem, worth splitting off: the RWT store sits in the servlet container state directory, so it is lost on container restart and on .war update. Persisting that directory, or moving the store out of it, fixes preference loss in the web client on its own, with none of the per-user work — and it covers theme files, map tile cache and MIB downloads at the same time.

Hi, Yes, it's on the roadmap, but it might end up in the enterprise build -- we are not sure yet.

Objects already have a "presentation image" property that is meant to control exactly this. It turns out it's currently ignored when the object is rendered on the geo map, so you always get the default icon there. I've opened an issue to fix it — once done, your custom presentation image will be used on geo maps as well. Thanks for the report.

Is your feature request related to a problem? Please describe. Currently, installing and maintaining the NetXMS Management Console on Windows requires manually downloading the installer from the official website and running through the setup wizard. While this method works perfectly fine, it bypasses the modern package management ecosystem that many Windows administrators now rely on for seamless software deployment and automated workstation updates. Describe the solution you would like I would like to request official support for installing the NetXMS client console on Windows using Winget (Windows Package Manager). This could be achieved by submitting and maintaining a package manifest for the NetXMS Management Console in the official Microsoft community repository (https://github.com/microsoft/winget-pkgs). This would allow Windows users to simply open their terminal and run `winget install NetXMS.Console` (or a similar identifier) to get the software up and running natively. It would also allow IT professionals to easily keep the management client updated alongside their other administrative tools using `winget upgrade`. Describe alternatives you have considered The current alternative is performing a manual installation using the executable from the NetXMS website or deploying it via custom enterprise scripts. However, having an official Winget package would greatly simplify the deployment and update processes, especially for users who use automated scripts to provision their IT management workstations. Additional context Since the NetXMS client console already has a Homebrew package available for macOS users (https://formulae.brew.sh/cask/netxms-console), adding Winget support would provide excellent parity for Windows users. It would significantly increase accessibility and make version management much easier across different operating systems. Thank you for considering this enhancement and for the great work on the project!

Сабж. Вводят в заблуждение - предлагаю убрать, оставив только квадратики пустые. Либо, что лучше, если возможно и позволит ширина квадратиков - заполнять автоматически giXX / %interface name%, как в всплывающем меню собственно. [image: state-status.png]

Собственно предложение в топике. Сейчас если сетевой интерфейс в операционном статусе DOWN, то есть нет физического линка - система отображает в строке Speed видимо последнее значение. Это путает и не логично. Лучше если бы отображало в этом случае  0 принудительно, независимо от прочитанного по SNMP значения. В данном случае на приложенной картинке специфичный коммутатор фирмы Planet, он видимо некорректно сам возвращает значение скорости, когда link down. Возможно такое поведение есть еще у каких либо промышленных коммутаторов. Версия 5.2.8 [image: Безымянный2.png]

Hi team, I wanted to inquire if we are expecting any improvements to the map view in NetXMS to enhance clarity, similar to what we see in WeatherMap. For reference, please check the map views in both NetXMS and WeatherMap. In WeatherMap, we get clear visibility into how much traffic is coming from which direction, with different colors for each direction based on traffic percentage. However, in NetXMS, it shows only one link color, making it unclear whether it's representing the inbound or outbound direction—this is handled much more clearly in WeatherMap. Additionally, data source labels cannot be placed differently in NetXMS, which further creates confusion regarding traffic direction. It would be great if we could incorporate similar features to improve usability. Please let me know your thoughts or if there's any timeline for such enhancements. dhaval lad [image: weathermap_map.jpg] [image: netxms_map.jpg]

Hello, I have uploaded a walk from .1 (.txt) and the mib-files (.zip): C9800-L-universalk9_wlc.17.12.05.SPA.bin-v2.zip wlc-C9800-L-F-K9-walk.txt I have edited the walk to remove company name and domains. the data is from 2-Unit-Failover environment with currently 40 active AP. Also showing 86 rogue access points from the neighborhood. Please keep the data confidential. Thanks. best... Detlev

https://github.com/netxms/docker/

Hi, git-enabled configuration might be nice, but then comes a question what should be included like templates and other stuff, so this may end up in serious development effort and the resources are limited. What can be done currently - there's nxshell api that allows to do everything that management client can do. So you can import and export script library scripts (and get list which scripts are in the system).

Yes, it takes some effort to renew them and there's always no time for that. Which images are most problematic, you can just post image URLs from web version of docs or name of chapter.

it would be really useful if you could nest Zones e.g have a Root Zone for a Customer then Child Zones for each site. or create multiple 'Entire Network' at the root level one for each customer. this would also be very useful for assigning permission

Not sure if this has been requested before, but the Dial Gauge is pretty rigid in its configuration with regards to color and values.   You can only have three color zones, and the color zones have to be, yellow, green, red in that order.   That assumes that something on the left/bottom is bad, something in the top/middle is good, and something far to the right is really bad.   This works fine for things like pressure, RPMs, etc but does not work very well for things like battery voltages where "8" could be just as bad as "15" for a 12V battery where both values need to be in the red.  A battery dial gauge really should be red, orange, green, orange, red.   (or possibly red, orange, green, red) I think it would be much more useful to allow us to specify the number of color zones, and in which order.  This could be done with a table, kind of like how we can add multiple Dashboard Elements.  You click Add, specify the minimum and maximum values for the range you are creating, and then choose the color.   The item at the top would be the left/bottom color zone on the gauge.  The next item/range would be the next color zone on the gauge, etc  As a sanity check, you could require that the second color zone HAS to start from where the previous zone ends by pre-populating and graying out the field so it cant be changed.  This way, you couldn't overlap the end of color zone 1 with a value of like 11, and then start color zone 2 at 10.     I thought about having the ability to reorder these, but then I think you'd have to give up the sanity check...and that's probably not necessary anyhow since you can adjust the values and colors on each to match your needs.

Templates are GREAT, but, occasionally we realize after the fact there is a "better" way to build something, or we have a new use case that requires us to split DCI's defined in templates into new templates.   Currently, we can keep historic data by removing the template, but not removing the DCIs however this isn't really ideal since the graphs are wrong anyhow.   I was thinking it would be pretty nice if a template would automatically merge two DCI's based on identical matching names and other fields.   This could be enabled or disabled somehow in the configuration, just in case someone didn't want this behavior.     I think the DCI's would need to match identically, 100%... as would be the case when you copy or move DCI's between templates.  If something doesn't match, then they wouldn't merge and a new one would be created.   If that happened accidentally, say for instance if you copied a DCI to a new template and then changed the name and then applied it.... then you could fix this by manually merging the DCI's (after you fixed the name change on the old one), by multi-selecting the two of them, right clicking, and then going to "Actions > Merge" or something like that.   [image: Untitled.png] Merging DCI's manually through the menu would do the same thing as the automatic method; it would check to ensure 100% of the configuration fields were the same, and then move the oldest set of data into the newer DCI.   A warning prompt for Yes/No and brief explanation of what will happen wouldn't be a bad idea either.   Just for simplicity, you could only merge 2 DCIs at a time.   I'm sure I could poke around in the database and do this in psql... but I'd rather there be an official NetXMS supported method haha

+1 to both requests. 3rd mouse button to move map (press down mouse wheel) and mouse wheel to zoom in and zoom out will be super useful. A little bit optimization performance for bigger maps and I will be very happy TY.

Yes, for time being it's file delivery policy, not file removal policy. Could be nice thing, but development resources are limited and there are more important features to work on, so probably only with sponsored development. It's probably possible to add files with 0 size - this will at least delete contents of files. It's possible to configure action on agent that would do deletion of files. And, also requires quite some effort - nxshell / java app can use file manager api to talk to agent nodes and to the deletion.