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: postgresname: The name of the asset.type: Set toingestrto 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.ymlThis command will ingest data from the specified Internet Society Pulse metric into your destination database.
Available Source Tables
| Table | PK | Inc Key | Inc Strategy | Details |
|---|---|---|---|---|
dnssec_adoption | date | date | merge | DNSSEC adoption metrics for specific domains. Supports domain name as an additional option. |
dnssec_tld_adoption | date | date | merge | DNSSEC adoption metrics for top-level domains. Supports country code. |
dnssec_validation | date | date | merge | DNSSEC validation metrics. Supports country code. |
http | date | date | merge | HTTP protocol metrics. |
http3 | date | date | merge | HTTP/3 protocol metrics. |
https | date | date | merge | HTTPS adoption metrics. Supports topsites and country code (e.g., https:topsites:US). |
ipv6 | date | date | merge | IPv6 adoption metrics. Supports topsites and country code (e.g., ipv6:DE). |
net_loss | date | date | merge | Internet disconnection metrics. Supports shutdown type and country code. |
resilience | date | date | merge | Internet resilience metrics. Supports country code. |
roa | date | date | merge | Route Origin Authorization metrics. Supports IP version (4/6) and country code. |
rov | date | date | merge | Route Origin Validation metrics. |
tls | date | date | merge | TLS protocol metrics. |
tls13 | date | date | merge | TLS 1.3 protocol metrics. |
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: postgresNotes
- You must obtain your API token from the Internet Society Pulse platform.
- The
source_tableparameter 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.