Application Settings

Overview And Key Tabs Within Settings

The Settings section captures team setup, permissions, and credentials. You can access the Settings page from the user settings on the left navigation bar of the Fiddler UI.

Fiddler home page showing the user menu open and highlighting the Settings link.

General

The General tab shows your organization name, your email, and a few other details.

General tab of the Settings page.

Access

The Access tab shows the users, teams, and invitations for everyone in the organization.

Access > Users

The Users sub-tab shows all the users that are members of this organization.

Users sub-tab of the Access tab on the Settings page showing a list of users.

Access > Teams

The Teams tab shows all the teams that have been defined for this organization.

Teams sub-tab of the Access tab on the Settings page showing a list of teams

You can create a team by clicking on the plus (+) icon on the top-right.

🚧 Note

Only Org Admins can create teams. The plus (+) icon will not be visible unless you have the Org Admin role.

The create Team modal dialog popup.

Access > Invitations

The Invitations tab shows all pending user invitations. Invitations that have been accepted no longer appear.

Invitations sub-tab of the Access tab on the Settings page with a list of user invitations.

You can invite a user by clicking on the plus (+) icon on the top-right.

🚧 Note

Only Org Admins can invite users. The plus (+) icon will not be visible unless you have the Org Admin role.

Create Team modal dialog popup.

Credentials

The Credentials tab displays user access keys. These access keys are used by Fiddler Python client for authentication. Each Org Admin or Org Member can create a unique key by clicking on Create Key.

Credentials sub-tab of the Access tab on the Settings page with a list of keys and highlighting the create key button.

Webhooks

Webhooks enable you to link Fiddler to your notification and communication services, allowing them to receive Fiddler alerts as they're triggered. We support Slack and Microsoft Teams webhook integrations directly. We also offer a custom webhook option that works with any webhook-consuming platform. You can manage these webhooks in the "Webhook Integration" tab.

Configure a New Slack Webhook

From the "Webhook Integrations" tab, use the + icon on the "Webhook Integration" tab to configure a new webhook.

Create Webhook Service modal dialog

Follow these steps:

1. Enter a unique webhook name in the Service Name textbox

2. Select Slack in the Provider dropdown

3. Enter the Slack webhook URL provided by your Slack administrator which will appear similar to this example: https://hooks.slack.com/services/xxxxxxxxxx
4. Test the webhook service using the Test button

5. Click the Create button once the test is successful

Slack documentation on creating webhooks can be reviewed here.

Configure a Microsoft Teams Webhook

To configure a webhook for Microsoft Teams, follow the same steps listed for the Slack webhook, but instead select MS Teams for Provider type and enter the webhook URL provided by your MS Teams' administrator.

Microsoft Teams documentation on creating webhooks can be reviewed here.

Configure a New Custom Webhook

To configure a webhook for any other platform, follow the same steps listed for the Slack webhook, but instead select Other for Provider type and enter the webhook URL provided by the platform's administrator.

1. Enter a unique webhook name in the Service Name textbox

2. Select Other in the Provider dropdown

3. Enter the webhook URL provided by your platform administrator

4. Test the webhook service using the Test button

5. Click the Create button once the test is successful

Custom Webhook Payload Description

For custom webhooks, Fiddler sends payload with following fields:

Field Name	Type	Description	Example
alert_name	String	Name of the triggered alert	"Feature Drift Alert"
overall_severity	String	Alert severity level	"CRITICAL", "WARNING", "INFO"
project_name	String	Fiddler project name	"Fraud Detection"
model_name	String	Model being monitored	"fraud_classifier_v2"
priority	String	Configured alert priority	"HIGH", "MEDIUM", "LOW"
bin_start_time_string	String	Start time of the time bin for which alert has been triggerred	"2023-05-15 14:30:00"
bin_size	String	Time window for evaluation	"Day", "Hour", "Minute"
segment	String	Model segment identifier	"high_value_transactions"
message_content	String	Alert message content	"Model drift detected in production"
alert_inspect_url	String	URL to alert details in Fiddler	"https://fiddler.com/alert/123"

Example Payload

{
  "alert_name": "Test Alert",
  "overall_severity": "CRITICAL",
  "project_name": "Test Project",
  "model_name": "Test Model",
  "priority": "LOW",
  "bin_start_time_string": "2021-01-01 00:00:00",
  "bin_size": "Day",
  "segment": "Test Segment",
  "message_content": "Hello, This is a test notification from Fiddler Labs!",
  "alert_inspect_url": "https://fiddler.com/alert/123"
}

🚧 Important Note

Many platforms will require specific configuration to properly receive and process Fiddler's webhook notifications. Consult your platform's documentation for details on how to parse and display the incoming JSON payload.

Edit or Delete a Webhook

Webhooks list on the Webhook Integration tab with Delete Webhook and Edit Webhook actions

You can manage your webhook from the Webhook Integrations tab.

1. Select the webhook that you want to edit/delete using the "..." icon towards the right of a webhook integration row.

2. Select the Delete Webhook option to delete the webhook

🚧 Deleting a Webhook

You will not be able to delete a webhook that is already linked to alerts. To delete the webhook, you will need to modify the alert and then delete the webhook

1. Select the Edit Webhook option to edit the webhook

2. Click the Test button to test your changes

3. Click the Save button once the test is successful

---

❓ Questions? Talk to a product expert or request a demo.

💡 Need help? Contact us at [e-mail].