What I wish every Library author would do in the world of API Libraries.
If you are building web services with Node.JS or TypeScript, chances are you have used many community-built API bindings to make 3rd Party API calls. Since these bindings are built by different teams from different backgrounds, their conventions can vary quite a bit.
Below are three things that would drastically improve the usability of an API Library for end users. Library Authors, if you care about gaining more users, please make them happen!
TypeScript is gaining traction and saving developers a lot of headaches in finding type related bugs. When a request to 3rd party API does not specify its input Shape nor its return Shape, it results in developers putting in lots…
tl;dr: Full example code: https://github.com/teamzerolabs/mirth_channel_exporter, read on to see step by step instructions
Exporters are the heart and soul of Prometheus Monitoring Pipelines. If you run into a situation where an exporter does not exist yet, you are encouraged to write your own. We will cover the steps required to make the exporter. No worries, it is quick.
go mod init my_first_exporter
go get github.com/prometheus/client_golang
go get github.com/joho/godotenv …
tl;dr: If you are already familiar with the concept of monitoring and only need the Mirth channel exporter: https://github.com/teamzerolabs/mirth_channel_exporter
Let me know if this matches your story:
You are busy leading a team in implementing new features, company is in the early phase, and cannot spare cycles to check up on Mirth Connect. …