Attacks view
Attacks is the Panel screen for events Templass recorded against your protected service. Open it during an incident and when you review the last week.
URL: panel.templass.com
What you should see
When an event is recorded, Attacks is the place to learn:
- That Templass treated the traffic as an attack worth storing
- Timing (start, and end if the event has finished)
- High-level volume or vector information if Panel shows it for your account
If a field is missing, it is not published for your service yet. Do not infer a fake PPS number or a named botnet.
Empty Attacks
An empty list can mean:
- You are not under attack, and nothing recent was stored
- The service is not provisioned, so there is nothing to record
- The attack is hitting an IP that is not the Templass-protected prefix
Empty Attacks plus a down service is a routing or DNS problem more often than a "mitigation off" problem. See Routing expectations and Under attack.
During a live event
- Leave Attacks open. Note the start time in UTC.
- Compare with Dashboard.
- Only then consider firewall or rate limiting.
- If the origin is down and Attacks is also empty, say that clearly in Discord.
After an event
Use Attacks to confirm the event ended before you blame the application. If Attacks is quiet and users still fail, debug the origin (process, disk, application limits).
Templass staff may ask for a screenshot of Attacks. That is enough. You do not need to invent a PCAP story.