• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Frits Walraven
Bartenders:
  • Carey Brown
  • salvin francis
  • Claude Moore

Best monitoring solution for microservices  RSS feed

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

We have around 50 microservices to monitor all these services we have created one application which checks the availability of critical functionalities in this services and if any of the services are down alert will be sent on mail. Problem with this approach too many consumptions of sitescope alert license which are costly. Is their any better solution to monitor microservices?
 
Author
Posts: 6
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Abdul,

I'm not particularly familiar with Sitescope, so can't compare like-for-like.

In your approach:

an application that checks the availability of critical functionalities and if any of the services are down alert will be sent on mail



Are you checking availability i.e. can this function be called by the test application _or_ functionality i.e. making a test/synthetic call to check that functionality actually works?

In general, I'd aim to build three layers of instrumentation in a microservice application:

* Log aggregation i.e. consuming and indexing logs from all microservices (using ELK stack, Splunk, cloud provider log tools, etc).  These allow you to investigate system behaviour, but can also drive dashboards and alerts.
* Time series metrics for dashboards and alerts (using Prometheus and Grafana, or a commercial tool like Datadog or Amazon Cloudwatch, depending on where/how you host).  This data might be emitted from multiple sources e.g. infrastructure, app frameworks, service code...
* Distributed tracing (using Jaeger, OpenTracing, or a commercial option) to understand service interactions


 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This excerpt from the book Production-Ready Microservices, by Susan Fowler, provides a list of useful questions to assess the production-readiness of microservices and a microservice ecosystem. The questions are related to key metrics, logging, dashboards, alerting, and on-call rotations to give you an idea of what kinds of tools and processes you need to have in place to effectively monitor microservices.

Plex Kodi Lucky Patcher
 
The happiness of your life depends upon the quality of your thoughts -Marcus Aurelius ... think about this tiny ad:
Create Edit Print & Convert PDF Using Free API with Java
https://coderanch.com/wiki/703735/Create-Convert-PDF-Free-Spire
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!