Remove deprecated /events endpoint from swagger and close/delete traffic-bz events

[clezag]

in reference to noi-techpark/opendatahub-collectors#38

The timeseries /events endpoint is slated for removal.
The only open dataset on the events endpoint is traffic-bz, which is not provided via the content API.
This dataset in timeseries is obsolete, and was never fully completed and advertised for production use.
(The other one is A22, which is closed)

• Check the logs to confirm (non) usage
• Close dataset of traffic events
• mark swagger /events as deprecated or remove completely if nobody uses it

[haasham1]

hi @clezag , Can I work on this?

[haasham1]

hi @clezag , Can I work on this?

I have requested a pull request.
I will appreciate your review.

[sseppi]

@clezag I was reviewing the issues in the Backlog, what do you think to remove the events from the swagger and close this issue in the next sprint?

[clezag]

@sseppi I don't remember if we communicated the deprecation officially, it's been deprecated in the swagger only since April.
In theory, though, the only 2 datasets ever available where either closed (A22) or broken (province-bz)

I'll have a look at the logs if there is notable traffic on these endpoints still

[clezag]

@sseppi I've checked the logs, and I see 3 interesting user agents:
truckmap/1.0 (+incidents) (coud be https://truckmap.com)
sinuous-moto-api-road-events/1.0 (could be https://sinuousmoto.com)
odh-cli/0.2 seems to be this project: https://github.com/galjos/odh-cli

It might be worth it to contact these 3 and point them at the content API announcements that have replaced this endpoint.

otherwise there are a few curl and browser request that we can't associate to any user or company.

Strangely there was practically zero usage (1 req/d) until beginning of june 26, when suddenly truckmap and sinuous started requesting data (800 req/d).
Maybe this is related to documentation or something we published and some AI agents picked it up.

[sseppi]

@clezag thank you for checking. I kindly ask you to ask our customer care team, to notify this three agents that the Traffing Annoucements has been migrated to the content API.

Maybe in the meintime we can start with the brownouts.