• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Adding a data source column to the primary data sources window

    Wishlist
    3
    7
    1.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      Phillip Weeks
      last edited by Phillip Weeks

      Where we have many ES devices running, it is convenient to have all these machines streaming data to our primary cloud server. Many of the data schemes have identical nomenclature and it would be wonderful if that on the primary data sources screen instead or in addition to the Data Source Type it could filter by data sources Name, We can include the data sources type distinction in the name if we had to know the type. It would help a lot with handling data points since all our devices have the same names across different data sources. We can then filter all client data sources for example a client may have 3 properties, multiple data sources for each, all with same schema, same device names, right now we have no way to isolate just one client's devices as a filtered group on the cloud.

      1 Reply Last reply Reply Quote 0
      • CraigWebC
        CraigWeb
        last edited by

        I think using the new point tagging system is going to be your best bet. Add your specific client as a tag to those points.

        1 Reply Last reply Reply Quote 0
        • phildunlapP
          phildunlap
          last edited by phildunlap

          I concur with CraigWeb, but with the caveat that we haven't included tags in the point attributes transmitted by the Persistent publisher. This is high on our TODO list.

          The more oldschool way of doing this is to make your XIDs more meaningful.

          1 Reply Last reply Reply Quote 0
          • P
            Phillip Weeks
            last edited by

            Yes ok I have not implemented any point tags yet and I do need this to go through persistent TCP so I have decided to decorate the Device-XID with a prefix for now and perhaps change later. Anyhow this does eliminate much of the confusion of which points are from which devices. Thanks guys.

            1 Reply Last reply Reply Quote 0
            • phildunlapP
              phildunlap
              last edited by

              Tags were added to the transmitted data point info in this interim. You can also define additional tags to mixin on either the publisher or the data source.

              1 Reply Last reply Reply Quote 0
              • CraigWebC
                CraigWeb
                last edited by CraigWeb

                Awesome! Was going to ask when this is coming, it going to come in very handy.

                1 Reply Last reply Reply Quote 0
                • phildunlapP
                  phildunlap
                  last edited by

                  I just reread this, and I'm not sure i understood the question in the OP. On a reread, it sounds like this feature exists and should be unmissable:

                  0_1526304450256_dsNameFilter.png

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post