Visualize Failing Third Party APIs with Railway's "Observability"
Our service relies on many third party apis, and it is hard for us to keep track of how often the apis get called, how often they succeed and fail - if they fail then with what status code.
I am wondering if Railway's "Observability" can be used to visualize such data, or if someone knows an easy way to visualize something like this.
I would greatly appreciate help, thanks a lot!
Solution:Jump to solution
i think thats a little outside of the wheelhouse of what the observability tab aims to be, what you deserbied is more geared towards a service like data dog where you ship metrics and create metrics and graphs from the data your app sent
7 Replies
Project ID:
03b9d68c-2d80-4600-a0a4-317a53176c9703b9d68c-2d80-4600-a0a4-317a53176c97
Solution
i think thats a little outside of the wheelhouse of what the observability tab aims to be, what you deserbied is more geared towards a service like data dog where you ship metrics and create metrics and graphs from the data your app sent
For us to do that, we would need to ship network logs which is tentatively planned for this quarter, then we can start graphing it π
that would track incoming requests, but from my understanding they wanted to track calls to external apis
Do you by chance know how to get started on implementation something like this in a way where it is not too time intense? I am not even sure how to properly search for it.
follow datadog's docs?