How to Troubleshoot
Web Console in 7.2
or
Why the F#$k is the Web Team
Changing Stuff that Already Works?
Pre 7.2 Problems
Performance
- primarily a development concern
- driver behind many of the changes
Stability
- too many issues traced back to "bad config"
- startup order of services mattes
- system feels brittle
Troubleshoot-ability
- config bloat
- communication over ZMQ
- poor logging
- poor visibility into overall state of system
So What's New?
Small Stuff
- new directory (...\LogRhythm\LogRhythm Web Services\)
- Web Console split into Web Console UI and Web Console API
- all vendor dependencies are local
- retry loops for dependencies
- no more ZMQ (mostly...)
Big Stuff
- API Gateway
- Procman
- Config Tool
API Gateway
- comprised of the following services:
- API Gateway
- API Gateway Integration
- Cluster Configuration Service (consul)
- does a lot for dev...
- responsible for routing requests to the correct service
- no more IPs and ports in configs! (think smart DNS)
Procman
- not a service
- primary responsibilities:
- starting/stoping service
- service registration with gateway
- config injection
- restart on config change
Config Tool
- single config location (similar to AllConf)
- no more .json/.xml/.env files
- significant reduction in number of configs
Ramifications
- no service talks directly to another service
- ZMQ is dead. Long live HTTP.
- environment variables used for config
All Together Now
Procman
Service Startup and Registration
Service to Service Communication
All The Services
Demo
Are we done changing things?
- more configs will be removed
- API Gateway adoption
- logs will continue to get better
- log aggregation
- system visualizer
- refined HTTP APIs for backing services
Nope.
How to Troubleshoot Web Console in 7.2
By Chris Langager
