Internet Society Pulse

Internet Society Pulse is a platform that monitors the health, availability, and evolution of the Internet, providing metrics on key technologies that contribute to its security, resilience, and trustworthiness.

Bruin supports Internet Society Pulse as a source for Ingestr assets, allowing you to ingest data from Pulse into your data warehouse.

Step 1: Add a connection to .bruin.yml file

To connect to Internet Society Pulse, add a configuration item to the connections section of your .bruin.yml file. You will need an API token from the Internet Society Pulse platform.

connections:
  isoc_pulse:
    - name: 'my-pulse'
      token: 'your_token_here'

• token: The API token used for authentication with the Internet Society Pulse API.

Step 2: Create an asset file for data ingestion

Create an asset configuration YAML file (e.g., pulse_ingestion.asset.yml) in your assets folder:

name: public.https_adoption_us
type: ingestr
connection: postgres

parameters:
  source_connection: my-pulse
  source_table: 'https:US'
  destination: postgres

• name: The name of the asset.
• type: Set to ingestr to use the ingestr data pipeline.
• connection: The destination connection (e.g., postgres).
• source_connection: The name of the Pulse connection defined in .bruin.yml.
• source_table: The metric to ingest (see below for options).

Step 3: Run asset to ingest data

bruin run assets/pulse_ingestion.asset.yml

This command will ingest data from the specified Internet Society Pulse metric into your destination database.

Supported Metrics and Tables

Metric	Description	Country Support	Additional Options	PK	Inc Key	Inc Strategy
dnssec_adoption	DNSSEC adoption metrics for specific domains	No	Domain name	date	date	merge
dnssec_tld_adoption	DNSSEC adoption metrics for top-level domains	Yes	Country code	date	date	merge
dnssec_validation	DNSSEC validation metrics	Yes	Country code	date	date	merge
http	HTTP protocol metrics	No	None	date	date	merge
http3	HTTP/3 protocol metrics	No	None	date	date	merge
https	HTTPS adoption metrics	Yes	topsites, Country code	date	date	merge
ipv6	IPv6 adoption metrics	Yes	topsites, Country code	date	date	merge
net_loss	Internet disconnection metrics	Yes	Shutdown type, Country code	date	date	merge
resilience	Internet resilience metrics	Yes	Country code	date	date	merge
roa	Route Origin Authorization metrics	Yes	IP version (4/6), Country code	date	date	merge
rov	Route Origin Validation metrics	No	None	date	date	merge
tls	TLS protocol metrics	No	None	date	date	merge
tls13	TLS 1.3 protocol metrics	No	None	date	date	merge

Refer to the Pulse documentation for the full list and parameter syntax.

Example: Internet Shutdowns in US

name: public.net_shutdown_us
type: ingestr
connection: postgres

parameters:
  source_connection: my-pulse
  source_table: 'net_loss:shutdown:US'
  destination: postgres

Notes

• You must obtain your API token from the Internet Society Pulse platform.
• The source_table parameter uses a colon-separated syntax for metric, options, and country codes (e.g., https:topsites:US).
• Country codes should follow the ISO 3166-1 alpha-2 format (e.g., US, GB, DE).

For more details and advanced usage, see the official documentation.