Skip to main content

Flux Administration and Logs

In the following

  • {org} is the name of your Arraylake organization
  • {repo} is the name of the Repo
  • {branch|commit|tag} is the branch, commit, or tag within the Repo to use to fulfill the request
  • {path/to/group} is the path to group within the Repo that contains an xarray Dataset
  • {protocol} is one of the supported protocols (e.g. edr, wms, dap).

Services​

services are activated at an organization level, not per repo. To manage what services are active, whether or not they are public, and to view logs navigate to https://app.earthmover.io/{org}/settings/services. No services are enabled automatically; they must be explicitly turned on before use.

You can also manage services via the arraylake command line client.

Service Status

al compute list {org}

Enable or Disable a Service

By default the service is only accessible to those with access to the Repo being queried. Provide the --is-public flag to open access to all users without authentication. For more information, see the Authentication page.

al compute enable {org} {protocol}

To disable choose the appropriate service_name from the output of al compute list {org}.

al compute disable {org} {service_name}

Services can either be open to the public (as in earthmover-public which is used in all the examples) or private, in which case they will require Authentication to access.

Logs​

Running flux services generate logs. These can be viewed in the web app or via the CLI. You can use the logs to analyse usage or help debug problems.

In the web app​

To view the flux logs in the web app, navigate to the Organization Settings page, then the Services tab. Then click the Logs button next to the service whose logs you want to see.

Button to view flux logs

Button to view Flux logs.

This should show some logs:

Example logs from a Flux Service

Example logs from a Flux Service.

You can view the latest logs, view specific time windows, or follow live logs as they appear.

CLI​

You can also view flux logs via the arraylake CLI:

al compute logs {org} {service_name}

For example

al compute logs earthmover-demos edr-b413972a
✓ Getting service logs for edr-b413972a...succeeded
2025-08-21T08:12:30.157419663Z | [INFO] 10.0.9.176:39080 - "GET
/v1/services/edr/earthmover-demos/dyanmical-gfs-analysis/main/edr/position?coords=POINT(5.669308322197139%2051.913490501057254)&time=2015-05-01T0
0:00:00/2015-06-01T00:00:00&f=cf_covjson&parameter-name=temperature_2m&f=cf_covjson HTTP/1.1" 200
2025-08-21T08:12:52.354997634Z | [INFO] 10.0.9.176:47256 - "GET
/v1/services/edr/earthmover-demos/dyanmical-gfs-analysis/main/edr/position?coords=POINT(86.70079407664105%2029.937047793387052)&time=2015-05-01T0
0:00:00/2015-06-01T00:00:00&f=cf_covjson&parameter-name=temperature_2m&f=cf_covjson HTTP/1.1" 200
2025-08-21T08:13:59.142135Z | [INFO] 10.0.66.178:39184 - "GET
/v1/services/edr/earthmover-demos/dyanmical-gfs-analysis/main/edr/position?coords=POINT(-1.3354108407841068%207.489843848990361)&time=2015-05-01T
00:00:00/2015-06-01T00:00:00&f=cf_covjson&parameter-name=temperature_2m&f=cf_covjson HTTP/1.1" 200
2025-08-21T08:14:00.029393771Z | [INFO] 10.0.66.178:47754 - "GET
/v1/services/edr/earthmover-demos/dyanmical-gfs-analysis/main/edr/position?coords=POINT(13.760277782786034%201.1747459774573912)&time=2015-05-01T
00:00:00/2015-06-01T00:00:00&f=cf_covjson&parameter-name=temperature_2m&f=cf_covjson HTTP/1.1" 200
2025-08-21T08:14:06.567584468Z | [INFO] 10.0.66.178:47762 - "GET
/v1/services/edr/earthmover-demos/dyanmical-gfs-analysis/main/edr/position?coords=POINT(-43.272690538306165%2065.3366654982585)&time=2015-05-01T0
0:00:00/2015-06-01T00:00:00&f=cf_covjson&parameter-name=temperature_2m&f=cf_covjson HTTP/1.1" 200

Various CLI flags allow you to follow logs as they appear (--follow), fetch only the most recent lines of logs (--tail), or fetch only logs between certain times (--since and --until). See all the available CLI flags with arraylake compute logs --help.