Novus Examples, Real, documented example files for testing

Project Checklist Template (Markdown)

A Markdown checklist template with task-list checkboxes. Opens directly in the in-browser editor.

File: MD · Checklist
Use case: TemplatesEditor testing

Project Proposal (PDF, SAMPLE)

One-page SAMPLE project proposal PDF.

File: PDF · Proposal
Use case: TemplatesPDF editor testing

Project Risk Register (CSV)

A scored delivery-risk register with owners, mitigations, triggers, and review dates. This UTF-8 CSV twin contains the model's single canonical table for parser, import, and round-trip tests.

File: CSV · Planning · 8 rows
Use case: TemplatesConversion testing+1· Conversion set

Project Risk Register (PDF)

A scored delivery-risk register with owners, mitigations, triggers, and review dates. This print-ready PDF twin is designed for page-rendering, extraction, and cross-format comparison tests.

File: PDF · Planning · 8 rows
Use case: TemplatesConversion testing· Conversion set

Preview of Project Risk Register (XLSX) — Actual file preview for Project Risk Register (XLSX)

A scored delivery-risk register with owners, mitigations, triggers, and review dates. This Excel workbook adds filters, frozen headers, print settings, typed cells, and live formulas where the model defines them.

File: XLSX · Planning · 8 rows
Use case: TemplatesConversion testing+1· Conversion set

Project Task List Template (XLSX)

A project task list with task, owner, status, and due-date columns.

File: XLSX · Task List
Use case: TemplatesSpreadsheet testing

Prometheus Alerting Rules: Four Rules Across Two Groups (yaml)

Four alerting rules over two groups, using the YAML features that break naive config readers: block scalars for multi-line PromQL, folded scalars for descriptions, Go template annotations with pipes, and keep_firing_for. Every expression references metrics that exist in this category's fixtures.

File: YAML · Alerts
Use case: ObservabilityConfig parsing+1· Conversion set

Prometheus Alerting Rules: Intentionally Invalid, Five Distinct Faults (yaml)

A rule file that is perfectly valid YAML and completely invalid as Prometheus rules: a rule that is both an alert and a recording rule, a PromQL syntax error, a duplicated group name, a rule with no expr and a duration written in prose. Intentionally invalid, with each fault labelled in place.

File: YAML · Alerts
Use case: ObservabilitySchema validation+1· Conversion set

Prometheus Exposition: 2,000-Series Cardinality Explosion (prom)

A single metric family blown up to 2,000 series by two unbounded labels (customer_id and session_id), which is the most common way a metrics bill and a TSDB both fall over. A load fixture for scrape parsing and a worked example for cardinality-limit rules.

File: PROM · Metrics
Use case: ObservabilityTime-series data+1

Prometheus Exposition: Broken Histograms, Intentionally Invalid (prom)

Two histogram families that are syntactically fine and semantically wrong: one has non-monotonic buckets and no +Inf bucket, the other reports a _count larger than its +Inf bucket. Intentionally invalid, because histogram_quantile over either produces a confidently wrong number rather than an error.

File: PROM · Metrics
Use case: ObservabilitySchema validation+1· Conversion set

Prometheus Exposition: Counters and Gauges (prom)

The body a /metrics endpoint returns: five metric families with HELP and TYPE metadata across 27 labelled series, request counters by route and status, process and runtime gauges, per-target up values (one deliberately 0) and a business gauge. The baseline exposition-parser fixture.

File: PROM · Metrics
Use case: ObservabilityTime-series data+1· Conversion set

Prometheus Exposition: Cumulative Histogram (prom)

A classic Prometheus histogram: eleven finite le buckets plus +Inf, with monotonically non-decreasing cumulative counts and matching _sum and _count series. The fixture for bucket ordering, cumulative arithmetic and histogram_quantile interpolation.

File: PROM · Metrics
Use case: ObservabilityTime-series data+1· Conversion set

Prometheus Exposition: Duplicate Series, Intentionally Invalid (prom)

One label set exposed twice, a second pair that is only a duplicate once labels are sorted, and a repeated HELP line. Intentionally invalid: a scrape must fail rather than let last-write-wins decide which of two values for the same series survives.

