Author Topic: JSON Report API missmatch V14 - V17  (Read 711 times)

NereliZ

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
    • View Profile
JSON Report API missmatch V14 - V17
« on: February 12, 2018, 10:59:09 »
Hi,

We are using JSON Reprot API with our QueueMetrics. But after upgrade from version 14 to version 17 we spot some issues which is holding us to use version 14. The problem is the change with some API calls we used to use. In all the cases we send a Queues ids to get only information related to queues we are interested in.

1. In earlier version RTRiassunto was returning information about the all queues passed by queues parameter including queues with no active call. Now it looks like it returns only those with active calls.

2. RTAgentsLoggedIn behaves even worse. We have both version running in parallel to make sure we are ready to make the switch. But the RTAgentsLoggedIn returns different number of logged in agents. While the newer version includes some other agents from other queues and field on_queues populated with the search value, so where is no way to trace which agent belongs to which queue.

It looks more like it completely ignores queues parameter or use it in some kind of different way.

mirkox

  • Full Member
  • ***
  • Posts: 231
  • Karma: 4
    • View Profile
Re: JSON Report API missmatch V14 - V17
« Reply #1 on: February 12, 2018, 11:36:19 »
Hi NereliZ,
please send us the call to the API so that we can test locally

Kind Regards
Mirko

NereliZ

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
    • View Profile
Re: JSON Report API missmatch V14 - V17
« Reply #2 on: February 12, 2018, 11:42:58 »
Hi, thanks for quick response.

1. API Call: curl -X GET -H "Content-Type: application/json" --user "username:password" "https://exmaple.com:443/queuemetrics/QmRealtime/jsonStatsApi.do?queues=x1|x2|x3&block=RealtimeDO.RTRiassunto"

2. API Call: curl -X GET -H "Content-Type: application/json" --user "username:password" "https://example.com:443/queuemetrics/QmRealtime/jsonStatsApi.do?queues=x1|x2|x3&block=RealtimeDO.RTAgentsLoggedIn"

These API calls in question. Sorry forgot to include in my question.

mirkox

  • Full Member
  • ***
  • Posts: 231
  • Karma: 4
    • View Profile
Re: JSON Report API missmatch V14 - V17
« Reply #3 on: February 13, 2018, 10:03:16 »
Hi NereliZ,

does setting the following in the configuration help?

realtime.members_only=true
realtime.all_subqueues=true

NereliZ

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
    • View Profile
Re: JSON Report API missmatch V14 - V17
« Reply #4 on: February 13, 2018, 12:44:03 »
Hi,

That did helped. I was going round and round via configs it was bit confusing as they all mainly for the panel and these to not mention API. Anyway big part of the problem solved. But it still return onqueue differently form older version. Just populate field with search query.

Thanks,
Nerijus Barauskas

mirkox

  • Full Member
  • ***
  • Posts: 231
  • Karma: 4
    • View Profile
Re: JSON Report API missmatch V14 - V17
« Reply #5 on: February 13, 2018, 14:27:17 »
Which kind of difference there are? Do you have a sample response from both version?

Anyway yes, it's possible that the table changed over time