Alerts

Marshal tells you when something needs a look: a space left running for days, or a spike in blocked network traffic, or deputy launches waiting on your install’s concurrency limit. The Alerts entry in the left rail shows a count of what you have not read, and the Alerts page lists every alert raised for you. Mark alerts read, dismiss them, mute the kinds you do not want, and choose whether to get them by email.

What you can do with it

• Catch a forgotten space. The owner of a space and your admins hear about it when the space has run longer than your org’s limit, before it costs another day of compute. The alert shows how long the space has run, who owns it and whether it is still up, so you can decide on the spot.
• Spot a traffic spike. Admins see when blocked network requests in one day reach the threshold they set, with the destinations blocked most, then open the Security Center page to see where the traffic went.
• See when deputies hit the ceiling. Admins see when launches are waiting on the install concurrency limit, with a link to the Licensing page to request more capacity.
• Keep your own volume. Mute a kind for yourself, or switch on an email for each new alert or a weekly summary.

Who sees which alert

Each kind of alert has a fixed audience. You only see, count and receive the kinds that are meant for you.

Marshal checks every 15 minutes. An admin who also owns the space gets one alert, not two. If your role changes, your alerts change on your next page load.

The Alerts entry and the page

The Alerts entry in the left rail shows a count of your unread alerts and updates by itself.

Open it to see the page, with two tabs: Alerts and Settings. On Alerts, choose Open to see what is still active or All to include cleared alerts. Newest comes first. Each row shows what happened, when it was raised, a New badge until you read it, and a Cleared badge once the condition has ended.

• Mark read removes the New badge and lowers your count.
• Dismiss takes the alert out of your Open list and your count. It stays under All.

Both apply to you only. Nobody else’s view changes.

Cleared alerts are kept for 90 days, then removed.

Long-running space rows

A long-running row has everything you need to act:

• The space. Its name opens the space, and a small label shows whether it is running, stopping or stopped. If the space has been deleted, the name stays and the link goes away.
• How long it has run. For example, “Running 4d 6h, since Oct 28 09:12 UTC”. The time keeps counting while the page is open.
• Who owns it. The owner’s name and email, or “You” when it is your space. Reach the owner before you stop their work.
• Stop space. If you own the space, or you are an owner or admin of the org, press Stop space and confirm. The space stops the same way it does from the Spaces page, and the row shows its new state. A cleared alert keeps the space link and owner but shows no running time and no Stop space, because the space may have started again since.

Install concurrency rows

This row reads “Deputy launches are waiting on the install concurrency limit” and shows how many are waiting. Choose See licensing and request more capacity to open the Licensing page. See Licensing.

Blocked network access rows

A blocked-access row lists the hosts that were blocked most that day, with the number of blocked requests for each, up to five. Choose Open Security to see the full picture.

Settings

Open the Settings tab to choose how you hear about each kind. You see only the kinds meant for you. Each change saves as you flip the switch.

The A package version your spaces or manifests use was blocked (email) kind is email-only: it has no row on the Alerts tab and none in the table above. Only people who own a space or manifest see its switch. See Security Center.

A long-running alert email, and its line in the weekly digest, names the space owner and links straight to the space, so you can open it from your inbox. The running time in the email is the time at the moment it is sent. Email options are available when email is set up for your organization. When it is not, the page tells you so and the email switches stay off.

Configure it

Org owners and admins set these under Settings > Configuration.

Alerts email is sent through your organization’s own mail provider. Set it up under Settings > Email, where you choose the provider and the default sender.

Try it

Open Alerts in the left rail, choose the Settings tab, and switch on Weekly digest.

What you should see

• A count next to Alerts in the left rail when something is unread.
• On the Alerts tab, the alerts for you, with Mark read and Dismiss on each row. With nothing to report: “No open alerts” and “Nothing needs your attention right now.”
• On the Settings tab, a switch for each kind meant for you, and the Weekly digest switch.

Related

• Spaces and storage
• Licensing
• Admin dashboards