Organize monitors across projects
Monitors live in a project, and a project is the unit you share, filter, and review. Keeping each project to a manageable number of monitors makes them easier to find and to check at a glance.
Choose how many monitors to keep in a project
Aim for about 100 monitors per project. Treat this as guidance, not a limit.
A large deployment, for example 1,000 to 1,500 monitors, works better spread across several projects than kept in one. Group the monitors by something your team uses to find them, such as an API, a team or an environment.
Spread monitors across projects
- Create a project for each group. See Create a new project.
- Move or copy the monitors into the right project. See Copying and moving APImetrics resources between projects. A scheduled monitor must be unscheduled before it can be moved.
- Check each project's monitor count and the group it holds.
Result
Each project holds a group of monitors that your team can find and review together.
Next steps
- Projects and collections: how monitors, projects, and collections relate.
- Monitors: what a monitor is and what it holds.
- Create a new project: the ways to create a project.