SignalFx Developers Guide

Developer Home

Product Docs

SignalFx

Integrations API

API for creating, retrieving, updating, and deleting integrations from external systems to SignalFx.

Integrations store basic information about an external system in SignalFx. They also ensure that the connection is valid before you try to use it.

For example, suppose you want to send detector notifications using Slack. When you integrate Slack with SignalFx as the first step, you get the following:

  • Verification that Slack and SignalFx can communicate
  • A SignalFx-assigned integration ID that links to the integration

To configure alerts that go to Slack from a detector, you specify the Slack integration ID and the Slack channel name.

Each external system has its own integration requirements. Read the documentation for the request body of the POST or UPDATE /integration to learn the requirements for the integration you want.

Authentication

To create, update, delete, or validate integrations, you need to authenticate your request using a session token associated with a SignalFx administrator.

To retrieve integration information, your session token doesn't need to be associated with an administrator. You can also retrieve integrations using an org token.

In the web UI, session tokens are known as user API access tokens, and org tokens are known as access tokens. To learn more about authentication tokens, see the topic Authentication Tokens in the Developers Guide.

Supported service types

SignalFx offers integrations for the following:

  • Monitoring systems such as AWS CloudWatch
  • SSO Authentication systems that use SAML, such as ADFS
  • Notification systems such as PagerDuty

Monitoring integrations

SignalFx integrations APIs support monitoring for the following services:

  • Amazon Web Services (AWS)
  • Google Cloud Platform (GCP)
  • Microsoft Azure
  • NewRelic

SSO Authentication using SAML

SignalFx integration APIs support SAML-based SSO integrations for the following services:

  • Microsoft Active Directory Federation Services (ADFS)
  • Bitium
  • Okta
  • OneLogin
  • PingOne

Alert notification systems

SignalFx integration APIs support alert notifications using the following services:

  • Amazon EventBridge
  • BigPanda
  • Jira
  • Office 365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • xMatters

NOTE: You can't create Office 365 integrations using the API, and your ability to update them in a PUT request is limited, but you can retrieve their data or delete them. To create an Office 365 integration, use the the web UI.

Viewing request body documentation

The request body format for the following operations depends on the type of integration you use:

  • POST /integration
  • PUT /integration/{id}

The response body format for the following operations also depends on the type of integration you use:

  • GET /integration
  • GET /integration/{id}

Retrieve Integrations Using Query

Retrieves integrations based on search criteria

get /integration

SignalFx API endpoint.

Replace {REALM} with the name of your realm.

For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.

To find your realm, go to your profile page in the SignalFx web UI.

If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration

Retrieves one or more integration objects based on a query specified in query parameters encoded on the URL.

NOTE: To ensure security, SignalFx omits some authentication and authorization properties from response objects.

Jira integration:

To see an example of the response to this operation for a Jira integration, see Retrieve Single Integration.

The response body contains a union of the following response properties:

  • Properties common to all integration responses
  • Properties common to all Jira integration responses
  • Authentication credential properties for Jira Cloud integrations
  • Authentication credential properties for Jira Server integrations

Some Jira integration properties are set to null in the response:

  • Optional properties that you didn't specify in your creation request

  • Password or API token, to ensure security

  • Properties not used for a specific type of Jira integration.

    For example, if you integrate with Jira Cloud, the response body contains "username": null because username isn't a valid property for a Jira Cloud integration.

query Parameters
name
string

Integration object name to search for. You can use wildcard characters to specify the name:

  • *: Matches a run of any characters in any part of the name
  • ?: Matches any single character in any part of the name
type
string
Enum:"ADFS" "AWSCloudWatch" "AmazonEventBridge" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Jira" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of integration to search for. This property is an enumerated string, and only the enumerated values are allowed.

offset
integer <int32> >= 0
Default: 0

0-relative position in the result set where SignalFx should start returning integration objects.

limit
integer <int32> >= 1
Default: 50

