<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Cannot read measurement unit information: Illegal repetition]]></title><description><![CDATA[<p dir="auto">I've been able to figure out how to poll a lot of information from SNMP, but as I'm trying to dump this into dashboards, I'm receiving the following error:</p>
<p dir="auto">Cannot read measurement unit information: Illegal repetition near index 28<br />
.1.3.6.1.4.1.41112.1.4.7.1.3.{instance}</p>
<p dir="auto">Some google searching reveals that the java implementation of regex requires \\ before the { however with various attempts/changes and more searching, I'm not finding anything that works and doesn't break what I already have working <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":-)" alt="🙂" /></p>
<p dir="auto">Since I don't quite know what I'm doing, I'm not sure if this is an issue with the script in Instance Discovery, or if there is a bug of some sort when building dashboards, that doesn't like an SNMP OID that references {instance}.</p>
]]></description><link>https://forum.netxms.org/topic/7690/cannot-read-measurement-unit-information-illegal-repetition</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 18:38:01 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7690.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 10 Jun 2023 21:45:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cannot read measurement unit information: Illegal repetition on Mon, 12 Jun 2023 15:14:26 GMT]]></title><description><![CDATA[<p dir="auto">Yes, {} characters are interpreted as part of regular expression. These fields will be renamed, e.g. "DCI name regular expression" to give more understanding.</p>
]]></description><link>https://forum.netxms.org/post/32512</link><guid isPermaLink="true">https://forum.netxms.org/post/32512</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Mon, 12 Jun 2023 15:14:26 GMT</pubDate></item><item><title><![CDATA[Reply to Cannot read measurement unit information: Illegal repetition on Sat, 10 Jun 2023 23:19:20 GMT]]></title><description><![CDATA[<p dir="auto">Oh.   *facepalm*  I just drop the {instance} and it matches the DCI for the node... haha.</p>
]]></description><link>https://forum.netxms.org/post/32511</link><guid isPermaLink="true">https://forum.netxms.org/post/32511</guid><dc:creator><![CDATA[cbwecomm]]></dc:creator><pubDate>Sat, 10 Jun 2023 23:19:20 GMT</pubDate></item><item><title><![CDATA[Reply to Cannot read measurement unit information: Illegal repetition on Sat, 10 Jun 2023 22:20:49 GMT]]></title><description><![CDATA[<p dir="auto">Sadly, I think I understand what's happening here... and this just isn't possible. </p>
<p dir="auto">Am I correct?   </p>
<p dir="auto">Is there any way to define a DCI and then, also, tell it to ignore the last n characters of the OID based on the context?</p>
]]></description><link>https://forum.netxms.org/post/32510</link><guid isPermaLink="true">https://forum.netxms.org/post/32510</guid><dc:creator><![CDATA[cbwecomm]]></dc:creator><pubDate>Sat, 10 Jun 2023 22:20:49 GMT</pubDate></item></channel></rss>