Pingdom

Reading time: 0 minute(s) (0 words)

Pingdom is a website monitoring solution that gives users real-time, quality insights into the uptime and performance of their websites. After adding Pingdom as a data source in Nobl9, users can configure SLOs to check the overall performance status of their sites. Leveraging Pingdom, users can build SLOs on top of their existing metrics data.

Pingdom parameters and supported features in Nobl9

General support:: Release channel: Stable, Beta; Connection method: Agent, Direct; Replay and SLI Analyzer: Not supported; Event logs: Supported; Query checker: Not supported; Query parameters retrieval: Supported; Timestamp cache persistence: Supported
Query parameters:: Query interval: 1 min; Query delay: 1 min; Jitter: 15 sec; Timeout: 30 sec
Agent details and minimum required versions for supported features:: Plugin name: n9pingdom; Query delay environment variable: PINGDOM_QUERY_DELAY; Query parameters retrieval: 0.73.2; Timestamp cache persistence: 0.65.0
Additional notes:: Support for the uptime and transaction checks; Learn more

Authentication

Pingdom’s API uses basic authentication and a bearer token. Users can retrieve the token from the Pingdom UI (My Pingdom) and pass it to Nobl9.

To create a Pingdom API token if you don’t already have one, follow these steps:

Navigate to My Pingdom.
Log in to your customer account.
Go to Settings > Synthetic & RUM Settings > Pingdom API:

Image 1: Settings in the My Pingdom UI
Click Add API token, then Generate token (read access is enough for this integration):

Image 2: Adding API Token in the My Pingdom UI

Adding Pingdom as a data source

You can add the Pingdom data source using the direct or agent connection methods.

Direct connection method

A direct connection to Pingdom requires users to enter their credentials, which Nobl9 stores safely.

Nobl9 Web

Follow these steps to set up this type of connection:

Navigate to Integrations > Sources.
Click .
Click the required Source button.
Choose Direct.

Select one of the following Release Channels:
- The stable channel is fully tested by the Nobl9 team. It represents the final product; however, this channel does not contain all the new features of a beta release. Use it to avoid crashes and other limitations.
- The beta channel is under active development. Here, you can check out new features and improvements without the risk of affecting any viable SLOs. Remember that features in this channel can change.
Enter your API Token (mandatory).
You can find this in My Pingdom, under Synthetic & RUM Settings > Pingdom API. Details on creating a Pingdom API token were provided in the Authentication section above.

Select a Project.
Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
Enter a Display Name.
You can enter a user-friendly name with spaces in this field.
Enter a Name.
The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
Enter a Description.
Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
- The default value in Pingdom integration for Query delay is 1 minute.
info
Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
Click Add Data Source.

sloctl

Create a YAML definition to set up a direct connection with Pingdom. For this, refer to the following example:

YAML definition for the direct connection method
apiVersion: n9/v1alpha
kind: Direct
metadata:
  name: pingdom
  displayName: Pingdom Direct
  project: default
spec:
  description: Example Pingdom Direct
  releaseChannel: stable
  pingdom:
    apiToken: "[secret]"
  queryDelay:
    value: 2
    unit: Minute

Field	Type	Description
`queryDelay.unit` mandatory	enum	Specifies the unit for the query delay. Possible values: `Second` \| `Minute`. • Check query delay documentation for default unit of query delay for each source.
`queryDelay.value` mandatory	numeric	Specifies the value for the query delay. • Must be a number less than 1440 minutes (24 hours). • Check query delay documentation for default unit of query delay for each source.
`logCollectionEnabled` optional	boolean	Optional. Defaults to `false`. Set to `true` if you'd like your direct to collect event logs. Contact us to activate it.
`releaseChannel` mandatory	enum	Specifies the release channel. Accepted values: `beta` \| `stable`.
Source-specific fields
`pingdom.apiToken` mandatory	string, secret	Pingdom’s API uses basic authentication and a bearer token. You can retrieve the token from the Pingdom UI (My Pingdom) and pass it to Nobl9. See authentication section above for more details.

Apply your YAML definition using the sloctl apply command.

Agent connection method

Nobl9 Web

Follow the instructions below to set up an agent configuration.

Navigate to Integrations > Sources.
Click .
Click the required Source button.
Choose Agent.

Select one of the following Release Channels:
- The stable channel is fully tested by the Nobl9 team. It represents the final product; however, this channel does not contain all the new features of a beta release. Use it to avoid crashes and other limitations.
- The beta channel is under active development. Here, you can check out new features and improvements without the risk of affecting any viable SLOs. Remember that features in this channel can change.

Select a Project.
Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
Enter a Display Name.
You can enter a user-friendly name with spaces in this field.
Enter a Name.
The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
Enter a Description.
Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
- The default value in Pingdom integration for Query delay is 1 minute.
info
Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
Click Add Data Source.

Deploy your agent in a Kubernetes cluster or Docker container.

sloctl

Create a YAML definition to set up an agent connection with Pingdom. For this, refer to the following example:

YAML definition for the agent connection method
apiVersion: n9/v1alpha
kind: Agent
metadata:
  name: pingdom
  displayName: Pingdom Agent
  project: default
spec:
  description: Example Pingdom Agent
  releaseChannel: stable
  pingdom: {}
  queryDelay:
    value: 2
    unit: Minute

Field	Type	Description
`queryDelay.unit` mandatory	enum	Specifies the unit for the query delay. Possible values: `Second` \| `Minute`. • Check query delay documentation for default unit of query delay for each source.
`queryDelay.value` mandatory	numeric	Specifies the value for the query delay. • Must be a number less than 1440 minutes (24 hours). • Check query delay documentation for default unit of query delay for each source.
`releaseChannel` mandatory	enum	Specifies the release channel. Accepted values: `beta` \| `stable`.