PagerDuty Enterprise pricing & rate limits

• PagerDuty’s observability tier pricing remains flat at $41.00/mo per user, contrasting with the usage-based billing seen at Datadog or New Relic.
• The platform supports unlimited log ingestion and unlimited monitored targets, removing the risk of surprise overage invoices when your microservices start logging excessively.
• Retention periods and seat counts are flexible, allowing teams to scale from a single developer to an enterprise-wide deployment without triggering hidden per-host hardware fees.

When you shift from standard on-call alerting to full observability, the primary risk is usually the "log tax" that scales linearly with traffic volume. PagerDuty avoids this by decoupling their pricing from the raw data volume. While most competitors charge $0.10/GB or more for high-cardinality log indexing, the fixed-cost model here allows for aggressive telemetry collection without needing to filter out logs to save budget. You are essentially paying for the seat and the incident response integration rather than the underlying storage footprint.

This structure favors engineering organizations that generate high-volume trace data but lack the time to manually prune logs to stay under monthly budget caps. Because you are not paying for the infrastructure overhead of the backend storage or the underlying compute cycles used to process your metrics, you can retain logs for longer periods than you might on a volume-based provider. This is a practical choice for teams running noisy distributed systems on AWS or GCP where the cost of generating logs is already high enough. It works best for teams that prioritize consistent monthly burn rates over the ability to pay for only the exact bytes ingested.