Number of integration objects to return from the result set

header Parameters
X-SF-TOKEN
required
string

Authentication token

Responses

200

Success

NOTE: If the request is well-formed but SignalFx can't find any matching integration objects, the API still returns 200. In this case, the count property is set to 0, and the results array is empty.

Response Schema: application/json
count
integer <int64>

Number of integrations that matched the search criteria. This value is not the number of integrations returned in the response body. To learn more, see the description of results.

results
Microsoft ADFS Integration (object) or AWS CloudWatch Integration (object) or Amazon EventBridge Integration (object) or Microsoft Azure Active Directory Integration (object) or Microsoft Azure Integration (object) or BigPanda Integration (object) or Bitium Integration (object) or Google Cloud Platform Integration (object) or Google Cloud Identity Integration (object) or Jira Integration Response (object) or NewRelic Integration (object) or Okta Integration (object) or Microsoft Office 365 Integration (object) or OneLogin Integration (object) or Opsgenie Integration (object) or PagerDuty Integration (object) or PingOne Integration (object) or ServiceNow Integration (object) or Slack Integration (object) or VictorOps Integration (object) or Webhook Integration (object) or xMatters Integration (object)

List of integrations, in the form of a JSON array of JSON objects. Each object contains properties that are common to all integrations as well as properties that are specific to the integration type (type property) for the object.

The size of results and the value of count are not necessarily equal:

  • If you don't specify limit or offset: If count > 50, then sizeOf(results) = 50; otherwise sizeOf(results) = count.
  • If you only specify limit: If count > limit then sizeOf(results) = limit; otherwise sizeOf(results) = count.
  • If you specify limit and offset: If count > (offset + limit) then sizeOf(results) = limit; otherwise, sizeOf(results) = limit.

Response samples

application/json
Copy
Expand all Collapse all
{
  • "count": 0,
  • "results":
    {
    }
}

Create Integration

Creates an integration

post /integration

SignalFx API endpoint.

Replace {REALM} with the name of your realm.

For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.

To find your realm, go to your profile page in the SignalFx web UI.

If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration

Creates an integration object that SignalFx uses to connect with a monitoring, SSO, or alerting service. The steps for establishing a connection to a service differ for each type of service and may differ for individual services.

Each service has specific information requirements for integrating with SignalFx.

NOTES:

  • To ensure security, SignalFx omits authentication and authorization properties from response objects.
  • In the response object, the "enabled" property is always set to true.

Jira integration: For a Jira integration request, the response body contains a union of the following response properties:

  • Properties common to all integration responses
  • Properties common to all Jira integration responses
  • Authentication credential properties for Jira Cloud integrations
  • Authentication credential properties for Jira Server integrations

Some Jira integration properties are set to null in the response:

  • Optional properties that you didn't specify in your creation request

  • Password or API token, to ensure security

  • Properties not used for a specific type of Jira integration.

    For example, if you integrate with Jira Cloud, the response body contains "username": null because username isn't a valid property for a Jira Cloud integration.

query Parameters
skipValidation
boolean

Flag that controls how SignalFx validates an alert integration object. If true, SignalFx doesn't send a test notification.

header Parameters
Content-Type
required
string

Format of the request body. Always "application/json".

X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user who has administrative privileges.

Request Body schema: application/json

Properties of the integration.

NOTE: Because this is a request to create a new integration, you must specify the "type" and "name" properties:

  • "type" determines the type of integration that SignalFx creates.
  • "name" provides a unique name for the integration.
One of
  • Microsoft ADFS Integration
  • AWS CloudWatch Integration
  • Amazon EventBridge Integration
  • Microsoft Azure Active Directory Integration
  • Microsoft Azure Integration
  • BigPanda Integration
  • Bitium Integration
  • Google Cloud Platform Integration
  • Google Cloud Identity Integration
  • Jira Integration Request
  • NewRelic Integration
  • Okta Integration
  • OneLogin Integration
  • Opsgenie Integration
  • PagerDuty Integration
  • PingOne Integration
  • ServiceNow Integration
  • Slack Integration
  • VictorOps Integration
  • Webhook Integration
  • xMatters Integration
