Hi all,
Currently, I wanna install the Observability features on our K8s Infrastructure.
When surveyed about the suitable solutions for that I wonder what is the difference, the pros and cons, use-cases,… of the Elastic Observability Stack and Grafana Stack. What should we choose now?
Finally, when I have to upgrade to enterprise products in the future, what is the Stack more compatible with the current enterprises?
It is opinionated question, so fans of both stack will tell you that their stack is the best.
You are on the Grafana forum, so you may guess, which stack will be winner here 
.
I wouldn’t focus on vendor specific stack (that’s vendor lock-in). I would rather build vendor agnostic base (e.g. OpenTelemetry), so then you can use any vendor specific storage at the end. Then nobody is stopping you to use even their combinations and variations.
1 Like
Yeah, thank you for your reply!
I think there are some people here who had experience with both Stacks and they can leave some objective opinions.
IMHO that’s impossible.
You should make a comparison for some particular use case. Or better is to make POC for that use case.
I would say that trend is to be vendor agnostic, so you can cherry pick the best tools from different vendor for each particular use case. For example fictive use case: you will use Elasticsearch Agent (just because it is already deployed and it wil be expensive/impossible to deployed another agent on thousands manually managed machines), but logs will be stored in Loki. Then you will decide, that you like more vendor X one day, so you will just switch log destination to log storage provided by vendor X. So it is irrelevant if stack A is “better” than stack B, because you can use the best for your case from both eventually. This is applicable for Elasticsearch and Grafana stacks, because both have support for OpenTelemetry. That’s that vendor agnostic piece.
1 Like