Configuration Files

Archagent comes with four config files automatically fetched and stored in the directory /etc/opt/archsaber/ upon installation.


Contains all the connection parameters & credentials required for collecting metrics for various services. The guide on how to create & assign them can be found on the respective guide of the plugins.


Contains the alert rule name to which your host belongs, and the alert channel name on which alerts will be sent out. Comes with a pre-defined alert rule ("default-rule") and alert channel ("default-channel").

You can use the alert rules page in web app to modify this rule definition or create a new one (similarly for alert channels). Or you can also directly edit this file to assign any rule/channel created from the dashboard (in this case, you will need to restart the agent).


Contains the license key for your organization. Already set to the right key when you run the installer script. No changes required in this file.


Contains APM related configuration. You can choose to override the defaults. dd-server section specifies configuration for receiving traces from dd-trace-* libraries. Reducing the extra-sample-rate can significantly reduce outbound network traffic at the cost of loss of traces.

The processor section specifies configuration for receiving traces from jaeger-client-* libraries. You should not be needing to change rest of the settings.

  "dd-server": {
    "enabled": "True",
    "host-port": "",
    "extra-sample-rate": 1.0
  "collector": {
    "host-port": ""
  "processor": {
    "zipkin-compact": {
      "server-host-port": "localhost:5775"
    "jaeger-compact": {
      "server-host-port": "localhost:6831"
    "jaeger-binary": {
      "server-host-port": "localhost:6832"
  "http-server": {
    "host-port": "localhost:5778"
  "auth": {
    "token-file": "/etc/opt/archsaber/archsaber.token"

results matching ""

    No results matching ""