signalfx.azure.Integration
Explore with Pulumi AI
Splunk Observability Cloud Azure integrations. For help with this integration see Monitoring Microsoft Azure.
NOTE When managing integrations, use a session token of an administrator to authenticate the Splunk Observability Cloud provider. See Operations that require a session token for an administrator. Otherwise you’ll receive a 4xx error.
Example
import * as pulumi from "@pulumi/pulumi";
import * as signalfx from "@pulumi/signalfx";
const azureMyteam = new signalfx.azure.Integration("azureMyteam", {
additionalServices: [
"some/service",
"another/service",
],
appId: "YYY",
customNamespacesPerServices: [{
namespaces: [
"monitoringAgent",
"customNamespace",
],
service: "Microsoft.Compute/virtualMachines",
}],
enabled: true,
environment: "azure",
pollRate: 300,
resourceFilterRules: [
{
filterSource: "filter('azure_tag_service', 'payment') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))",
},
{
filterSource: "filter('azure_tag_service', 'notification') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))",
},
],
secretKey: "XXX",
services: ["microsoft.sql/servers/elasticpools"],
subscriptions: ["sub-guid-here"],
tenantId: "ZZZ",
});
import pulumi
import pulumi_signalfx as signalfx
azure_myteam = signalfx.azure.Integration("azureMyteam",
additional_services=[
"some/service",
"another/service",
],
app_id="YYY",
custom_namespaces_per_services=[signalfx.azure.IntegrationCustomNamespacesPerServiceArgs(
namespaces=[
"monitoringAgent",
"customNamespace",
],
service="Microsoft.Compute/virtualMachines",
)],
enabled=True,
environment="azure",
poll_rate=300,
resource_filter_rules=[
signalfx.azure.IntegrationResourceFilterRuleArgs(
filter_source="filter('azure_tag_service', 'payment') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))",
),
signalfx.azure.IntegrationResourceFilterRuleArgs(
filter_source="filter('azure_tag_service', 'notification') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))",
),
],
secret_key="XXX",
services=["microsoft.sql/servers/elasticpools"],
subscriptions=["sub-guid-here"],
tenant_id="ZZZ")
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using SignalFx = Pulumi.SignalFx;
return await Deployment.RunAsync(() =>
{
var azureMyteam = new SignalFx.Azure.Integration("azureMyteam", new()
{
AdditionalServices = new[]
{
"some/service",
"another/service",
},
AppId = "YYY",
CustomNamespacesPerServices = new[]
{
new SignalFx.Azure.Inputs.IntegrationCustomNamespacesPerServiceArgs
{
Namespaces = new[]
{
"monitoringAgent",
"customNamespace",
},
Service = "Microsoft.Compute/virtualMachines",
},
},
Enabled = true,
Environment = "azure",
PollRate = 300,
ResourceFilterRules = new[]
{
new SignalFx.Azure.Inputs.IntegrationResourceFilterRuleArgs
{
FilterSource = "filter('azure_tag_service', 'payment') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))",
},
new SignalFx.Azure.Inputs.IntegrationResourceFilterRuleArgs
{
FilterSource = "filter('azure_tag_service', 'notification') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))",
},
},
SecretKey = "XXX",
Services = new[]
{
"microsoft.sql/servers/elasticpools",
},
Subscriptions = new[]
{
"sub-guid-here",
},
TenantId = "ZZZ",
});
});
package main
import (
"github.com/pulumi/pulumi-signalfx/sdk/v7/go/signalfx/azure"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := azure.NewIntegration(ctx, "azureMyteam", &azure.IntegrationArgs{
AdditionalServices: pulumi.StringArray{
pulumi.String("some/service"),
pulumi.String("another/service"),
},
AppId: pulumi.String("YYY"),
CustomNamespacesPerServices: azure.IntegrationCustomNamespacesPerServiceArray{
&azure.IntegrationCustomNamespacesPerServiceArgs{
Namespaces: pulumi.StringArray{
pulumi.String("monitoringAgent"),
pulumi.String("customNamespace"),
},
Service: pulumi.String("Microsoft.Compute/virtualMachines"),
},
},
Enabled: pulumi.Bool(true),
Environment: pulumi.String("azure"),
PollRate: pulumi.Int(300),
ResourceFilterRules: azure.IntegrationResourceFilterRuleArray{
&azure.IntegrationResourceFilterRuleArgs{
FilterSource: pulumi.String("filter('azure_tag_service', 'payment') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))"),
},
&azure.IntegrationResourceFilterRuleArgs{
FilterSource: pulumi.String("filter('azure_tag_service', 'notification') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))"),
},
},
SecretKey: pulumi.String("XXX"),
Services: pulumi.StringArray{
pulumi.String("microsoft.sql/servers/elasticpools"),
},
Subscriptions: pulumi.StringArray{
pulumi.String("sub-guid-here"),
},
TenantId: pulumi.String("ZZZ"),
})
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.signalfx.azure.Integration;
import com.pulumi.signalfx.azure.IntegrationArgs;
import com.pulumi.signalfx.azure.inputs.IntegrationCustomNamespacesPerServiceArgs;
import com.pulumi.signalfx.azure.inputs.IntegrationResourceFilterRuleArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var azureMyteam = new Integration("azureMyteam", IntegrationArgs.builder()
.additionalServices(
"some/service",
"another/service")
.appId("YYY")
.customNamespacesPerServices(IntegrationCustomNamespacesPerServiceArgs.builder()
.namespaces(
"monitoringAgent",
"customNamespace")
.service("Microsoft.Compute/virtualMachines")
.build())
.enabled(true)
.environment("azure")
.pollRate(300)
.resourceFilterRules(
IntegrationResourceFilterRuleArgs.builder()
.filterSource("filter('azure_tag_service', 'payment') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))")
.build(),
IntegrationResourceFilterRuleArgs.builder()
.filterSource("filter('azure_tag_service', 'notification') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))")
.build())
.secretKey("XXX")
.services("microsoft.sql/servers/elasticpools")
.subscriptions("sub-guid-here")
.tenantId("ZZZ")
.build());
}
}
resources:
azureMyteam:
type: signalfx:azure:Integration
properties:
# Optional
additionalServices:
- some/service
- another/service
appId: YYY
# Optional
customNamespacesPerServices:
- namespaces:
- monitoringAgent
- customNamespace
service: Microsoft.Compute/virtualMachines
enabled: true
environment: azure
pollRate: 300
resourceFilterRules:
- filterSource: filter('azure_tag_service', 'payment') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))
- filterSource: filter('azure_tag_service', 'notification') and (filter('azure_tag_env', 'prod-us') or filter('azure_tag_env', 'prod-eu'))
secretKey: XXX
services:
- microsoft.sql/servers/elasticpools
subscriptions:
- sub-guid-here
tenantId: ZZZ
Arguments
app_id
- (Required) Azure application ID for the Splunk Observability Cloud app. To learn how to get this ID, see the topic Connect to Microsoft Azure in the product documentation.enabled
- (Required) Whether the integration is enabled.custom_namespaces_per_service
- (Optional) Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parametersync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces.namespaces
- (Required) The additional namespaces.service
- (Required) The name of the service.
environment
(Optional) What type of Azure integration this is. The allowed values are\"azure_us_government\"
and\"azure\"
. Defaults to\"azure\"
.name
- (Required) Name of the integration.named_token
- (Optional) Name of the org token to be used for data ingestion. If not specified then default access token is used.poll_rate
- (Optional) Azure poll rate (in seconds). Value between60
and600
. Default:300
.resource_filter_rules
- (Optional) List of rules for filtering Azure resources by their tags.filter_source
- (Required) Expression that selects the data that Splunk Observability Cloud should sync for the resource associated with this sync rule. The expression uses the syntax defined for the SignalFlowfilter()
function. The source of each filter rule must be in the form filter(‘key’, ‘value’). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix.
secret_key
- (Required) Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant ID. To learn how to get this ID, see the topic Connect to Microsoft Azure in the product documentation.services
- (Required) List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Can be an empty list to import data for all supported services. See Microsoft Azure services for a list of valid values.subscriptions
- (Required) List of Azure subscriptions that Splunk Observability Cloud should monitor.sync_guest_os_namespaces
- (Optional) If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested. Defaults to false.import_azure_monitor
- (Optional) If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.tenant_id
(Required) Azure ID of the Azure tenant. To learn how to get this ID, see the topic Connect to Microsoft Azure in the product documentation.
Attributes
In a addition to all arguments above, the following attributes are exported:
id
- The ID of the integration.
Create Integration Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Integration(name: string, args: IntegrationArgs, opts?: CustomResourceOptions);
@overload
def Integration(resource_name: str,
args: IntegrationArgs,
opts: Optional[ResourceOptions] = None)
@overload
def Integration(resource_name: str,
opts: Optional[ResourceOptions] = None,
secret_key: Optional[str] = None,
app_id: Optional[str] = None,
tenant_id: Optional[str] = None,
enabled: Optional[bool] = None,
subscriptions: Optional[Sequence[str]] = None,
services: Optional[Sequence[str]] = None,
name: Optional[str] = None,
named_token: Optional[str] = None,
poll_rate: Optional[int] = None,
resource_filter_rules: Optional[Sequence[IntegrationResourceFilterRuleArgs]] = None,
additional_services: Optional[Sequence[str]] = None,
import_azure_monitor: Optional[bool] = None,
environment: Optional[str] = None,
sync_guest_os_namespaces: Optional[bool] = None,
custom_namespaces_per_services: Optional[Sequence[IntegrationCustomNamespacesPerServiceArgs]] = None)
func NewIntegration(ctx *Context, name string, args IntegrationArgs, opts ...ResourceOption) (*Integration, error)
public Integration(string name, IntegrationArgs args, CustomResourceOptions? opts = null)
public Integration(String name, IntegrationArgs args)
public Integration(String name, IntegrationArgs args, CustomResourceOptions options)
type: signalfx:azure:Integration
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args IntegrationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args IntegrationArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args IntegrationArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args IntegrationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args IntegrationArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Example
The following reference example uses placeholder values for all input properties.
var signalfxIntegrationResource = new SignalFx.Azure.Integration("signalfxIntegrationResource", new()
{
SecretKey = "string",
AppId = "string",
TenantId = "string",
Enabled = false,
Subscriptions = new[]
{
"string",
},
Services = new[]
{
"string",
},
Name = "string",
NamedToken = "string",
PollRate = 0,
ResourceFilterRules = new[]
{
new SignalFx.Azure.Inputs.IntegrationResourceFilterRuleArgs
{
FilterSource = "string",
},
},
AdditionalServices = new[]
{
"string",
},
ImportAzureMonitor = false,
Environment = "string",
SyncGuestOsNamespaces = false,
CustomNamespacesPerServices = new[]
{
new SignalFx.Azure.Inputs.IntegrationCustomNamespacesPerServiceArgs
{
Namespaces = new[]
{
"string",
},
Service = "string",
},
},
});
example, err := azure.NewIntegration(ctx, "signalfxIntegrationResource", &azure.IntegrationArgs{
SecretKey: pulumi.String("string"),
AppId: pulumi.String("string"),
TenantId: pulumi.String("string"),
Enabled: pulumi.Bool(false),
Subscriptions: pulumi.StringArray{
pulumi.String("string"),
},
Services: pulumi.StringArray{
pulumi.String("string"),
},
Name: pulumi.String("string"),
NamedToken: pulumi.String("string"),
PollRate: pulumi.Int(0),
ResourceFilterRules: azure.IntegrationResourceFilterRuleArray{
&azure.IntegrationResourceFilterRuleArgs{
FilterSource: pulumi.String("string"),
},
},
AdditionalServices: pulumi.StringArray{
pulumi.String("string"),
},
ImportAzureMonitor: pulumi.Bool(false),
Environment: pulumi.String("string"),
SyncGuestOsNamespaces: pulumi.Bool(false),
CustomNamespacesPerServices: azure.IntegrationCustomNamespacesPerServiceArray{
&azure.IntegrationCustomNamespacesPerServiceArgs{
Namespaces: pulumi.StringArray{
pulumi.String("string"),
},
Service: pulumi.String("string"),
},
},
})
var signalfxIntegrationResource = new Integration("signalfxIntegrationResource", IntegrationArgs.builder()
.secretKey("string")
.appId("string")
.tenantId("string")
.enabled(false)
.subscriptions("string")
.services("string")
.name("string")
.namedToken("string")
.pollRate(0)
.resourceFilterRules(IntegrationResourceFilterRuleArgs.builder()
.filterSource("string")
.build())
.additionalServices("string")
.importAzureMonitor(false)
.environment("string")
.syncGuestOsNamespaces(false)
.customNamespacesPerServices(IntegrationCustomNamespacesPerServiceArgs.builder()
.namespaces("string")
.service("string")
.build())
.build());
signalfx_integration_resource = signalfx.azure.Integration("signalfxIntegrationResource",
secret_key="string",
app_id="string",
tenant_id="string",
enabled=False,
subscriptions=["string"],
services=["string"],
name="string",
named_token="string",
poll_rate=0,
resource_filter_rules=[signalfx.azure.IntegrationResourceFilterRuleArgs(
filter_source="string",
)],
additional_services=["string"],
import_azure_monitor=False,
environment="string",
sync_guest_os_namespaces=False,
custom_namespaces_per_services=[signalfx.azure.IntegrationCustomNamespacesPerServiceArgs(
namespaces=["string"],
service="string",
)])
const signalfxIntegrationResource = new signalfx.azure.Integration("signalfxIntegrationResource", {
secretKey: "string",
appId: "string",
tenantId: "string",
enabled: false,
subscriptions: ["string"],
services: ["string"],
name: "string",
namedToken: "string",
pollRate: 0,
resourceFilterRules: [{
filterSource: "string",
}],
additionalServices: ["string"],
importAzureMonitor: false,
environment: "string",
syncGuestOsNamespaces: false,
customNamespacesPerServices: [{
namespaces: ["string"],
service: "string",
}],
});
type: signalfx:azure:Integration
properties:
additionalServices:
- string
appId: string
customNamespacesPerServices:
- namespaces:
- string
service: string
enabled: false
environment: string
importAzureMonitor: false
name: string
namedToken: string
pollRate: 0
resourceFilterRules:
- filterSource: string
secretKey: string
services:
- string
subscriptions:
- string
syncGuestOsNamespaces: false
tenantId: string
Integration Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The Integration resource accepts the following input properties:
- App
Id string - Azure application ID for the Splunk Observability Cloud app.
- Enabled bool
- Whether the integration is enabled or not
- Secret
Key string - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- Services List<string>
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- Subscriptions List<string>
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- Tenant
Id string - Azure ID of the Azure tenant.
- Additional
Services List<string> - Additional Azure resource types that you want to sync with Observability Cloud.
- Custom
Namespaces List<Pulumi.Per Services Signal Fx. Azure. Inputs. Integration Custom Namespaces Per Service> - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - Environment string
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- Import
Azure boolMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- Name string
- Name of the integration
- Named
Token string - A named token to use for ingest
- Poll
Rate int - Azure poll rate (in seconds). Between
60
and600
. - Resource
Filter List<Pulumi.Rules Signal Fx. Azure. Inputs. Integration Resource Filter Rule> - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- Sync
Guest boolOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- App
Id string - Azure application ID for the Splunk Observability Cloud app.
- Enabled bool
- Whether the integration is enabled or not
- Secret
Key string - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- Services []string
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- Subscriptions []string
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- Tenant
Id string - Azure ID of the Azure tenant.
- Additional
Services []string - Additional Azure resource types that you want to sync with Observability Cloud.
- Custom
Namespaces []IntegrationPer Services Custom Namespaces Per Service Args - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - Environment string
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- Import
Azure boolMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- Name string
- Name of the integration
- Named
Token string - A named token to use for ingest
- Poll
Rate int - Azure poll rate (in seconds). Between
60
and600
. - Resource
Filter []IntegrationRules Resource Filter Rule Args - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- Sync
Guest boolOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- app
Id String - Azure application ID for the Splunk Observability Cloud app.
- enabled Boolean
- Whether the integration is enabled or not
- secret
Key String - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services List<String>
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions List<String>
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- tenant
Id String - Azure ID of the Azure tenant.
- additional
Services List<String> - Additional Azure resource types that you want to sync with Observability Cloud.
- custom
Namespaces List<IntegrationPer Services Custom Namespaces Per Service> - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - environment String
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import
Azure BooleanMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name String
- Name of the integration
- named
Token String - A named token to use for ingest
- poll
Rate Integer - Azure poll rate (in seconds). Between
60
and600
. - resource
Filter List<IntegrationRules Resource Filter Rule> - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- sync
Guest BooleanOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- app
Id string - Azure application ID for the Splunk Observability Cloud app.
- enabled boolean
- Whether the integration is enabled or not
- secret
Key string - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services string[]
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions string[]
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- tenant
Id string - Azure ID of the Azure tenant.
- additional
Services string[] - Additional Azure resource types that you want to sync with Observability Cloud.
- custom
Namespaces IntegrationPer Services Custom Namespaces Per Service[] - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - environment string
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import
Azure booleanMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name string
- Name of the integration
- named
Token string - A named token to use for ingest
- poll
Rate number - Azure poll rate (in seconds). Between
60
and600
. - resource
Filter IntegrationRules Resource Filter Rule[] - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- sync
Guest booleanOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- app_
id str - Azure application ID for the Splunk Observability Cloud app.
- enabled bool
- Whether the integration is enabled or not
- secret_
key str - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services Sequence[str]
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions Sequence[str]
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- tenant_
id str - Azure ID of the Azure tenant.
- additional_
services Sequence[str] - Additional Azure resource types that you want to sync with Observability Cloud.
- custom_
namespaces_ Sequence[Integrationper_ services Custom Namespaces Per Service Args] - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - environment str
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import_
azure_ boolmonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name str
- Name of the integration
- named_
token str - A named token to use for ingest
- poll_
rate int - Azure poll rate (in seconds). Between
60
and600
. - resource_
filter_ Sequence[Integrationrules Resource Filter Rule Args] - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- sync_
guest_ boolos_ namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- app
Id String - Azure application ID for the Splunk Observability Cloud app.
- enabled Boolean
- Whether the integration is enabled or not
- secret
Key String - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services List<String>
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions List<String>
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- tenant
Id String - Azure ID of the Azure tenant.
- additional
Services List<String> - Additional Azure resource types that you want to sync with Observability Cloud.
- custom
Namespaces List<Property Map>Per Services - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - environment String
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import
Azure BooleanMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name String
- Name of the integration
- named
Token String - A named token to use for ingest
- poll
Rate Number - Azure poll rate (in seconds). Between
60
and600
. - resource
Filter List<Property Map>Rules - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- sync
Guest BooleanOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
Outputs
All input properties are implicitly available as output properties. Additionally, the Integration resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing Integration Resource
Get an existing Integration resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: IntegrationState, opts?: CustomResourceOptions): Integration
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
additional_services: Optional[Sequence[str]] = None,
app_id: Optional[str] = None,
custom_namespaces_per_services: Optional[Sequence[IntegrationCustomNamespacesPerServiceArgs]] = None,
enabled: Optional[bool] = None,
environment: Optional[str] = None,
import_azure_monitor: Optional[bool] = None,
name: Optional[str] = None,
named_token: Optional[str] = None,
poll_rate: Optional[int] = None,
resource_filter_rules: Optional[Sequence[IntegrationResourceFilterRuleArgs]] = None,
secret_key: Optional[str] = None,
services: Optional[Sequence[str]] = None,
subscriptions: Optional[Sequence[str]] = None,
sync_guest_os_namespaces: Optional[bool] = None,
tenant_id: Optional[str] = None) -> Integration
func GetIntegration(ctx *Context, name string, id IDInput, state *IntegrationState, opts ...ResourceOption) (*Integration, error)
public static Integration Get(string name, Input<string> id, IntegrationState? state, CustomResourceOptions? opts = null)
public static Integration get(String name, Output<String> id, IntegrationState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Additional
Services List<string> - Additional Azure resource types that you want to sync with Observability Cloud.
- App
Id string - Azure application ID for the Splunk Observability Cloud app.
- Custom
Namespaces List<Pulumi.Per Services Signal Fx. Azure. Inputs. Integration Custom Namespaces Per Service> - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - Enabled bool
- Whether the integration is enabled or not
- Environment string
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- Import
Azure boolMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- Name string
- Name of the integration
- Named
Token string - A named token to use for ingest
- Poll
Rate int - Azure poll rate (in seconds). Between
60
and600
. - Resource
Filter List<Pulumi.Rules Signal Fx. Azure. Inputs. Integration Resource Filter Rule> - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- Secret
Key string - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- Services List<string>
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- Subscriptions List<string>
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- Sync
Guest boolOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- Tenant
Id string - Azure ID of the Azure tenant.
- Additional
Services []string - Additional Azure resource types that you want to sync with Observability Cloud.
- App
Id string - Azure application ID for the Splunk Observability Cloud app.
- Custom
Namespaces []IntegrationPer Services Custom Namespaces Per Service Args - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - Enabled bool
- Whether the integration is enabled or not
- Environment string
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- Import
Azure boolMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- Name string
- Name of the integration
- Named
Token string - A named token to use for ingest
- Poll
Rate int - Azure poll rate (in seconds). Between
60
and600
. - Resource
Filter []IntegrationRules Resource Filter Rule Args - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- Secret
Key string - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- Services []string
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- Subscriptions []string
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- Sync
Guest boolOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- Tenant
Id string - Azure ID of the Azure tenant.
- additional
Services List<String> - Additional Azure resource types that you want to sync with Observability Cloud.
- app
Id String - Azure application ID for the Splunk Observability Cloud app.
- custom
Namespaces List<IntegrationPer Services Custom Namespaces Per Service> - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - enabled Boolean
- Whether the integration is enabled or not
- environment String
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import
Azure BooleanMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name String
- Name of the integration
- named
Token String - A named token to use for ingest
- poll
Rate Integer - Azure poll rate (in seconds). Between
60
and600
. - resource
Filter List<IntegrationRules Resource Filter Rule> - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- secret
Key String - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services List<String>
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions List<String>
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- sync
Guest BooleanOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- tenant
Id String - Azure ID of the Azure tenant.
- additional
Services string[] - Additional Azure resource types that you want to sync with Observability Cloud.
- app
Id string - Azure application ID for the Splunk Observability Cloud app.
- custom
Namespaces IntegrationPer Services Custom Namespaces Per Service[] - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - enabled boolean
- Whether the integration is enabled or not
- environment string
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import
Azure booleanMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name string
- Name of the integration
- named
Token string - A named token to use for ingest
- poll
Rate number - Azure poll rate (in seconds). Between
60
and600
. - resource
Filter IntegrationRules Resource Filter Rule[] - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- secret
Key string - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services string[]
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions string[]
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- sync
Guest booleanOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- tenant
Id string - Azure ID of the Azure tenant.
- additional_
services Sequence[str] - Additional Azure resource types that you want to sync with Observability Cloud.
- app_
id str - Azure application ID for the Splunk Observability Cloud app.
- custom_
namespaces_ Sequence[Integrationper_ services Custom Namespaces Per Service Args] - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - enabled bool
- Whether the integration is enabled or not
- environment str
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import_
azure_ boolmonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name str
- Name of the integration
- named_
token str - A named token to use for ingest
- poll_
rate int - Azure poll rate (in seconds). Between
60
and600
. - resource_
filter_ Sequence[Integrationrules Resource Filter Rule Args] - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- secret_
key str - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services Sequence[str]
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions Sequence[str]
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- sync_
guest_ boolos_ namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- tenant_
id str - Azure ID of the Azure tenant.
- additional
Services List<String> - Additional Azure resource types that you want to sync with Observability Cloud.
- app
Id String - Azure application ID for the Splunk Observability Cloud app.
- custom
Namespaces List<Property Map>Per Services - Allows for more fine-grained control of syncing of custom namespaces, should the boolean convenience parameter
sync_guest_os_namespaces
be not enough. The customer may specify a map of services to custom namespaces. If they do so, for each service which is a key in this map, we will attempt to sync metrics from namespaces in the value list in addition to the default namespaces. - enabled Boolean
- Whether the integration is enabled or not
- environment String
- what type of Azure integration this is. The allowed values are
"azure_us_government"
and"azure"
. Defaults to"azure"
- import
Azure BooleanMonitor - If enabled, Splunk Observability Cloud will sync also Azure Monitor data. If disabled, Splunk Observability Cloud will import only metadata. Defaults to true.
- name String
- Name of the integration
- named
Token String - A named token to use for ingest
- poll
Rate Number - Azure poll rate (in seconds). Between
60
and600
. - resource
Filter List<Property Map>Rules - List of rules for filtering Azure resources by their tags. The source of each filter rule must be in the form filter('key', 'value'). You can join multiple filter statements using the and and or operators. Referenced keys are limited to tags and must start with the azure_tag_ prefix..
- secret
Key String - Azure secret key that associates the Splunk Observability Cloud app in Azure with the Azure tenant.
- services List<String>
- List of Microsoft Azure service names for the Azure services you want Splunk Observability Cloud to monitor. Splunk Observability Cloud only supports certain services, and if you specify an unsupported one, you receive an API error.
- subscriptions List<String>
- List of Azure subscriptions that Splunk Observability Cloud should monitor.
- sync
Guest BooleanOs Namespaces - If enabled, Splunk Observability Cloud will try to sync additional namespaces for VMs (including VMs in scale sets): telegraf/mem, telegraf/cpu, azure.vm.windows.guest (these are namespaces recommended by Azure when enabling their Diagnostic Extension). If there are no metrics there, no new datapoints will be ingested.
- tenant
Id String - Azure ID of the Azure tenant.
Supporting Types
IntegrationCustomNamespacesPerService, IntegrationCustomNamespacesPerServiceArgs
- Namespaces List<string>
- The namespaces to sync
- Service string
- The name of the service
- Namespaces []string
- The namespaces to sync
- Service string
- The name of the service
- namespaces List<String>
- The namespaces to sync
- service String
- The name of the service
- namespaces string[]
- The namespaces to sync
- service string
- The name of the service
- namespaces Sequence[str]
- The namespaces to sync
- service str
- The name of the service
- namespaces List<String>
- The namespaces to sync
- service String
- The name of the service
IntegrationResourceFilterRule, IntegrationResourceFilterRuleArgs
- Filter
Source string
- Filter
Source string
- filter
Source String
- filter
Source string
- filter_
source str
- filter
Source String
Package Details
- Repository
- SignalFx pulumi/pulumi-signalfx
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
signalfx
Terraform Provider.