/api/search/lookup indeterminate behavior in 2.2.0-RC1

38 views
Skip to first unread message

Gabe Nydick

unread,
Sep 23, 2015, 2:47:26 PM9/23/15
to OpenTSDB
A couple of strange things.

1) when given a query like this "http://localhost:4243/api/search/lookup?m=MessageQueueBacklog{domain=*}" I get results for more metrics than just the requested one. For example. I'm asking only about "MessageQueueBacklog", but I'm getting "Aborted_clients"

{
  • type: "LOOKUP",
  • metric: "MessageQueueBacklog",
  • tags:
    [
    • {
      • key: "domain",
      • value: "*"
      }
    ],
  • limit: 25,
  • time: 3,
  • results:
    [
    • {
      • tsuid: "0008AA0000010000010000020000030000050000D800000C000034000018000156",
      • tags:
        {
        • host: <redacted>,
        • cluster:
          <redacted>,
        • messagequeue:
          <redacted>,
        • fabric:
          <redacted>,
        • domain:
          <redacted>
        },
      • metric: "Aborted_clients"
      },
    • {
      • tsuid: "0008AA00000100000100000200000D0000050000D800000C000564000018000CAE",
      • tags:
        {
        • host: <redacted>,
        • cluster: <redacted>,
        • messagequeue: <redacted>,
        • fabric: <redacted>,
        • domain:
          <redacted>
        },
      • metric: "Aborted_clients"
      },

2) When I use metric, tag key, and tag value width > 3, the meta data seems to just be wrong. The query I used as my example above yields no results, yet if I search for just the metric name (with no {tags}), I get results that show that "domain" is indeed one of the tags. 

Izak Marais

unread,
Oct 5, 2015, 4:27:58 AM10/5/15
to OpenTSDB
This looks like a (serious) bug. Have you logged it on github? Hopefully they fix it.

ManOLamancha

unread,
Nov 10, 2015, 6:43:28 PM11/10/15
to OpenTSDB
On Wednesday, September 23, 2015 at 11:47:26 AM UTC-7, Gabe Nydick wrote:
A couple of strange things.

1) when given a query like this "http://localhost:4243/api/search/lookup?m=MessageQueueBacklog{domain=*}" I get results for more metrics than just the requested one. For example. I'm asking only about "MessageQueueBacklog", but I'm getting "Aborted_clients"
2) When I use metric, tag key, and tag value width > 3, the meta data seems to just be wrong. The query I used as my example above yields no results, yet if I search for just the metric name (with no {tags}), I get results that show that "domain" is indeed one of the tags. 

Yeah, that's not good. Do you have real-time meta sync enabled? I'm guessing there *could* be an issue with unsynchronized or out of data meta data. If you try disabling real-time meta in your config, then query the TSD I'd like to know if it gives you the proper results. 
Reply all
Reply to author
Forward
0 new messages