Nocentry FAQ - Monitoring, Alerts, Incidents and Plans
Practical answers to common questions about deploying and operating Nocentry in production.
How fast can we launch Nocentry?
Most teams can launch initial production checks the same day. A typical start path is: add critical services, set alert contacts, validate notification flow, then tune thresholds in the first operating week.
What monitor types are supported?
Nocentry supports HTTP, API, Content, Ping, TCP, DNS, SSL expiration and Domain expiration monitoring in one operational model.
Can API checks validate response content, not only status code?
Yes. API monitoring supports JSON field checks via json_path, expected values and comparison operators,
so business-level failures can be detected even when transport is reachable.
How do alerts and incidents work?
Failed checks create active incidents, recovery checks resolve them, and notifications are routed through configured alert contacts based on selected event types.
Can we route different incident events to different owners?
Yes. Alert contacts can be configured by event type, including down, up, SSL expiration and domain expiration events.
How can we reduce noisy alerts?
- Use realistic timeout and interval settings
- Set per-service notification delay and repeat interval
- Validate payload conditions for critical APIs
- Test notification routes before full rollout
What are the main timing limits for checks?
Check intervals start at 30 seconds and timeout can be configured from 1 to 300 seconds, subject to plan restrictions.
Can plans and monitoring scope scale over time?
Yes. Teams can expand monitored services, refine check policies and upgrade plans as reliability requirements and system complexity grow.
Does Nocentry support incident analysis and reporting?
Yes. Incident timelines, status history and response-time/availability trends provide context for post-incident review and reliability planning.
How do we contact support or onboarding?
Email support@nocentry.com for onboarding, migration and support requests. Include service scope and urgency for faster triage.