Still no support for PagerDuty Common Event Format (PD-CEF) about pdagent

[nekodojo]

We have tried the suggestion of switching to go-pdagent but it has other bugs and we gave up after many days of effort trying to make it work for our situation.

PagerDuty team needs to pick one of these agents to support. Both projects have open bugs for multiple years now. In the official PagerDuty documentation, pdagent (python) is the official recommended agent and go-pdagent is still "beta" and not showing in PD docs as a recommended/supported option. It is OK to support both, and it's OK to support one if that's the official recommended one. it's not OK to stop supporting both.

From #127

After yet another log delay here, we have added this support into our new agent: PagerDuty/go-pdagent.
@aaron-goulet-bfg @apollo13 any chance you all could have a look at this and see if it meets your needs?

Copying my comments from #127 after it was closed

Since this got closed 3 years ago, should we assume that "go-pdagent" is the better agent and this older pdagent will stop getting updates?

I can see on Pagerduty Developer site that pdagent is still listed as the "official" agent, but a footnote says "go-pdagent *This project originated inside of PagerDuty with the eventual goal of replacing the Python based pdagent."

So what are the next steps by PD dev team to promote go-pdagent and retire Python based pdagent? Is this still the plan?

User @NargiT wrote:

go-pdagent is still in beta and does not support all event api v2 fields (PagerDuty/go-pdagent#34)

Good point... I'm hesitant to switch over to go-pdagent since it looks like it has open issues for 2+ years that aren't getting worked on. At least it supports some PD-CEF fields but I guess not all of them?

Anyway, my concern is that PD team is closing bugs against the older pdagent with comments pointing to the new one, but the new one is also not getting any love.