Dashboards for call centers (was: JSON output of /scheduler/on_call)

[jasonwinget]

Triggered either through Accept: Application/JSON HTTP header or through ?output=json provide data in a parsable format.

[jasonwinget]

Currently, Minnesota is parsing the HTML output of the page, this leads to errors when application updates are made. There are also some malformed tag pairs that make automated client-side parsing difficult. In today's modern DevOps world JSON output would be nice to have.

[frankduncan]

After talking with @OhMcGoo, this may change to actually having dcsops display the page that you are collecting the data for, meaning you no longer have to take care of this problem at all. If that turns out to be too large of a change, we'll fall back on the json data.

Do you script getting it, or do you log into dcsops and then save page?

[jasonwinget]

Currently using CURL to pull page and then process it into an HTML table.

…

On Mon, Jul 20, 2020, 6:31 PM Frank Duncan ***@***.***> wrote: After talking with @OhMcGoo <https://github.com/OhMcGoo>, this may change to actually having dcsops display the page that you are collecting the data for, meaning you no longer have to take care of this problem at all. If that turns out to be too large of a change, we'll fall back on the json data. Do you script getting it, or do you log into dcsops and then save page? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#257 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA32RUFT42KEUM3PJEQQ5BLR4THU5ANCNFSM4O6D3FZA> .

[frankduncan]

How do you log in?

[jasonwinget]

I was using the SSO cookie in the headers, copied from another browser session.

…

On Tue, Jul 21, 2020 at 6:05 PM Frank Duncan ***@***.***> wrote: How do you log in? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#257 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA32RUEG74GR4ZRRJOKY6MDR4YNNFANCNFSM4O6D3FZA> .

[kfogel]

Summarizing and providing some backstory hitherto unrepresented in this ticket:

Jason currently hosts (on his own server) a page that a third-party call center uses to reach the current on-call people. The way he populates this self-hosted page is by copying the SSO cookie into a script that uses curl to pull down the on_call HTML, parse it, and then generate his page. He's asked to refresh his page every so often.

It would be great if DCSOps could just provide that third-party-oriented on-call page directly. Then Jason could get out of the business of maintaining a self-hosted page that's generated from a script that does its best to parse DCSOps HTML pages that weren't ever meant to be parsed.

Thus, merely changing the source that his script parses to be JSON instead of HTML is probably not the real solution here. Instead, let's just have DCSOps itself generate the page those call centers need. (Now, if they want JSON, because they want the freedom that comes with a parseable format, that's fine -- we can do that. But that doesn't seem to be the solution actually called for here, given the full context.)

[kfogel]

Issue #301 now notes how it would be good to tackle that issue and this one at the same time, for efficiency.