enabled
boolean (Enabled)

Indicates the state of the integration. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.

When you create an integration, set this property according to the instructions in the product documentation. Some integrations, such as AWS, expect the initial value to be false, which lets you create the integration and use its properties to set values in AWS.

id
string (IntegrationID)

SignalFx-assigned ID of the integration. Use this property to refer to an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint.

name
string (Name)

Human-readable label for the integration. Use this property to identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)
Enum:"ADFS" "AWSCloudWatch" "AmazonEventBridge" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Jira" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of service that this integration represents. This is an enumerated string.

For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • Amazon EventBridge
  • BigPanda
  • Jira
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")
issuerUrl
string <uri> (IssuerUrl)

URL of the entity that issued the certificate for a SAML integration

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Responses

200

Success

Response Schema: application/json
One of
  • Microsoft ADFS Integration
  • AWS CloudWatch Integration
  • Amazon EventBridge Integration
  • Microsoft Azure Active Directory Integration
  • Microsoft Azure Integration
  • BigPanda Integration
  • Bitium Integration
  • Google Cloud Platform Integration
  • Google Cloud Identity Integration
  • Jira Integration Response
  • NewRelic Integration
  • Okta Integration
  • OneLogin Integration
  • Opsgenie Integration
  • PagerDuty Integration
  • PingOne Integration
  • ServiceNow Integration
  • Slack Integration
  • VictorOps Integration
  • Webhook Integration
  • xMatters Integration
created
integer <int64> (Created)

Date and time the integration was created, in the form of a Unix timestamp. Set by SignalFx; read-only

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration. If SignalFx created the object, the value is "AAAAAAAAAA". Set by SignalFx; read-only

enabled
boolean (Enabled)

Indicates the state of the integration. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.

When you create an integration, set this property according to the instructions in the product documentation. Some integrations, such as AWS, expect the initial value to be false, which lets you create the integration and use its properties to set values in AWS.

id
string (IntegrationID)

SignalFx-assigned ID of the integration. Use this property to refer to an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint.

lastUpdated
integer <int64> (LastUpdated)

The date and time the integration was last updated, in the form of a Unix timestamp. Set by SignalFx; read-only

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the user who last updated the integration. If SignalFx last updated the integration, the value is "AAAAAAAAAA". Set by SignalFx; read-only

name
string (Name)

Human-readable label for the integration. Use this property to identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)
Enum:"ADFS" "AWSCloudWatch" "AmazonEventBridge" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Jira" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of service that this integration represents. This is an enumerated string.

For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • Amazon EventBridge
  • BigPanda
  • Jira
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")
issuerUrl
string <uri> (IssuerUrl)

URL of the entity that issued the certificate for a SAML integration

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

400

Invalid request

Response Schema: application/json
One of
  • Integration Request Failures
  • Jira Integration Request Failure
One of
  • CommonIntegrationFailureAuthentication
  • CommonIntegrationFailureInvalidIntegrationId
  • CommonIntegrationFailureUnknownIntegrationId
code
integer

HTTP response code. Always 401 (Unauthorized)

message
string

Human-readable text message for the error. Always "<p>Problem accessing /v2/integration. Reason:<pre> Unauthorized</pre></p>"

Request samples

application/json
Copy
Expand all Collapse all
{
  • "enabled": true,
  • "id": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": "http://example.com",
  • "metadata": "string",
  • "publicKey": "string"
}

Response samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": "http://example.com",
  • "metadata": "string",
  • "publicKey": "string"
}

Validate Integration

Validates the integration specified in the {id} path parameter

get /integration/validate/{id}

SignalFx API endpoint.

