Nevermore Location serves as the central command environment for monitoring and managing the distributed Nevermore observability platform. This page is designed to help engineers and operators quickly understand where data lives, how services connect, and how to navigate the console efficiently.
Use the structured reference below to locate resources, compare deployment options, and align teams on terminology across regions and accounts.
| Environment | Region | API Endpoint | Documentation URL |
|---|---|---|---|
| Production | us-east-1 | https://api.nevermore.io | https://docs.nevermore.io/production |
| Production | eu-central-1 | https://api.eu.nevermore.io | https://docs.nevermore.io/europe |
| Staging | us-west-2 | https://staging-api.nevermore.io | https://docs.nevermore.io/staging |
| Development | us-east-1 | https://dev-api.nevermore.io | https://docs.nevermore.io/development |
Navigating the Nevermore Console
Organization and Team Access
The console organizes resources by organization, team, and project tags. Use the sidebar to jump between workspaces and filter by environment status. Account roles determine which regions and integrations you can configure, so coordinate with platform owners for elevated permissions.
Observability Pipelines by Region
Data Ingestion Paths
Nevermore Location routes telemetry through regional collectors close to your workloads. Selecting the nearest region reduces latency and helps meet data residency requirements. Each region supports the same feature set, but some third-party integrations may vary by cloud provider availability.
Compliance and Data Residency
Regulatory Considerations
Choose region mappings that align with legal constraints on personally identifiable information and log retention. The table in this article highlights where metadata is stored and which endpoints enforce encryption in transit. Review policy documents for cross-border data transfer rules before enabling replication across regions.
Operational Topology
Service Mesh and Agent Placement
Deploy collectors as sidecars or DaemonSets depending on runtime constraints. Nevermore Location uses service discovery to map dependencies, so accurate namespace labeling is essential for clean service maps. Keep agent versions aligned across clusters to prevent metric gaps during upgrades.
Deployment Roadmap
- Map regulatory constraints to target regions for data residency.
- Select the nearest region for each workload to minimize latency.
- Standardize agent versions and tagging schemes across clusters.
- Validate failover procedures for critical observability pipelines.
- Monitor pricing and usage per region to control budget variance.
FAQ
Reader questions
How do I find the correct API endpoint for my region?
Refer to the region column in the summary table and use the matching API endpoint for production, staging, or development. Hardcoding endpoints is discouraged; prefer environment variables that map to the intended workspace.
Can I move resources between regions after creation?
Some resources can be relocated using export and import workflows, but stateful backends may require snapshots or replication jobs. Always validate data integrity in the target region before decommissioning the source.
What happens during a regional outage?
Failover to a secondary region is supported for production accounts with redundancy enabled. Automated routing depends on health checks, so ensure probes are configured for your critical collectors and dashboards.
Are there cost differences across regions?
Pricing may vary by region due to underlying cloud rates and local data storage requirements. Check the billing section of the documentation for line-item details and consider test projects to benchmark costs before committing workloads.