I have all sorts of metrics I would like to count and later query. For example I have a lambda that processes stuff from a queue, and for each batch I would like to save a count like this:
I would like to dump these pieces somewhere and later have the ability to query how many were processed within a time range.
So these are the options I considered:
1. write the json to the logs, and later have a component (beats?) that processed these logs and send to a timeseries db.
2. in the end of each execution send it directly to a timeseries db (like elasticearch).
What is better in terms of cost / scalability? Are there more options I should consider?
0 comments
—
Ask HN: How to count metrics from executions of AWS lambdas? · HackerTrans
I would like to dump these pieces somewhere and later have the ability to query how many were processed within a time range.
So these are the options I considered: 1. write the json to the logs, and later have a component (beats?) that processed these logs and send to a timeseries db. 2. in the end of each execution send it directly to a timeseries db (like elasticearch).
What is better in terms of cost / scalability? Are there more options I should consider?