The Grey Matter application is configured with the following environment variables set on the host machine. The term host machine can apply to an AWS EC2 server, Docker container, Kubernetes Pod, etc.
Note: to apply new configs, you must restart the application process on the host machine.
Base URL, relative to the Grey Matter installation's hostname
Default Control API endpoint for retrieving mesh configuration. See note below.
When set to true, disables parts of the UI that use route metrics from Prometheus - service summary view route-level metrics, service routes view entirely, and route SLOs in the service configuration panel.
Enables inline API documentation in service and instance views.
Catalog endpoint (for retrieving metadata of mesh services)
Hide Grey Matter social links in the app footer
Service Level Objectives endpoint (for retrieving and setting performance objectives)
Prometheus endpoint (for retrieving historical service metrics)
Number of milliseconds a request to backend services can take before returning a client error
Path to client trust file (SERVER_SSL_ENABLED=true is required)
Path to client certificate (SERVER_SSL_ENABLED=true is required)
Informs service to receive client connections over SSL only
Path to client private key (SERVER_SSL_ENABLED=true is required)
How many services should be displayed per page in the Fabric View views.
Use Prometheus to query service-level metrics
By default, the application uses the configured CONFIG_SERVER address to connect to the Control API server used for retrieving mesh configurations. However, in multi-mesh deployments, it will be necessary to specify a unique Control API server address and zone_key for retrieving mesh-specific configurations. These may be specified by adding mesh labels to your Catalog mesh configuration.
Need help setting up the Grey Matter application? Create an account at Grey Matter Support to reach our team.