New CycleOps Features
Improved Canister Organization and Searchability
Say you’re an IC dev that’s been around the block. This isn’t your first rodeo, and you have tens of canisters you’ve spun up since Genesis 
Managing cycles for your canisters is a painful manual process 
, and you got so many that you need a way to organize your canisters 
and interpret their data 
.
Introducing CycleOps Projects and Canister Tags
-
Canister Projects
allow developers to organize and analyze groupings of canisters belong to a specific project or use case -
Canister tags
provide a secondary level of organization when searching through all the canisters you’ve deployed. Is it a frontend canister or backend canister? Ledger or Asset canister? Was the canister written in Motoko, Rust 
, or Azle?
To top it all off, now when you search by a canister project or tag, your canister overview stats update, allowing you to view just how many cycles that sub-grouping has been burning. 
Canister Memory Thresholds and Alerts
Worried about a spike in storage costs or pre-defined canister memory limits? 
CycleOps now provides memory notifications with per-canister alerting thresholds 
, allowing you to get notified via email 
long before memory becomes a problem 
What’s next?
January has been a busy month for the CycleOps team, but we’re not slowing down anytime soon.
Have a canister management or DevOps feature you’d like us to add to our roadmap? Reach out to us on Twitter or OpenChat!