device REST param does not work

[robot-ranger]

our agent has 3 devices:

"mxi_m001"
"mxi_r001"
"pr_super"

using the following urls:

• /sample?device=mxi_m001
• /sample?device=mxi_r001

both return a document with all 3 devices; it seems that the device param is not honored

While we are at it; would it be possible to pass multiple devices into the REST request? that would be nice; we have a use case to 'subscribe' to multiple devices and it would be clean if we could open one stream.

something like /sample?device=mxi_m001&device=mxi_r001&path=//Interfaces

[wsobel]

There is not parameter for device. The correct format is: /mxi_m001/sample /mxi_r001/sample /pr_super/sample Check out the REST url: /swagger This will give documentation for the api. Best W

[robot-ranger]

Oh, it is listed in the 2.2 pdf docs:

[robot-ranger]

I see now device param is intended for the host path before params, the context in the pdf made me think it was a ?key= param.
could it be implemented?
as an aside, it would be nice to also be able to specify multiple devices in a sample stream

[wsobel]

Documentation can also be found in the model: https://model.mtconnect.org/#Package___19_0_4_45f01b9_1637706615628_274120_5004

[wsobel]

I can see where the individual documentation could be misleading. I think we need to add classification to documentation of the device parameter.

[wsobel]

The swagger api is built into the agent as well:  https://demo.mtconnect.org/swagger?pretty=true

[robot-ranger]

I can see where the individual documentation could be misleading. I think we need to add classification to documentation of the device parameter.

The juxtaposition of 'device' next to ex 'from' and 'path' in the pdf doc led me to think I could do ?device=

Ill refer to swagger from now on

[robot-ranger]

closing; clearly i misinterpreted the docs

[wsobel]

closing; clearly i misinterpreted the docs

I will open an issue in the projects site to address this. Misinterpretation is our issue since it is not clear enough.