Save data to db? multi-node support? about swagger-stats HOT 5 CLOSED

Thank you, @ofeka !

You are absolutely right, and yes, I am currently working on addressing this. My plan is to add the following:

1. Expose Prometheus metrics
   This would enable using Prometheus to collect metrics from multiple app nodes, storing them in Prometheus db, and then aggregate and query over time, and set up alerts. And using Grafana to visualize, set up dashboards.
   This is well underway - latest code already provides metrics via /swagger-stats/metrics API endpoint.
   so I expect this to be included it in the next npm release shortly.
   Tracking in #9

2. Support storing detailed record about each request / response in Elasticsearch.
   The data you can currently see in last errors details, or longest request details, will be stored in Elasticsearch, one document per each request/response, including hostname/node name. With this, it would be possible to use Elasticsearch to aggregate and analyze API usage across app nodes and over time with great level of details, and use Kibana to visualize.

Overall, my thinking is to address all of these 3 levels of monitoring:

1. Out-of-the box telemetry - enabling swagger-stats allows to start monitoring on individual nodes right away, with no infrastructure requirements.
2. Prometheus metrics and Grafana dashboards - enables monitoring and alerting over time and over multiple nodes / microservices
3. Storing API request/response records in Elasticearch - enables detailed analytics on API telemetry

Would appreciate your feedback !

from swagger-stats.

All this sounds really great, couldn't agree more.

from swagger-stats.

this will be addressed by:
#9
#12

from swagger-stats.

#12 addressed in v0.95.0

from swagger-stats.

good

from swagger-stats.