Prepping Pingdom for the Integrated Experience

As mentioned in Adam’s post the other week, Pingdom users will soon have the option to view end user experience data with their metrics, traces, and logs in the integrated experience.

In preparation for the integrated experience, today we have launched changes to Pingdom’s navigation, provided additional account management options, and updated our user management functions.

Simplified Navigation

We have consolidated all functions related to synthetic monitoring under one category in the side navigation call ‘Synthetics’. In this new section you will find Uptime, Transactions, Page Speed, Maintenance, Public status page, Email reports, Report banners, and Probe servers. Previously, these functions were spread out across three navigational areas, but now you have a one stop shop for all things synthetic.

202011_Pingdom_Syntetics Navigation.png

Additionally, the following changes were also made to our navigation:

  • Visitor Insights now has its own section called ‘Real User Monitoring’
  • Functions under ‘Sharing’ have been moved to ‘Synthetics’ and the navigation item removed
  • Functions under ‘Integrations’ and ‘Users and Teams’ have been moved to ‘Settings’ and the navigation items removed
  • The list of probe servers will now be found under ‘Synthetics’ instead of ‘Support’

Enhanced Account Management

Under ‘Settings’ you will notice two sections, ‘Organizational Settings’ and ‘Synthetics and RUM Settings’.

202011_Pingdom_Settings Only.png

Organizational settings are global settings that apply to Pingdom, AppOptics, Loggly, and Papertrail. By connecting more closely with the other cloud-based products, we can take advantage of shared functionality, such as SAML and the new Activity Log (allowing admins to see who is inviting who to what product).

202011_Pingdom_Activity Log.png

Admins will also be able to see which SolarWinds SaaS products their organization has access to:

202011_Pingdom_General_Org_Settings.png

 ‘Synthetics and RUM Settings’ are those settings that only apply to Pingdom, such as:

  • Subscription management
  • Pingdom account preferences, allows user to set time zone, date and number format in Pingdom only
  • Integrations (i.e. Slack, PagerDuty, and other apps)
  • Generating tokens for API use
  • Managing alert contacts and teams

Unified User Management

As we bring together our APM tools, we wanted to reduce the number of times you’d have to take the same action if you had multiple products. To help achieve this goal, with this release, we have unified user management. Managing users now falls under ‘Organization Settings – Users’.

When you want to invite a user to have login access to Pingdom, you will now have the option to provide the users with access to any SolarWinds SaaS product your Organization has access to. In the example below, I have been invited to AppOptics as a Member and Pingdom as a Viewer. I have not been given access to Papertrail (even though it is in my Organziation) or Loggly (This Organiation does not have a subscription to Loggly – you can tell because it is grayed out). Additionally, I have been granted the Organziational Role of Admin. This would allow me to invite other users to the org and various products.

202011_pingdom_User Management.png

Should you have any questions about these changes please feel free to leave a comment on this post or submit a ticket to support. We look forward to continuing to improve Pingdom and our integration with AppOptics, Loggly, and Papertrail.

Anonymous

Top Comments

  • hey  The new SAML group mapping also comes with just in time provisioning, so you can manage access in Azure AD itself without adding users manually in the product. For your role mapping, when you…

Parents
  • OK finally got this working with some help from Pingdom support. I'm not sure whether this is standard IdP settings that I'm not aware of or just some gaps in the documentation. 

    So to get the role provisioning working using Azure AD:

    1. Select Single sign-on within the Pingdom Enterprise Application
    2. Select SAML
      pidge_84_0-1612819445045.png
    3. Select Edit next to User Attributes & Claims
      pidge_84_1-1612819510384.png
    4. Select Add a group claim
      1. Set the groups to send (I selected groups assigned to the application)
      2. Select the Group ID as the attribute
      3. Select the tick box to customise the name of the group claim to groups
        pidge_84_2-1612819633939.png
    5. Within Role Mapping in the solarwinds.cloud portal, add the Object ID of the Azure AD group
      pidge_84_3-1612819774634.pngpidge_84_5-1612819834129.png
    6. Done! Members of the Azure AD groups should now be automatically provisioned the role mapped.

    Delighted its working - its a great feature 

Comment
  • OK finally got this working with some help from Pingdom support. I'm not sure whether this is standard IdP settings that I'm not aware of or just some gaps in the documentation. 

    So to get the role provisioning working using Azure AD:

    1. Select Single sign-on within the Pingdom Enterprise Application
    2. Select SAML
      pidge_84_0-1612819445045.png
    3. Select Edit next to User Attributes & Claims
      pidge_84_1-1612819510384.png
    4. Select Add a group claim
      1. Set the groups to send (I selected groups assigned to the application)
      2. Select the Group ID as the attribute
      3. Select the tick box to customise the name of the group claim to groups
        pidge_84_2-1612819633939.png
    5. Within Role Mapping in the solarwinds.cloud portal, add the Object ID of the Azure AD group
      pidge_84_3-1612819774634.pngpidge_84_5-1612819834129.png
    6. Done! Members of the Azure AD groups should now be automatically provisioned the role mapped.

    Delighted its working - its a great feature 

Children
No Data