Cisco
snmp-server enable traps
snmp-server host trap.coldstart.io version 2c AUTH_KEYInstant SNMP trap alerting
Polling for alerts doesn’t cut it anymore.
Point your switches, routers and firewalls at ColdStart. Traps arrive parsed, named and enriched — in your chat, your SIEM, your own webhook, or an AI that triages them and acts.
Get a free auth key See device setup
Free to start · standard SNMP · no agents, no proxy
Why ColdStart
-
Rapid
Traps are relayed within a few hundred milliseconds of leaving your kit. Lose connectivity and they queue, then land the moment you are back.
-
Standard SNMP
No agent to install, no proxy to deploy. Configure traps the way you always have, with your auth key as the community string, and point them at us.
-
Open source
The trap relay is open source under the GPLv3. Fork it, audit it, or run the whole thing yourself on your own network.
How it works
Three steps, and the third one is the only one on your kit.
-
Sign up and generate an auth key
Free, and no card. The key identifies you, so it doubles as the SNMP community string your devices already send. Protect it with a password if you want to lock it to your account.
-
Choose where alerts go
A webhook of your own, a chat channel, your SIEM, or hand the stream to the AI and let it decide what deserves waking someone up.
-
Point your devices at us
Send traps to
trap.coldstart.iowith your auth key as the community string. That is the whole integration.
Where your traps can go
Every trap is decoded against real MIBs first, so what arrives is
linkDown on GigabitEthernet0/7 — not
1.3.6.1.6.3.1.1.5.3 and a column of integers.
-
Your own webhook Available
One JSON document per trap, POSTed to any endpoint you control, signed with HMAC-SHA256 so you can prove it came from us. Retries with backoff when your endpoint is having a bad day.
-
Grafana Loki Available
Pushed straight to Loki as structured log lines, labelled by device, trap type and MIB, so a year of trap history is one LogQL query away.
-
Chat and SIEM Planned
Splunk, Slack, Discord, Teams and PagerDuty, formatted the way each one expects rather than as a wall of raw JSON. Pick a destination, paste a URL, done.
-
AI triage and response Planned
Hand the trap stream to our AI. It correlates the flood a failing uplink produces into one incident, tells you what changed, and where you allow it, takes the agentic fix — then shows its working.
Device setup
Replace AUTH_KEY with the key from your dashboard. If your
vendor is not here, any device that speaks SNMPv2c traps will work.
Arista
snmp-server host trap.coldstart.io version 2c AUTH_KEYJuniper
trap-options {
source-address lo0;
}
trap-group "AUTH_KEY" {
version v2;
categories link startup;
targets {
trap.coldstart.io;
}
}Extreme
configure snmp add trapreceiver trap.coldstart.io community AUTH_KEYBrocade Server Iron
snmp-server host trap.coldstart.io AUTH_KEYF5 BIG-IP LTM
modify sys snmp traps add {
coldstart {
host trap.coldstart.io
community AUTH_KEY
version 2c
}
}Start free
Generate an auth key, point one switch at us, and watch the first trap land. Nothing to install and nothing to pay.
Roadmap
What is shipping next, in order.
-
Planned
Free accounts and auth keys
Self-service signup, key issuance and rotation, with each key scoped to one account.
-
Planned
Destination integrations
Splunk, Slack, Discord, Teams and PagerDuty, each with a payload shaped for that product.
-
Planned
AI processing and agentic response
Correlation, plain-English incident summaries, and opt-in automated remediation.