Configuring Subsystem Connectors

Haystack UI can be configured to use one or more connectors, each providing user interface for one subsystem in Haystack. Based on what subsystems you have available in your haystack cluster, you can configure corresponding connectors(and remove others from connectors object) and UI will adapt to show interfaces only for the configured subsystems.

List of subsystems and corresponding connectors options for them could be found in base.config. Please note that only one connector option can be enabled for a subsystem at a time. Also, traces subsystem is mandatory, all other subsystems are optional.

Using haystack-ui as replacement for Zipkin UI

There is a bridge connector for Zipkin traces. If you have an existing zipkin cluster, you can use haystack UI as a drop-in replacement for Zipkin's UI. Typically, you would only have traces connector specified and other removed, as Zipkin doesn't have direct support for trends, alerts etc. Here is a sample connector config -

connectors: {
        traces: {
            connectorName: 'zipkin',
            zipkinUrl: 'http://zipkin.example/api/v2'
        }