This message was deleted.
# generals
sparse-intern-71089
03/05/2020, 8:15 PMThis message was deleted.
e
early-intern-90238
03/05/2020, 8:23 PMI have logging, monitoring and metrics pretty extensively. It's still super annoying to troubleshoot. For instance one of the micros couldn't communicate to the other in certain situations, I had three instances running with a loadbalancer in between right (kubernetes). First to troubleshoot you need to figure which service is having the issue, then which instance, then when and how, then replicating is nearly impossible as you can't control which instance is hit, etc.
early-intern-90238
03/05/2020, 8:25 PMI find it massively easier to troubleshoot a more consolidated system. Also things seem to be a lot faster and more stable since I consolidated. I guess I'm not bought into the microservice thing entirely....
g
great-accountant-75189
03/05/2020, 9:28 PMdo you have tracing?
great-accountant-75189
03/05/2020, 9:28 PMI couldn’t live without jaeger tracing tbh
great-accountant-75189
03/05/2020, 9:28 PMand I have over 50 microservices heh
great-accountant-75189
03/05/2020, 9:29 PMmay be something to look into!
e
early-intern-90238
03/06/2020, 1:28 AMNot using anything like Istio, but I do plan to get Istio installed at some point so we can see flow
early-intern-90238
03/06/2020, 1:29 AMWhat transport mechanism are you using? I am using TCP and it seems very unreliable. I was considering GRPC, or some sort of Queue System like RabbitMq
g
great-accountant-75189
03/06/2020, 2:42 AMrabbitmq