Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

  • March 2, 2019
Table of Contents

Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

In a Cloud Native world, microservices are running with ephemeral containers that are regularly deployed to multiple availability zones, regions, and even multiple clouds. As these cloud native applications become more complex, our supporting solutions like monitoring, have also had to become more complex. Today, more traditional monitoring responsibilities are being automated, and monitoring has become less human centric.

In the first part of this series, we’ve summarized some of the most popular monitoring solutions with Ambassador. Prometheus can be used for real-time monitoring of Ambassador instances. We’re fans of the Prometheus Operator, which automatically creates and manages Prometheus monitoring instances.

Check out our tutorial on using the Prometheus Operator with Ambassador here: http://www.datawire.io/faster/ambassador-prometheus/. Grafana enables you to view your time series analytics through dashboards. Alex Gervais, an Ambassador community member, maintains a Grafana dashboard for Ambassador. Datadog is a cloud-based monitoring system.

We’ve added a native Datadog integration that allows you to easily export Ambassador stats into the Datadog monitoring system.

Source: getambassador.io

Tags :
Share :
comments powered by Disqus

Related Posts

Ambassador 0.50 GA Release Notes: SNI, New AuthService and Envoy v2 Support

Ambassador 0.50 GA Release Notes: SNI, New AuthService and Envoy v2 Support

Read More
Rate Limiting at the Edge

Rate Limiting at the Edge

I’m sure many of you have heard of the “Death Star Security” model—the hardening of the perimeter, without much attention paid to the inner core—and while this is generally considered bad form in the current cloud native landscape, there is still many things that do need to be implemented at edge in order to provide both operational and business logic support. One of these things is rate limiting. Modern applications and APIs can experience a burst of traffic over a short time period, for both good and bad reasons, but this needs to be managed well if your business model relies upon the successful completion of requests by paying customers.

Read More
Server Name Indication (SNI) Support Now in Ambassador

Server Name Indication (SNI) Support Now in Ambassador

We’ve discussed many interesting use cases for SNI support within the edge proxy/gateway with both open source and commercially supported users of Ambassador. In a nutshell (and with thanks to Wikipedia), SNI is an extension to the TLS protocol which allows a client to indicate which hostname it is attempting to connect to at the start of the TCP handshaking process. This allows the server to present multiple certificates on the same IP address and TCP port number, which in turn enables the serving of multiple secure websites or API services without requiring all those sites to use the same certificate.

Read More