File: PROM · Metrics
Use case: ObservabilitySchema validation+1· Conversion set

Prometheus Exposition: Empty but Valid Scrape (prom)

A scrape body with metadata but no samples, which is what a freshly started process returns before it has recorded anything. Valid, and routinely mistaken for a failed scrape by code that treats an empty result as an error.

File: PROM · Metrics
Use case: ObservabilityError handling+1· Conversion set

Prometheus Exposition: Explicit and Skewed Timestamps (prom)

Samples with explicit millisecond timestamps alongside samples without any, including one an hour stale and one an hour in the future. Optional timestamps are the part of the exposition format most parsers get wrong, and out-of-window samples are what a scraper must reject rather than backfill.

File: PROM · Metrics
Use case: ObservabilityTime-series data+1· Conversion set

Prometheus Exposition: Label Value Escaping Edge Cases (prom)

Ten series whose label values contain the characters that break naive line splitting, escaped quotes and backslashes, an escaped newline, non-ASCII text, braces, commas, equals signs, a leading hash and significant whitespace. The exposition format defines exactly three escapes and this file uses all of them.

File: PROM · Metrics
Use case: ObservabilityEncoding detection+1· Conversion set

Prometheus Exposition: NaN, Infinities and Float Limits (prom)

Every numeric form the exposition format permits: NaN, +Inf and -Inf, negative zero, denormal and maximum doubles, and a uint64 counter beyond the exact range of a double. Parsers that route values through a JSON number or a 32-bit float fail on this file specifically.

File: PROM · Metrics
Use case: ObservabilityTime-series data+1· Conversion set

Prometheus Exposition: Samples with No HELP or TYPE (prom)

Samples exposed with no HELP or TYPE at all, metadata arriving after the sample it describes, blank and whitespace-only lines and a bare comment. All of it is legal (metadata is optional), and all of it breaks parsers that assume every sample is introduced by a TYPE line.

File: PROM · Metrics
Use case: ObservabilityConfig parsing+1· Conversion set

Prometheus Exposition: Summary with and without Quantiles (prom)

Two summary families: one exposing four client-side quantiles including quantile="1" for the observed maximum, and one exposing only _sum and _count, which is legal and common. Summaries cannot be re-aggregated across instances, and this fixture is where that gets tested.

File: PROM · Metrics
Use case: ObservabilityTime-series data+1· Conversion set

Prometheus Exposition: UTF-8 Quoted Metric and Label Names (prom)

Dotted OpenTelemetry-style metric and label names written with the quoted-name syntax that Prometheus 3 accepts, mixed in one document with a legacy underscore-named family. The fixture for parsers that still assume every name matches [a-zA-Z_][a-zA-Z0-9_]*.

File: PROM · Metrics
Use case: ObservabilityEncoding detection+1· Conversion set

Prometheus HTTP API: Error Envelope with a PromQL Parse Error (json)

The error envelope a Prometheus API returns for a malformed PromQL query: status, errorType, a message with a line and column position, and an empty but present data object. Clients that only check for a data key render this as a successful empty result.

File: JSON · Metrics
Use case: ObservabilityError handling+1

Prometheus HTTP API: Instant Query Vector with Warnings (json)

An instant-query response: five up series at a single evaluation timestamp, one of them zero, plus a warnings array that clients routinely ignore. A successful response can carry warnings, and dropping them hides truncated results.

File: JSON · Metrics
Use case: ObservabilityJSON parsing+1

Prometheus HTTP API: Metric Metadata with a HELP Conflict (json)

The metadata endpoint's response, where each metric name maps to a list because different targets can disagree. http_requests_total here has two conflicting HELP strings: the real-world state that a metric catalogue or documentation generator has to resolve rather than assume away.

File: JSON · Metrics
Use case: ObservabilityMetadata testing+1

Prometheus HTTP API: query_range Matrix Response (json)

A Prometheus /api/v1/query_range response: three labelled series of 30 points each at a 60-second step, with sample values as JSON strings and timestamps as float seconds. The exact envelope a dashboard client has to unpack, including the string-typed values that break naive charting code.

File: JSON · Metrics
Use case: ObservabilityJSON parsing+1· Conversion set

Explore the test library

Filter the library

5297 results