Replace {REALM} with the name of your realm.

For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.

To find your realm, go to your profile page in the SignalFx web UI.

If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/validate/{id}

Validates the credentials of an existing integration.

Integrations such as AWS or GCP may have permission changes. Use this API to verify that the integration is still valid.

NOTE: This API doesn't require a request body, and doesn't return a response body.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to validate

header Parameters
X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user who has administrative privileges.

Responses

200

Successful validation of the integration object

Delete Single Integration

Deletes an integration specified in the {id} path parameter

delete /integration/{id}

SignalFx API endpoint.

Replace {REALM} with the name of your realm.

For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.

To find your realm, go to your profile page in the SignalFx web UI.

If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/{id}

Deletes the integration object specified by the id path parameter.

NOTE: This API doesn't require a request body, and doesn't return a response body.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to delete

header Parameters
X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user who has administrative privileges.

Responses

200

Successful update of the integration object

Retrieve Single Integration

Retrieves an integration specified in the {id} path parameter

get /integration/{id}

SignalFx API endpoint.

Replace {REALM} with the name of your realm.

For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.

To find your realm, go to your profile page in the SignalFx web UI.

If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/{id}

Retrieves the integration object specified by the id path parameter. NOTE: To ensure security, SignalFx omits some authentication and authorization properties from response objects.

Jira integration:

For a Jira integration request, the response body contains a union of the following response properties:

  • Properties common to all integration responses
  • Properties common to all Jira integration responses
  • Authentication credential properties for Jira Cloud integrations
  • Authentication credential properties for Jira Server integrations

Some Jira integration properties are set to null in the response:

  • Optional properties that you didn't specify in your creation request

  • Password or API token, to ensure security

  • Properties not used for a specific type of Jira integration.

    For example, if you integrate with Jira Cloud, the response body contains "username": null because username isn't a valid property for a Jira Cloud integration.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to retrieve

header Parameters
X-SF-Token
required
string

Authentication token

Responses

200

Success

NOTE: If the request is well-formed but SignalFx can't find the object, the API still returns 200. In this case, the response body is empty.

Response Schema: application/json
One of
  • Microsoft ADFS Integration
  • AWS CloudWatch Integration
  • Amazon EventBridge Integration
  • Microsoft Azure Active Directory Integration
  • Microsoft Azure Integration
  • BigPanda Integration
  • Bitium Integration
  • Google Cloud Platform Integration
  • Google Cloud Identity Integration
  • Jira Integration Response
  • NewRelic Integration
  • Microsoft Office 365 Integration
  • Okta Integration
  • OneLogin Integration
  • Opsgenie Integration
  • PagerDuty Integration
  • PingOne Integration
  • ServiceNow Integration
  • Slack Integration
  • VictorOps Integration
  • Webhook Integration
  • xMatters Integration
created
integer <int64> (Created)

Date and time the integration was created, in the form of a Unix timestamp. Set by SignalFx; read-only

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration. If SignalFx created the object, the value is "AAAAAAAAAA". Set by SignalFx; read-only

enabled
boolean (Enabled)

Indicates the state of the integration. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.

When you create an integration, set this property according to the instructions in the product documentation. Some integrations, such as AWS, expect the initial value to be false, which lets you create the integration and use its properties to set values in AWS.

id
string (IntegrationID)

SignalFx-assigned ID of the integration. Use this property to refer to an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint.

lastUpdated
integer <int64> (LastUpdated)

The date and time the integration was last updated, in the form of a Unix timestamp. Set by SignalFx; read-only

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the user who last updated the integration. If SignalFx last updated the integration, the value is "AAAAAAAAAA". Set by SignalFx; read-only

name
string (Name)

Human-readable label for the integration. Use this property to identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)
Enum:"ADFS" "AWSCloudWatch" "AmazonEventBridge" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Jira" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of service that this integration represents. This is an enumerated string.

