Ask for support with a ticket, from Support at the bottom of the console's menu. Email does not open one.
Opening a ticket
Support → New ticket. A ticket belongs to the team you are working in. Anyone on that team can open one, Viewers included.
| Field | |
|---|---|
| Subject | Up to 200 characters |
| Project | Required — which of the team's projects this is about |
| Environment | Optional. It tells us which machine to look at |
| Activity log entry | Optional, once an environment is chosen: one of its 50 latest, such as the deploy that failed or the backup that did not run |
| Priority | Below |
| Affected URL | Optional. Where to see the problem, if it can be seen |
| What happened | Plain text. What you did, what you expected, what you got |
| Attachments | Screenshots: PNG, JPEG, GIF or WebP, up to 2 MB each, five per ticket |
A ticket cannot be edited once it is open. Add anything further as a reply.
Priority
| Priority | Means |
|---|---|
| Low | A question, or something to look at when there is time |
| Normal | Something is wrong but the site is working |
| High | Part of the site is broken, or it is badly degraded |
| Urgent | The site is down or losing data |
You choose the priority, and we do not change it. The response times on your project's support level are measured against Urgent — see Projects.
Replies
Replies are on the ticket, in the console. When we reply, everyone on the team from Developer upwards is emailed, with a link back to it. Replying to that email does not reach us — answer on the ticket.
A Viewer who opened a ticket is not emailed about replies, and should check the ticket itself.
Resolved and closed
Either side can mark a ticket resolved with their last reply. No replies can be added afterwards. If the problem comes back, open a new ticket and mention the old one.
A ticket nobody has replied to for 14 days closes by itself, with a note saying so. If the problem is not solved, open a new ticket.
Changing your email address
Your address is how you sign in, and where invoices, alerts and password resets go. Once it is confirmed, you cannot change it on your account's form. Open a ticket from any of the team's projects and we change it, once we know the request is yours.
Until it is confirmed, just after signing up, you can correct a mistyped one yourself, and a new link goes to it.
Everyone on the team sees every ticket
The Support page lists the team's tickets, open and closed, whoever opened them. Do not put anything in one you would not want the rest of your team to read — a password, for instance.
Tickets we open
The platform opens a ticket for sustained load on an environment. It shows as from Vallic.
| Opened when | |
|---|---|
| CPU | The environment has used at least 60% of its machine's cores for an hour |
| Memory | The environment has used at least 90% of its plan's memory for 30 minutes |
Sustained means every reading in that time was over the line: a spike does not count. Both are opened as High, and a Load notification is sent alongside. The ticket resolves itself once the environment has stayed back under the line for 15 minutes.
Reply on it if you want to talk about the load: a bigger machine, a cache, a query that has started scanning a table. These tickets follow the same 14-day rule as any other, and a new one opens if the load is still there.
Next
- Projects — the support levels and their response times
- Monitoring and metrics — the readings behind a load ticket
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console