Monitoring Microservices with Synthetic Transactions in Go
labs.unacast.com
Monitoring Microservices with Synthetic Transactions in Go
1–10 of 22 posts
Re: Monitoring Microservices with Synthetic Transactions in Go
#2Why does the author use double ticks? As far as I know you use only one.
ID string ``json:"id"``Re: Monitoring Microservices with Synthetic Transactions in Go
#3Why does the author use double ticks? As far as I know you use only one. ID string ``json:"id"``
That is an error and would not compile.
This code example has not gone through gofmt or been compiled... it is pseudo-Go
Re: Monitoring Microservices with Synthetic Transactions in Go
#4Why does the author use double ticks? As far as I know you use only one. ID string ``json:"id"``
Well, that is a typo. I'll fix it =) Thank you!
Re: Monitoring Microservices with Synthetic Transactions in Go
#5Re: Monitoring Microservices with Synthetic Transactions in Go
#6Re: Monitoring Microservices with Synthetic Transactions in Go
#7Earlier quoted context omitted.
Well, that is a typo. I'll fix it =) Thank you!
You should definitely run go fmt, at the moment it's rather difficult to read the examples.
I had to anonymize the code a bit and it seems like I messed up doing so in the gist. I am sorry! I will unsure to run it through gofmt the next time. Thank you for the feedback!
Re: Monitoring Microservices with Synthetic Transactions in Go
#8Re: Monitoring Microservices with Synthetic Transactions in Go
#9I wasn't familiar with "synthetic transactions" until I read this post--great write up! Synthetic transactions are kind of like TDD on a live system (really loose analogy). It's a cool concept for keeping microservices consistent and bug-free by verifying responses return data that are expected.
Re: Monitoring Microservices with Synthetic Transactions in Go
#10Note that this approach isn't just useful for microservices - it's a great way to monitor any complex system, even if it's a monolith.