For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • Amazon EventBridge
  • BigPanda
  • Jira
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")
issuerUrl
string <uri> (IssuerUrl)

URL of the entity that issued the certificate for a SAML integration

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Response samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": "http://example.com",
  • "metadata": "string",
  • "publicKey": "string"
}

Update Single Integration

Updates an integration specified in the {id} path parameter

put /integration/{id}

SignalFx API endpoint.

Replace {REALM} with the name of your realm.

For example, if your realm is eu0, use https://api.eu0.signalfx.com/v2.

To find your realm, go to your profile page in the SignalFx web UI.

If you don't include a realm and use https://api.signalfx.com/v2, SignalFx interprets the endpoint as pointing to the us0 realm.

https://api.{realm}.signalfx.com/v2/integration/{id}

Updates the integration object specified by the id path parameter.

NOTE: To ensure security, SignalFx omits some authentication and authorization properties from response objects.

Jira integration:

For a Jira integration request, the response body contains a union of the following response properties:

  • Properties common to all integration responses
  • Properties common to all Jira integration responses
  • Authentication credential properties for Jira Cloud integrations
  • Authentication credential properties for Jira Server integrations

Some Jira integration properties are set to null in the response:

  • Optional properties that you didn't specify in your creation request

  • Password or API token, to ensure security

  • Properties not used for a specific type of Jira integration.

    For example, if you integrate with Jira Cloud, the response body contains "username": null because username isn't a valid property for a Jira Cloud integration.

path Parameters
id
required
string

SignalFx-assigned ID of the existing integration object that you want to update

query Parameters
skipValidation
boolean

Flag that controls how SignalFx validates an alert integration object. If true, SignalFx doesn't send a test notification.

header Parameters
Content-Type
required
string

Format of the request body. Always "application/json".

X-SF-TOKEN
required
string

Authentication token. Must be a session token (User API access token) associated with a SignalFx user who has administrative privileges.

Request Body schema: application/json

Model specifying the properties that SignalFx uses to update the integration object. Each service that SignalFx integrates with has its own model.

NOTE: For Office 365 integrations, you can only update the following properties:

  • "name"
  • "creator"
  • "created"
  • "lastUpdated"
  • "lastUpdatedBy"
  • "enabled"
  • "type"

All of these fields are described in the IntegrationCommonProperties schema.

One of
  • Microsoft ADFS Integration
  • AWS CloudWatch Integration
  • Amazon EventBridge Integration
  • Microsoft Azure Active Directory Integration
  • Microsoft Azure Integration
  • BigPanda Integration
  • Bitium Integration
  • Google Cloud Platform Integration
  • Google Cloud Identity Integration
  • Jira Integration Request
  • NewRelic Integration
  • Microsoft Office 365 Integration
  • Okta Integration
  • OneLogin Integration
  • Opsgenie Integration
  • PagerDuty Integration
  • PingOne Integration
  • ServiceNow Integration
  • Slack Integration
  • VictorOps Integration
  • Webhook Integration
  • xMatters Integration
enabled
boolean (Enabled)

Indicates the state of the integration. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.

When you create an integration, set this property according to the instructions in the product documentation. Some integrations, such as AWS, expect the initial value to be false, which lets you create the integration and use its properties to set values in AWS.

id
string (IntegrationID)

SignalFx-assigned ID of the integration. Use this property to refer to an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint.

name
string (Name)

Human-readable label for the integration. Use this property to identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)
Enum:"ADFS" "AWSCloudWatch" "AmazonEventBridge" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Jira" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of service that this integration represents. This is an enumerated string.

For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • Amazon EventBridge
  • BigPanda
  • Jira
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")
issuerUrl
string <uri> (IssuerUrl)

URL of the entity that issued the certificate for a SAML integration

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Responses

200

Successful update of the integration object

