Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pick up monitoring tool, Elasticsearch/Kibana or Grafana/Prometheus #24

Open
Tracked by #20
ilan-pinto opened this issue Aug 18, 2021 · 1 comment
Open
Tracked by #20
Assignees
Labels
Monitoring type: feature New feature or request
Milestone

Comments

@ilan-pinto
Copy link
Collaborator

ilan-pinto commented Aug 18, 2021

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:

  • already in use for kogito

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

@ilan-pinto ilan-pinto self-assigned this Aug 18, 2021
@ilan-pinto ilan-pinto added this to the Mercury - v1 milestone Aug 18, 2021
@ilan-pinto 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 ruromero changed the title pick up monitoring took, Elasticsearch or grafana/Prometheus Pick up monitoring tool, Elasticsearch/Kibana or Grafana/Prometheus Aug 18, 2021
@ilan-pinto ilan-pinto added type: feature New feature or request Monitoring labels Feb 21, 2022
@b-around
Copy link

b-around commented Mar 7, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Monitoring type: feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants