server {
  listen 80;
  server_name logging.*;

  location / {
    proxy_pass http://logging.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 443;
  server_name errbit.*;

  location / {
    proxy_pass https://exception-handler-1.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 80;
  server_name monitoring.*;

  location / {
    proxy_pass http://monitoring.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 443;
  server_name monitoring.* nagios.* ganglia.* graphite.*;

  location / {
    proxy_pass https://monitoring.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 80;
  server_name logging.*;

  location / {
    proxy_pass http://logging.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 443;
  server_name errbit.*;

  location / {
    proxy_pass https://exception-handler-1.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 80;
  server_name monitoring.*;

  location / {
    proxy_pass http://monitoring.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 443;
  server_name monitoring.* nagios.* ganglia.*;

  location / {
    proxy_pass https://monitoring.management.production/;
    proxy_set_header Host $http_host;
  }
}

server {
  listen 443;
  server_name graphite.*;

  location / {
    proxy_pass https://monitoring.management.production/;
    proxy_set_header Host $http_host;

    add_header "Access-Control-Allow-Origin" "*";
    add_header "Access-Control-Allow-Methods" "GET, OPTIONS";
    add_header "Access-Control-Allow-Headers" "origin, authorization, accept";
  }
}

Allow CORS requests to graphite
Allow CORS requests to graphite

Many JS-based dashboards need to be able to make cross-origin requests to the
Graphite API endpoints. These CORS headers allow that to happen.