Response Schema: application/json
One of
  • Microsoft ADFS Integration
  • AWS CloudWatch Integration
  • Amazon EventBridge Integration
  • Microsoft Azure Active Directory Integration
  • Microsoft Azure Integration
  • BigPanda Integration
  • Bitium Integration
  • Google Cloud Platform Integration
  • Google Cloud Identity Integration
  • NewRelic Integration
  • Microsoft Office 365 Integration
  • Okta Integration
  • OneLogin Integration
  • Opsgenie Integration
  • PagerDuty Integration
  • PingOne Integration
  • ServiceNow Integration
  • Slack Integration
  • VictorOps Integration
  • Webhook Integration
  • xMatters Integration
created
integer <int64> (Created)

Date and time the integration was created, in the form of a Unix timestamp. Set by SignalFx; read-only

creator
string (Creator)

SignalFx-assigned user ID of the user that created the integration. If SignalFx created the object, the value is "AAAAAAAAAA". Set by SignalFx; read-only

enabled
boolean (Enabled)

Indicates the state of the integration. If true, the integration is enabled. If false, the integration is disabled, and you must enable it by setting "enabled" to true in a PUT request that updates the object.

When you create an integration, set this property according to the instructions in the product documentation. Some integrations, such as AWS, expect the initial value to be false, which lets you create the integration and use its properties to set values in AWS.

id
string (IntegrationID)

SignalFx-assigned ID of the integration. Use this property to refer to an integration using the GET, PUT, or DELETE /integration/{id} endpoints or the GET /integration/validate{id}/ endpoint.

lastUpdated
integer <int64> (LastUpdated)

The date and time the integration was last updated, in the form of a Unix timestamp. Set by SignalFx; read-only

lastUpdatedBy
string (LastUpdatedBy)

SignalFx-assigned ID of the user who last updated the integration. If SignalFx last updated the integration, the value is "AAAAAAAAAA". Set by SignalFx; read-only

name
string (Name)

Human-readable label for the integration. Use this property to identify a specific integration when you're using multiple integrations for the same service.

type
required
string (Type)
Enum:"ADFS" "AWSCloudWatch" "AmazonEventBridge" "Azure" "AzureAD" "Bitium" "BigPanda" "GCP" "GoogleSaml" "Jira" "Office365" "Okta" "OneLogin" "Opsgenie" "PagerDuty" "PingOne" "NewRelic" "ServiceNow" "Slack" "VictorOps" "Webhook" "XMatters"

Type of service that this integration represents. This is an enumerated string.

For data collection services, the allowed values are:

  • AWSCloudWatch
  • Azure
  • GCP
  • NewRelic

For SSO integrations, the allowed values are:

  • ADFS
  • AzureAD
  • Bitium
  • GoogleSaml
  • Okta
  • OneLogin
  • PingOne

For alerting services, the allowed values are:

  • Amazon EventBridge
  • BigPanda
  • Jira
  • Office365
  • Opsgenie
  • PagerDuty
  • ServiceNow
  • Slack
  • VictorOps
  • Webhook
  • XMatters (note the capital "X")
issuerUrl
string <uri> (IssuerUrl)

URL of the entity that issued the certificate for a SAML integration

metadata
string (Metadata)

File name of the SAML metadata XML file for the integration: FederationMetadata.xml

publicKey
string (PublicKey)

Contents of the certificate.pem file for the public key associated with the SAML integration

Request samples

application/json
Copy
Expand all Collapse all
{
  • "enabled": true,
  • "id": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": "http://example.com",
  • "metadata": "string",
  • "publicKey": "string"
}

Response samples

application/json
Copy
Expand all Collapse all
{
  • "created": 1556361030000,
  • "creator": "string",
  • "enabled": true,
  • "id": "string",
  • "lastUpdated": 1556620230000,
  • "lastUpdatedBy": "string",
  • "name": "string",
  • "type": "ADFS",
  • "issuerUrl": "http://example.com",
  • "metadata": "string",
  • "publicKey": "string"
}