Display additional histograms in the web UI

If are using a hosted version of coronerd, please reach out to us to display additional histograms in the web UI. If you are using an on-premise version of coronerd, you'll need to complete the following steps to display additional histograms in the web UI:

  • Open /etc/coronerd/coronerd.conf on the coronerd machine.
  • In this configuration file, find the http-console object. In the http-console object, find the columnsobject.
"http-console" : {
    "columns" : {
        "expand" : [
            "hostname",
            "application",
            "version",
            "dc"
        ],

        "list" : [
            "application",
            "version",
            "dc"
        ]
    },
}
  • There are two JSON arrays named expand and list in the columns object.Elements in the list array are displayed on the project page. It is recommended that you add any histogram you'd like to search for across error groups to this array.Elements in the expand array are displayed in the group page It is recommend you add any histograms you'd like to view on a per-error basis to this array.
  • After updating the configuration, restart the console:
$ /etc/init.d/coronerd restart

You will now see the histograms you added on the relevant pages.

Disable SSL

By default, coronerd is configured to encrypt traffic. If you are using a hosted version of coronerd, please reach out to us to disable SSL. If you wish to turn this off on an on-premise version of coronerd, complete the following steps:

  • Remove any relevant ssl sections within /etc/coronerd/coronerd.conf. You'll find ssl objects in the JSON objects:console -- The configuration console.The read object within the listener object. -- The interface used to pull down snapshots.The write object within the listener object. -- The interface used to submit snapshots.http-console -- The web interface.
{
    "console" : {
        "path" : "/var/run/coronerd/coronerd.socket",
        "bind" : {
            "hostname" : "0.0.0.0",
            "service" : "9040"
        },
        "backlog" : 16,
        "ssl" : {
            "certificate_chain_file" : "/etc/coronerd/ssl/chain.pem",
            "key" : "/etc/coronerd/ssl/key.pem"
        }
    },
    "listener" : {
        "write" : {
            "http_bind" : [
                {
                    "hostname" : "0.0.0.0",
                    "service" : "6097",
                    "concurrency" : 2000
                }
            ],
            "https_bind" : [
                {
                    "hostname" : "0.0.0.0",
                    "service" : "6098",
                    "concurrency" : 2000
                }
            ],
            "threads" : 1,
            "ssl" : {
                "certificate_chain_file" : "/etc/coronerd/ssl/chain.pem",
                "key" : "/etc/coronerd/ssl/key.pem"
            }
        },
        "read" : {          
            "bind" : [
                {
                    "hostname" : "0.0.0.0",
                    "service" : "4097"
                }
            ],
            "threads" : 1,          
            "ssl" : {
                "certificate_chain_file" : "/etc/coronerd/ssl/chain.pem",
                "key" : "/etc/coronerd/ssl/key.pem"
            }
        },
        "http-console" : {
            "bind" : [
                {
                    "hostname" : "0.0.0.0",
                    "service" : "443",
                    "concurrency" : 1000
                }
            ],
            "columns" : {
        //...
            },
            "threads" : 1,
            "ssl" : {
                "certificate_chain_file" : "/etc/coronerd/ssl/chain.pem",
                "key" : "/etc/coronerd/ssl/key.pem"
            }
        }
    }
}

  • Restart coronerd after every configuration change.
/etc/init.d/coronerd restart

When configuring coroner client, configure the [universe] section as shown in: Client Install Configuration | Unsecured Communications

Did this answer your question?