oktabeat VS rest

As other users mentioned, Okta System Log API is the main way users implement 3rd party systems if you need to go somewhere custom. The logstash plugin another user linked to also has some Apache 2.0 code if you are looking to build something custom, here's another OSS solution for Elasticsearch if you are using that (https://github.com/forter/oktabeat). Splunk also has an app on Splunkbase though I'll be honest I've never used it.

Swaggest Rest can generate OpenAPI definitions from Go code, but it's not as comprehensive as Goa and does not support gRPC.

This is what I use: https://github.com/swaggest/rest

This has been the best implementation of the use case interactor I’ve seen and it outputs spec 3: https://github.com/swaggest/rest

Other times you might need a JSON REST API to generate OpenAPI docs code-first… for that I’m a fan of Swaggest REST. REST through clean arch.

For full code-first OpenAPI v3 REST, I’ve been using https://github.com/swaggest/rest and I like it.

For anything that needs OpenAPI docs, I’ve honestly found https://github.com/swaggest/rest pretty awesome. It’s basically just doc generation on top of Chi, but it does a lot of stuff right.

I used Echo for a lot of stuff (and it was easy to work with), but recently OpenAPI 3 has been a requirement, so I've switched to https://github.com/swaggest/rest

I've tried go-swagger comments to instrument existing code, but wasn't quite satisfied due to magical nature and error friendliness of those comments. So I decided to implement first-class OpenAPI generation on top of self-documenting action handlers: https://github.com/swaggest/rest/blob/master/_examples/basic/main.go. Schemas are generated from request and response structures using reflection and field tags.