# Odd filtering behavior with system.alarm.queryStatus

**URL:** <https://forum.inductiveautomation.com/t/odd-filtering-behavior-with-system-alarm-querystatus/18198>\
**Category:** Ignition\
**Created:** [May 29, 2018, 5:02pm UTC](https://forum.inductiveautomation.com/t/odd-filtering-behavior-with-system-alarm-querystatus/18198 "2018-05-29T17:02:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrogers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mrogers/32/4110_2.png) [@mrogers](https://forum.inductiveautomation.com/u/mrogers)\
**Post date:** [May 29, 2018, 5:02pm UTC](https://forum.inductiveautomation.com/t/odd-filtering-behavior-with-system-alarm-querystatus/18198/1 "2018-05-29T17:02:08Z")

</div>

I’m trying to use the system.alarm.queryStatus function using the source keyword:

```auto
providers = ["*btagprovider*"]
results = system.alarm.queryStatus(source = providers)

```

I am 100% sure this is the exact tag provider name, so that the source path is prov:btagprovider:/tag:blahblahblah. I have even copied and pasted from that source path into the providers assignment line above, it finds nothing. However, if I go down to something like just providers = ["\*btag\*"], it finds things. The actual provider name does have capitalization and I’ve tried that, still nothing. Similar situation with other tag providers - they work with limited sections of the provider name but thats it.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 29, 2018, 5:03pm UTC](https://forum.inductiveautomation.com/t/odd-filtering-behavior-with-system-alarm-querystatus/18198/2 "2018-05-29T17:03:40Z")

</div>

What version are you using? There was a known regression in 7.9.5 (fixed in 7.9.6+)

---

<div class="post-metadata">

**Author:** ![mrogers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mrogers/32/4110_2.png) [@mrogers](https://forum.inductiveautomation.com/u/mrogers)\
**Post date:** [May 29, 2018, 5:09pm UTC](https://forum.inductiveautomation.com/t/odd-filtering-behavior-with-system-alarm-querystatus/18198/3 "2018-05-29T17:09:46Z")

</div>

Unfortunately I’m already at 7.9.6

---

<div class="post-metadata">

**Author:** ![mrogers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mrogers/32/4110_2.png) [@mrogers](https://forum.inductiveautomation.com/u/mrogers)\
**Post date:** [May 29, 2018, 5:21pm UTC](https://forum.inductiveautomation.com/t/odd-filtering-behavior-with-system-alarm-querystatus/18198/4 "2018-05-29T17:21:48Z")

</div>

Huh. This does not have the behavior I would expect for the source filter. It looks like if I use

```auto
["prov:btagprovider:/tag:*:/alm:*"]

```

it works fine. I would have expected just one asterisk to take care of everything on one side or the other of the string but it looks like that isn’t the case.