(I'd love to know more for some use cases in PF I'm exploring)

But if you hit the /metrics endpoint there is data there you could pull daily into e.g. splunk/sumo and visualise

But would also be good if we were given enough info to try and catch bad habits early. Like if there are problem providers (for bi-directional etc) who just keep trying to publish breaking changes. So we could investigate why and if they aren't following api evolution from the start (or something similar). If they constantly run into contract verification failures when trying to deploy it could slow down development as they need to go back to redesign/implement/test etc

I guess that would need finer detail than existing metrics as it's currently all grouped under "verificationResults", if you could pull them by team or by pacticipant that could be interesting

Also if you could distinguish integrations by type (CDCT or BDCT)

Yes we've been thinking about a lot of these at various levels (e.g. at the account, team, integration and app level)

Trying to work out what exactly will be helpful in providing actionable feedback. E.g. as you say, if there are broken integrations can we infer if that's a problem, or if it's because the feature is in development (i.e. TDD for APIs).

Broken webhooks might be useful for admins to keep up maintenance Particularly interested in who is interested in seeing the data and who might end up being on the receiving end of any insights (.e.g Devs, testers, management etc) and why it's important they get it. We do get asked a bit about reporting, but ideally we don't just share vanity metrics that look good but aren't actually very useful. I think seeing trendline activity is helpful, because you can get a sense if teams are increasing, maintaining or decreasing their investment in the tool

I'll share some more thoughts when I get back to my desk