This TICK stack provides a robust and scalable monitoring architecture. These probes traverse through FactSet Managed Firewalls, NAT Gateways, and Internet Gateways (IGWs), making sure of internet connectivity and performance.įactSet relies on the TICK (Telegraf, Influx DB, Capacitor, and Kibana) stack for its network monitoring solution. Internet – Instances initiate a variety of ICMP, HTTP, and DNS probes to assess reachability to the internet from each AWS Region.These flows traverse through AWS Direct Connect Gateways, Transit Gateways, and Direct Connect Virtual Interfaces (VIFs), recording the health of the overall network. Hybrid-Cloud – Telegraf initiates ICMP, HTTP, and DNS probes for various targets outside of the Region.These flows traverse through Transit Gateway inter-Region peering connections and indicate the network health between Regions. Inter-Region – Telegraf initiates ICMP Probes to measure the response time and packet loss targeting instances across other AWS Regions. These flows traverse through Transit Gateway and provide an indication of network health across the Transit Gateway. Inter-VPC – Telegraf initiates ICMP Probes to measure the response time and packet loss to instances in the Shared Service environment of the same AWS Region.Inter-AZ – Telegraf initiates ICMP probes to measure the response time and packet between EC2 instances running in different AZs.These are some common probes/flows that are used across all environments: Telegraf server monitors network health by initiating and responding to probes. This solution provides consistent and unified monitoring that can be deployed to all locations while also providing intra/inter-VPC visibility on AWS. These probes enable FactSet to monitor response times and packet loss, making sure of the robustness of their network infrastructure.Īlong with Telegraf, FactSet uses native AWS network monitoring provided by Amazon CloudWatch and the various capabilities of Network Manager for visibility into AWS’s global infrastructure. By deploying agents in all operating infrastructure locations, FactSet can monitor network health within each AWS Region and AZ. They deployed the Telegraf server agents on Amazon Elastic Compute Cloud (Amazon EC2) instances across AWS Regions, Availability Zones (AZ), and data centers to collect network health metrics through ICMP, HTTP, and DNS probes. The same environment segmentation translates into AWS Transit Gateway Routing domains, with each domain having its own unique routing and propagation policy.įactSet opted for a combination of native AWS network monitoring capabilities and Telegraf, an open source server agent. There is also a distinct network segmentation across Development, UAT, Production, and Shared Services environments. Network Engineering provisions VPCs and builds connectivity between VPCs and various other FactSet premises. We show this in the following diagram (figure 1).įigure 1: FactSet network and Telegraf agent architecture Across AWS, FactSet uses shared VPC topology, where different AWS Accounts share the same VPC(s) in an AWS Organizational Unit (OU). Solution overviewįactSet had to make sure of optimal network latency and support the high transactional nature of their applications. This post explores how FactSet tackled this challenge by implementing a distributed infrastructure-agnostic monitoring system, providing valuable insights into network performance across their diverse premises. Network Engineering at FactSet is responsible for building connectivity across all these locations and achieving optimal latency between them. The rapid expansion of FactSet’s hybrid-cloud infrastructure, consisting of AWS, US-based data centers, and global Points of Presence (PoPs), necessitated an efficient and comprehensive network monitoring solution. At FactSet, we are always working to make our product more valuable to our customers.” Introduction These solutions provide instant access to financial data and analytics that investors use to make crucial decisions. In Factset’s own words, “FactSet creates flexible, open data and software solutions for tens of thousands of investment professionals around the world. This is a post by FactSet, Sreekanth Sarma Vanam – Director of Network Engineering, Saurabh Gadi – Principal Systems Engineer and AWS Solutions Architects, Mony Kiem and Amit Borulkar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |