Skip to content
Novus Examples
csv602 B

Juniper Workspace Cloud: Raw metered usage events

Raw metered usage events for Juniper Workspace Cloud. 18 daily usage records over 2026-08-01 to 2026-08-03 for 6 accounts, carrying an export count and a storage reading in MB. These are the inputs the tiered usage bill is computed from; the exports column sums to 102.

csv

text/csv

602 B
Document Set
saas
Industry
software
Source Kit
saas-subscriptions
Synthetic
true
As Of
2026-09-08
Rows
18

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
saas
Industry
software
Source Kit
saas-subscriptions
Synthetic
true
As Of
2026-09-08
Rows
18
Accounts
6
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Aggregate the raw events by account and feed the totals into the tiered rate card.
Expected result
18 rows group into 6 accounts with 3 readings each; the export counts sum to 102 and reproduce the billable_exports column of usage-billing-tiered.csv exactly.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Juniper Workspace Cloud: Raw metered usage events” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 18 rows · UTF-8. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import pandas as pd

df = pd.read_csv("usage-events.csv")
print(df.head())
print(df.dtypes)

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.