You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as part of mercury bootstrap solution. we would like to provide an enterprise-level business data monitoring tool.
this service will assist end 2 end Domain analysis.
based on our previous knowledge two monitoring stacks Elasticsearch/Kibana or Grafana/Prometheus were selected
both have OpenShift Operators.
ilan-pinto
changed the title
pick up monitoring took, Elasticsearch or grafana/Prometheus - @ilan-pinto
pick up monitoring took, Elasticsearch or grafana/Prometheus
Aug 18, 2021
ruromero
changed the title
pick up monitoring took, Elasticsearch or grafana/Prometheus
Pick up monitoring tool, Elasticsearch/Kibana or Grafana/Prometheus
Aug 18, 2021
Would be great to start with something simple, for example, a logging framework that would allow generate:
| < date time > | < service parent domain > | < name of service generating the data > | < entity associated to the metric (client, branch, etc) > | < metric name > | < value >
This would allow using tools like grafana to grab that data and put on a dashboard, allowing real time business insights like $$ of transactions processed via ATM or card network
We may just need to think whether specifically having a client ID (even if transformed to UUID) is a good idea given GDPR regulations.
Background
as part of mercury bootstrap solution. we would like to provide an enterprise-level business data monitoring tool.
this service will assist end 2 end Domain analysis.
based on our previous knowledge two monitoring stacks Elasticsearch/Kibana or Grafana/Prometheus were selected
both have OpenShift Operators.
Grafana/Prometheus
pros:
cons:
links
https://logz.io/blog/grafana-vs-kibana/
https://www.elastic.co/blog/introducing-elastic-cloud-on-kubernetes-the-elasticsearch-operator-and-beyond
https://www.youtube.com/watch?v=SpcxTSl68RY
The text was updated successfully, but these errors were encountered: