| Dara Hayes Looking at https://github.com/aerogear/aerogear-metrics-api, it seems like a good starting point. Few things:
- not sure about the name aerogear-metrics-api as it doesn't make it sound like a server, or capture that its about app metrics. Lets discuss on mail thread/irc. I'll follow up.
- Could be add a Jenkinsfile as part of project setup? The mobile-cli one could be a good reference https://github.com/aerogear/mobile-cli
- I think we might be missing some logging (or maybe its just a log level setting I need?). When I curl the 'default-metrics' endpoint, I get a 500. However, there is nothing in the response or server logs that indicates what went wrong. We can hash this out on thread/irc as well or on a call.
- Is 'default-metrics' a good name for the endpiont? If it's to be used for all 'system' metrics that we define, then just /metrics might be better. If there's going to be different endpoints, then we should name them accordingly. 'default-metrics' doesn't really mean anything. It's whatever we decided were the default
|