Other cloud services
Pingdom Sensor
This sensor monitors the status of the selected Pingdom check and response time of a monitored webpage
To use this sensor, you need to configure at least one Pingdom basic check.
Performance Counters:
- Response time (in seconds)
Statuses:
Last Check Status (Contains: time of the latest check, descriptions of statuses, probe id)
Default Alerts:
- Alert on check status - This alert occurs if the "Last Check Status" changes to a
down,unknown,orunconfirmedstate.
Default Report
- Response time - This report collects "Response time" counter data.
Credentials and registration
The sensor requires an API token to work that you can create in the Pingdom application.
NetCrunch requires Read Access permission.
Copy token and create a profile in NetCrunch (Click on edit next to the profile while adding the sensor and select the 'bearer' authentication scheme.
Pingdom sensor can be added to the Cloud Service node only
GitLab Cloud Sensor
This sensor monitors the latest build/job status on a specific project in the GitLab cloud repository. At least one project on GitLab, with configured jobs/builds, is necessary to use this sensor. GitLab documentation about jobs configuration can be found in GitLab CI/CD pipeline configuration reference
Performance Counters
- Total build duration (in seconds)
Statuses
- Last build overall (Contains information about "Last build date" and all "Build stages statuses")
Default Alerts
- Last build status changed to "Failed" - This alert will be generated if "The last build overall" changes to the "Failed" state.
Credentials
-
Access Token: GitLab documentation: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#doc-nav E.g. ATzt2bfFo_YqLXsVc-6y
-
GitLab Namespace and GitLab Project name: After entering any project, both can be found within the URL to access your project. E.g., https://gitlab.com/test1ws12/test_123.git- GitLab Namespace is test1ws12, and GitLab Project name is test_123