sysdig.MonitorTeam
Explore with Pulumi AI
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as sysdig from "@pulumi/sysdig";
const me = sysdig.getCurrentUser({});
const customRole = sysdig.getCustomRole({
name: "CustomRoleName",
});
const devops = new sysdig.MonitorTeam("devops", {
entrypoints: [{
type: "DashboardTemplates",
selection: "view.net.http",
}],
userRoles: [
{
email: me.then(me => me.email),
role: "ROLE_TEAM_MANAGER",
},
{
email: "john.doe@example.com",
role: "ROLE_TEAM_STANDARD",
},
{
email: "john.smith@example.com",
role: customRole.then(customRole => customRole.id),
},
],
filter: "kubernetes.namespace.name in (\"kube-system\") and kubernetes.deployment.name in (\"coredns\")",
prometheusRemoteWriteMetricsFilter: "kube_cluster_name in (\"test-cluster\", \"test-k8s-data\") and kube_deployment_name = \"coredns\" and my_metric starts with \"prefix\" and not my_metric contains \"prefix-test\"",
});
import pulumi
import pulumi_sysdig as sysdig
me = sysdig.get_current_user()
custom_role = sysdig.get_custom_role(name="CustomRoleName")
devops = sysdig.MonitorTeam("devops",
entrypoints=[{
"type": "DashboardTemplates",
"selection": "view.net.http",
}],
user_roles=[
{
"email": me.email,
"role": "ROLE_TEAM_MANAGER",
},
{
"email": "john.doe@example.com",
"role": "ROLE_TEAM_STANDARD",
},
{
"email": "john.smith@example.com",
"role": custom_role.id,
},
],
filter="kubernetes.namespace.name in (\"kube-system\") and kubernetes.deployment.name in (\"coredns\")",
prometheus_remote_write_metrics_filter="kube_cluster_name in (\"test-cluster\", \"test-k8s-data\") and kube_deployment_name = \"coredns\" and my_metric starts with \"prefix\" and not my_metric contains \"prefix-test\"")
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/sysdig/sysdig"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
me, err := sysdig.GetCurrentUser(ctx, &sysdig.GetCurrentUserArgs{}, nil)
if err != nil {
return err
}
customRole, err := sysdig.LookupCustomRole(ctx, &sysdig.LookupCustomRoleArgs{
Name: "CustomRoleName",
}, nil)
if err != nil {
return err
}
_, err = sysdig.NewMonitorTeam(ctx, "devops", &sysdig.MonitorTeamArgs{
Entrypoints: sysdig.MonitorTeamEntrypointArray{
&sysdig.MonitorTeamEntrypointArgs{
Type: pulumi.String("DashboardTemplates"),
Selection: pulumi.String("view.net.http"),
},
},
UserRoles: sysdig.MonitorTeamUserRoleArray{
&sysdig.MonitorTeamUserRoleArgs{
Email: pulumi.String(me.Email),
Role: pulumi.String("ROLE_TEAM_MANAGER"),
},
&sysdig.MonitorTeamUserRoleArgs{
Email: pulumi.String("john.doe@example.com"),
Role: pulumi.String("ROLE_TEAM_STANDARD"),
},
&sysdig.MonitorTeamUserRoleArgs{
Email: pulumi.String("john.smith@example.com"),
Role: pulumi.String(customRole.Id),
},
},
Filter: pulumi.String("kubernetes.namespace.name in (\"kube-system\") and kubernetes.deployment.name in (\"coredns\")"),
PrometheusRemoteWriteMetricsFilter: pulumi.String("kube_cluster_name in (\"test-cluster\", \"test-k8s-data\") and kube_deployment_name = \"coredns\" and my_metric starts with \"prefix\" and not my_metric contains \"prefix-test\""),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Sysdig = Pulumi.Sysdig;
return await Deployment.RunAsync(() =>
{
var me = Sysdig.GetCurrentUser.Invoke();
var customRole = Sysdig.GetCustomRole.Invoke(new()
{
Name = "CustomRoleName",
});
var devops = new Sysdig.MonitorTeam("devops", new()
{
Entrypoints = new[]
{
new Sysdig.Inputs.MonitorTeamEntrypointArgs
{
Type = "DashboardTemplates",
Selection = "view.net.http",
},
},
UserRoles = new[]
{
new Sysdig.Inputs.MonitorTeamUserRoleArgs
{
Email = me.Apply(getCurrentUserResult => getCurrentUserResult.Email),
Role = "ROLE_TEAM_MANAGER",
},
new Sysdig.Inputs.MonitorTeamUserRoleArgs
{
Email = "john.doe@example.com",
Role = "ROLE_TEAM_STANDARD",
},
new Sysdig.Inputs.MonitorTeamUserRoleArgs
{
Email = "john.smith@example.com",
Role = customRole.Apply(getCustomRoleResult => getCustomRoleResult.Id),
},
},
Filter = "kubernetes.namespace.name in (\"kube-system\") and kubernetes.deployment.name in (\"coredns\")",
PrometheusRemoteWriteMetricsFilter = "kube_cluster_name in (\"test-cluster\", \"test-k8s-data\") and kube_deployment_name = \"coredns\" and my_metric starts with \"prefix\" and not my_metric contains \"prefix-test\"",
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.sysdig.SysdigFunctions;
import com.pulumi.sysdig.inputs.GetCurrentUserArgs;
import com.pulumi.sysdig.inputs.GetCustomRoleArgs;
import com.pulumi.sysdig.MonitorTeam;
import com.pulumi.sysdig.MonitorTeamArgs;
import com.pulumi.sysdig.inputs.MonitorTeamEntrypointArgs;
import com.pulumi.sysdig.inputs.MonitorTeamUserRoleArgs;
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) {
final var me = SysdigFunctions.getCurrentUser();
final var customRole = SysdigFunctions.getCustomRole(GetCustomRoleArgs.builder()
.name("CustomRoleName")
.build());
var devops = new MonitorTeam("devops", MonitorTeamArgs.builder()
.entrypoints(MonitorTeamEntrypointArgs.builder()
.type("DashboardTemplates")
.selection("view.net.http")
.build())
.userRoles(
MonitorTeamUserRoleArgs.builder()
.email(me.applyValue(getCurrentUserResult -> getCurrentUserResult.email()))
.role("ROLE_TEAM_MANAGER")
.build(),
MonitorTeamUserRoleArgs.builder()
.email("john.doe@example.com")
.role("ROLE_TEAM_STANDARD")
.build(),
MonitorTeamUserRoleArgs.builder()
.email("john.smith@example.com")
.role(customRole.applyValue(getCustomRoleResult -> getCustomRoleResult.id()))
.build())
.filter("kubernetes.namespace.name in (\"kube-system\") and kubernetes.deployment.name in (\"coredns\")")
.prometheusRemoteWriteMetricsFilter("kube_cluster_name in (\"test-cluster\", \"test-k8s-data\") and kube_deployment_name = \"coredns\" and my_metric starts with \"prefix\" and not my_metric contains \"prefix-test\"")
.build());
}
}
resources:
devops:
type: sysdig:MonitorTeam
properties:
entrypoints:
- type: DashboardTemplates
selection: view.net.http
userRoles:
- email: ${me.email}
role: ROLE_TEAM_MANAGER
- email: john.doe@example.com
role: ROLE_TEAM_STANDARD
- email: john.smith@example.com
role: ${customRole.id}
filter: kubernetes.namespace.name in ("kube-system") and kubernetes.deployment.name in ("coredns")
prometheusRemoteWriteMetricsFilter: kube_cluster_name in ("test-cluster", "test-k8s-data") and kube_deployment_name = "coredns" and my_metric starts with "prefix" and not my_metric contains "prefix-test"
variables:
me:
fn::invoke:
function: sysdig:getCurrentUser
arguments: {}
customRole:
fn::invoke:
function: sysdig:getCustomRole
arguments:
name: CustomRoleName
Create MonitorTeam Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new MonitorTeam(name: string, args: MonitorTeamArgs, opts?: CustomResourceOptions);
@overload
def MonitorTeam(resource_name: str,
args: MonitorTeamArgs,
opts: Optional[ResourceOptions] = None)
@overload
def MonitorTeam(resource_name: str,
opts: Optional[ResourceOptions] = None,
entrypoints: Optional[Sequence[MonitorTeamEntrypointArgs]] = None,
filter: Optional[str] = None,
monitor_team_id: Optional[str] = None,
can_use_sysdig_capture: Optional[bool] = None,
default_team: Optional[bool] = None,
description: Optional[str] = None,
enable_ibm_platform_metrics: Optional[bool] = None,
can_use_aws_data: Optional[bool] = None,
can_use_agent_cli: Optional[bool] = None,
ibm_platform_metrics: Optional[str] = None,
can_see_infrastructure_events: Optional[bool] = None,
name: Optional[str] = None,
prometheus_remote_write_metrics_filter: Optional[str] = None,
scope_by: Optional[str] = None,
theme: Optional[str] = None,
timeouts: Optional[MonitorTeamTimeoutsArgs] = None,
user_roles: Optional[Sequence[MonitorTeamUserRoleArgs]] = None)
func NewMonitorTeam(ctx *Context, name string, args MonitorTeamArgs, opts ...ResourceOption) (*MonitorTeam, error)
public MonitorTeam(string name, MonitorTeamArgs args, CustomResourceOptions? opts = null)
public MonitorTeam(String name, MonitorTeamArgs args)
public MonitorTeam(String name, MonitorTeamArgs args, CustomResourceOptions options)
type: sysdig:MonitorTeam
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 MonitorTeamArgs
- 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 MonitorTeamArgs
- 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 MonitorTeamArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args MonitorTeamArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args MonitorTeamArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var monitorTeamResource = new Sysdig.MonitorTeam("monitorTeamResource", new()
{
Entrypoints = new[]
{
new Sysdig.Inputs.MonitorTeamEntrypointArgs
{
Type = "string",
Selection = "string",
},
},
Filter = "string",
MonitorTeamId = "string",
CanUseSysdigCapture = false,
DefaultTeam = false,
Description = "string",
EnableIbmPlatformMetrics = false,
CanUseAwsData = false,
CanUseAgentCli = false,
IbmPlatformMetrics = "string",
CanSeeInfrastructureEvents = false,
Name = "string",
PrometheusRemoteWriteMetricsFilter = "string",
ScopeBy = "string",
Theme = "string",
Timeouts = new Sysdig.Inputs.MonitorTeamTimeoutsArgs
{
Create = "string",
Delete = "string",
Read = "string",
Update = "string",
},
UserRoles = new[]
{
new Sysdig.Inputs.MonitorTeamUserRoleArgs
{
Email = "string",
Role = "string",
},
},
});
example, err := sysdig.NewMonitorTeam(ctx, "monitorTeamResource", &sysdig.MonitorTeamArgs{
Entrypoints: sysdig.MonitorTeamEntrypointArray{
&sysdig.MonitorTeamEntrypointArgs{
Type: pulumi.String("string"),
Selection: pulumi.String("string"),
},
},
Filter: pulumi.String("string"),
MonitorTeamId: pulumi.String("string"),
CanUseSysdigCapture: pulumi.Bool(false),
DefaultTeam: pulumi.Bool(false),
Description: pulumi.String("string"),
EnableIbmPlatformMetrics: pulumi.Bool(false),
CanUseAwsData: pulumi.Bool(false),
CanUseAgentCli: pulumi.Bool(false),
IbmPlatformMetrics: pulumi.String("string"),
CanSeeInfrastructureEvents: pulumi.Bool(false),
Name: pulumi.String("string"),
PrometheusRemoteWriteMetricsFilter: pulumi.String("string"),
ScopeBy: pulumi.String("string"),
Theme: pulumi.String("string"),
Timeouts: &sysdig.MonitorTeamTimeoutsArgs{
Create: pulumi.String("string"),
Delete: pulumi.String("string"),
Read: pulumi.String("string"),
Update: pulumi.String("string"),
},
UserRoles: sysdig.MonitorTeamUserRoleArray{
&sysdig.MonitorTeamUserRoleArgs{
Email: pulumi.String("string"),
Role: pulumi.String("string"),
},
},
})
var monitorTeamResource = new MonitorTeam("monitorTeamResource", MonitorTeamArgs.builder()
.entrypoints(MonitorTeamEntrypointArgs.builder()
.type("string")
.selection("string")
.build())
.filter("string")
.monitorTeamId("string")
.canUseSysdigCapture(false)
.defaultTeam(false)
.description("string")
.enableIbmPlatformMetrics(false)
.canUseAwsData(false)
.canUseAgentCli(false)
.ibmPlatformMetrics("string")
.canSeeInfrastructureEvents(false)
.name("string")
.prometheusRemoteWriteMetricsFilter("string")
.scopeBy("string")
.theme("string")
.timeouts(MonitorTeamTimeoutsArgs.builder()
.create("string")
.delete("string")
.read("string")
.update("string")
.build())
.userRoles(MonitorTeamUserRoleArgs.builder()
.email("string")
.role("string")
.build())
.build());
monitor_team_resource = sysdig.MonitorTeam("monitorTeamResource",
entrypoints=[{
"type": "string",
"selection": "string",
}],
filter="string",
monitor_team_id="string",
can_use_sysdig_capture=False,
default_team=False,
description="string",
enable_ibm_platform_metrics=False,
can_use_aws_data=False,
can_use_agent_cli=False,
ibm_platform_metrics="string",
can_see_infrastructure_events=False,
name="string",
prometheus_remote_write_metrics_filter="string",
scope_by="string",
theme="string",
timeouts={
"create": "string",
"delete": "string",
"read": "string",
"update": "string",
},
user_roles=[{
"email": "string",
"role": "string",
}])
const monitorTeamResource = new sysdig.MonitorTeam("monitorTeamResource", {
entrypoints: [{
type: "string",
selection: "string",
}],
filter: "string",
monitorTeamId: "string",
canUseSysdigCapture: false,
defaultTeam: false,
description: "string",
enableIbmPlatformMetrics: false,
canUseAwsData: false,
canUseAgentCli: false,
ibmPlatformMetrics: "string",
canSeeInfrastructureEvents: false,
name: "string",
prometheusRemoteWriteMetricsFilter: "string",
scopeBy: "string",
theme: "string",
timeouts: {
create: "string",
"delete": "string",
read: "string",
update: "string",
},
userRoles: [{
email: "string",
role: "string",
}],
});
type: sysdig:MonitorTeam
properties:
canSeeInfrastructureEvents: false
canUseAgentCli: false
canUseAwsData: false
canUseSysdigCapture: false
defaultTeam: false
description: string
enableIbmPlatformMetrics: false
entrypoints:
- selection: string
type: string
filter: string
ibmPlatformMetrics: string
monitorTeamId: string
name: string
prometheusRemoteWriteMetricsFilter: string
scopeBy: string
theme: string
timeouts:
create: string
delete: string
read: string
update: string
userRoles:
- email: string
role: string
MonitorTeam Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The MonitorTeam resource accepts the following input properties:
- Entrypoints
List<Monitor
Team Entrypoint> - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- Can
See boolInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - Can
Use boolAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - Can
Use boolAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - Can
Use boolSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - Default
Team bool - Description string
- A description of the team.
- Enable
Ibm boolPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- Filter string
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- Ibm
Platform stringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- Monitor
Team stringId - ID of the created team.
- Name string
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- Prometheus
Remote stringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- Scope
By string - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - Theme string
- Colour of the team. Default:
#05C391
. - Timeouts
Monitor
Team Timeouts - User
Roles List<MonitorTeam User Role>
- Entrypoints
[]Monitor
Team Entrypoint Args - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- Can
See boolInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - Can
Use boolAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - Can
Use boolAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - Can
Use boolSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - Default
Team bool - Description string
- A description of the team.
- Enable
Ibm boolPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- Filter string
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- Ibm
Platform stringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- Monitor
Team stringId - ID of the created team.
- Name string
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- Prometheus
Remote stringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- Scope
By string - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - Theme string
- Colour of the team. Default:
#05C391
. - Timeouts
Monitor
Team Timeouts Args - User
Roles []MonitorTeam User Role Args
- entrypoints
List<Monitor
Team Entrypoint> - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- can
See BooleanInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can
Use BooleanAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can
Use BooleanAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can
Use BooleanSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default
Team Boolean - description String
- A description of the team.
- enable
Ibm BooleanPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- filter String
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm
Platform StringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor
Team StringId - ID of the created team.
- name String
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus
Remote StringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope
By String - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme String
- Colour of the team. Default:
#05C391
. - timeouts
Monitor
Team Timeouts - user
Roles List<MonitorTeam User Role>
- entrypoints
Monitor
Team Entrypoint[] - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- can
See booleanInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can
Use booleanAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can
Use booleanAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can
Use booleanSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default
Team boolean - description string
- A description of the team.
- enable
Ibm booleanPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- filter string
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm
Platform stringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor
Team stringId - ID of the created team.
- name string
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus
Remote stringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope
By string - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme string
- Colour of the team. Default:
#05C391
. - timeouts
Monitor
Team Timeouts - user
Roles MonitorTeam User Role[]
- entrypoints
Sequence[Monitor
Team Entrypoint Args] - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- can_
see_ boolinfrastructure_ events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can_
use_ boolagent_ cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can_
use_ boolaws_ data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can_
use_ boolsysdig_ capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default_
team bool - description str
- A description of the team.
- enable_
ibm_ boolplatform_ metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- filter str
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm_
platform_ strmetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor_
team_ strid - ID of the created team.
- name str
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus_
remote_ strwrite_ metrics_ filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope_
by str - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme str
- Colour of the team. Default:
#05C391
. - timeouts
Monitor
Team Timeouts Args - user_
roles Sequence[MonitorTeam User Role Args]
- entrypoints List<Property Map>
- Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- can
See BooleanInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can
Use BooleanAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can
Use BooleanAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can
Use BooleanSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default
Team Boolean - description String
- A description of the team.
- enable
Ibm BooleanPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- filter String
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm
Platform StringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor
Team StringId - ID of the created team.
- name String
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus
Remote StringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope
By String - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme String
- Colour of the team. Default:
#05C391
. - timeouts Property Map
- user
Roles List<Property Map>
Outputs
All input properties are implicitly available as output properties. Additionally, the MonitorTeam resource produces the following output properties:
Look up Existing MonitorTeam Resource
Get an existing MonitorTeam 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?: MonitorTeamState, opts?: CustomResourceOptions): MonitorTeam
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
can_see_infrastructure_events: Optional[bool] = None,
can_use_agent_cli: Optional[bool] = None,
can_use_aws_data: Optional[bool] = None,
can_use_sysdig_capture: Optional[bool] = None,
default_team: Optional[bool] = None,
description: Optional[str] = None,
enable_ibm_platform_metrics: Optional[bool] = None,
entrypoints: Optional[Sequence[MonitorTeamEntrypointArgs]] = None,
filter: Optional[str] = None,
ibm_platform_metrics: Optional[str] = None,
monitor_team_id: Optional[str] = None,
name: Optional[str] = None,
prometheus_remote_write_metrics_filter: Optional[str] = None,
scope_by: Optional[str] = None,
theme: Optional[str] = None,
timeouts: Optional[MonitorTeamTimeoutsArgs] = None,
user_roles: Optional[Sequence[MonitorTeamUserRoleArgs]] = None,
version: Optional[float] = None) -> MonitorTeam
func GetMonitorTeam(ctx *Context, name string, id IDInput, state *MonitorTeamState, opts ...ResourceOption) (*MonitorTeam, error)
public static MonitorTeam Get(string name, Input<string> id, MonitorTeamState? state, CustomResourceOptions? opts = null)
public static MonitorTeam get(String name, Output<String> id, MonitorTeamState state, CustomResourceOptions options)
resources: _: type: sysdig:MonitorTeam get: id: ${id}
- 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.
- Can
See boolInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - Can
Use boolAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - Can
Use boolAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - Can
Use boolSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - Default
Team bool - Description string
- A description of the team.
- Enable
Ibm boolPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- Entrypoints
List<Monitor
Team Entrypoint> - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- Filter string
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- Ibm
Platform stringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- Monitor
Team stringId - ID of the created team.
- Name string
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- Prometheus
Remote stringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- Scope
By string - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - Theme string
- Colour of the team. Default:
#05C391
. - Timeouts
Monitor
Team Timeouts - User
Roles List<MonitorTeam User Role> - Version double
- Current version of the resource.
- Can
See boolInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - Can
Use boolAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - Can
Use boolAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - Can
Use boolSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - Default
Team bool - Description string
- A description of the team.
- Enable
Ibm boolPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- Entrypoints
[]Monitor
Team Entrypoint Args - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- Filter string
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- Ibm
Platform stringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- Monitor
Team stringId - ID of the created team.
- Name string
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- Prometheus
Remote stringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- Scope
By string - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - Theme string
- Colour of the team. Default:
#05C391
. - Timeouts
Monitor
Team Timeouts Args - User
Roles []MonitorTeam User Role Args - Version float64
- Current version of the resource.
- can
See BooleanInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can
Use BooleanAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can
Use BooleanAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can
Use BooleanSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default
Team Boolean - description String
- A description of the team.
- enable
Ibm BooleanPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- entrypoints
List<Monitor
Team Entrypoint> - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- filter String
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm
Platform StringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor
Team StringId - ID of the created team.
- name String
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus
Remote StringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope
By String - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme String
- Colour of the team. Default:
#05C391
. - timeouts
Monitor
Team Timeouts - user
Roles List<MonitorTeam User Role> - version Double
- Current version of the resource.
- can
See booleanInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can
Use booleanAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can
Use booleanAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can
Use booleanSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default
Team boolean - description string
- A description of the team.
- enable
Ibm booleanPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- entrypoints
Monitor
Team Entrypoint[] - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- filter string
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm
Platform stringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor
Team stringId - ID of the created team.
- name string
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus
Remote stringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope
By string - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme string
- Colour of the team. Default:
#05C391
. - timeouts
Monitor
Team Timeouts - user
Roles MonitorTeam User Role[] - version number
- Current version of the resource.
- can_
see_ boolinfrastructure_ events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can_
use_ boolagent_ cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can_
use_ boolaws_ data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can_
use_ boolsysdig_ capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default_
team bool - description str
- A description of the team.
- enable_
ibm_ boolplatform_ metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- entrypoints
Sequence[Monitor
Team Entrypoint Args] - Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- filter str
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm_
platform_ strmetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor_
team_ strid - ID of the created team.
- name str
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus_
remote_ strwrite_ metrics_ filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope_
by str - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme str
- Colour of the team. Default:
#05C391
. - timeouts
Monitor
Team Timeouts Args - user_
roles Sequence[MonitorTeam User Role Args] - version float
- Current version of the resource.
- can
See BooleanInfrastructure Events - Enable this option to allow this team to view all Infrastructure and Custom Events from every user and agent. Otherwise, this team will only see infrastructure events sent specifically to this team. Default:
false
. - can
Use BooleanAgent Cli - Enable this option to give this team access to Using the Agent Console. Default:
true
. - can
Use BooleanAws Data - Enable this option to give this team access to AWS metrics and tags. All AWS data is made available, regardless of the team’s Scope. Default:
false
. - can
Use BooleanSysdig Capture - Defines if the team is able to create Sysdig Capture files. Default:
true
. - default
Team Boolean - description String
- A description of the team.
- enable
Ibm BooleanPlatform Metrics - (Optional) Enable Platform Metrics on IBM Cloud Monitoring.
- entrypoints List<Property Map>
- Main entry point for the current team in the product. See the Entrypoint argument reference section for more information.
- filter String
- Use this option to select which Agent Metrics data users of this team can view. Not setting it will allow users to see all Agent Metrics data.
- ibm
Platform StringMetrics - (Optional) Use this option to select which Platform Metrics data users of this team can view. Not setting it will allow users to see all Platform Metrics data.
- monitor
Team StringId - ID of the created team.
- name String
- The name of the Monitor Team. It must be unique and must not exist in Secure.
- prometheus
Remote StringWrite Metrics Filter - Use this option to select which Prometheus Remote Write data users of this team can view. Not setting it will allow users to see all Prometheus Remote Write data.
- scope
By String - Scope for the team, either
container
orhost
. Default:host
. If set tohost
, team members can see all host-level and container-level information. If set tocontainer
, team members can see only Container-level information. - theme String
- Colour of the team. Default:
#05C391
. - timeouts Property Map
- user
Roles List<Property Map> - version Number
- Current version of the resource.
Supporting Types
MonitorTeamEntrypoint, MonitorTeamEntrypointArgs
- Type string
- Main entrypoint for the team.
Valid options are:
Explore
,Dashboards
,Events
,Alerts
,Settings
,DashboardTemplates
,Advisor
. - Selection string
- Sets up the defined Dashboard name as entrypoint.
Warning: This field must only be added if the
type
isDashboards
, and the value is the numeric id of the selected dashboard, orDashboardTemplates
, and the value is the id (dotted name) of the selected dashboard template.
- Type string
- Main entrypoint for the team.
Valid options are:
Explore
,Dashboards
,Events
,Alerts
,Settings
,DashboardTemplates
,Advisor
. - Selection string
- Sets up the defined Dashboard name as entrypoint.
Warning: This field must only be added if the
type
isDashboards
, and the value is the numeric id of the selected dashboard, orDashboardTemplates
, and the value is the id (dotted name) of the selected dashboard template.
- type String
- Main entrypoint for the team.
Valid options are:
Explore
,Dashboards
,Events
,Alerts
,Settings
,DashboardTemplates
,Advisor
. - selection String
- Sets up the defined Dashboard name as entrypoint.
Warning: This field must only be added if the
type
isDashboards
, and the value is the numeric id of the selected dashboard, orDashboardTemplates
, and the value is the id (dotted name) of the selected dashboard template.
- type string
- Main entrypoint for the team.
Valid options are:
Explore
,Dashboards
,Events
,Alerts
,Settings
,DashboardTemplates
,Advisor
. - selection string
- Sets up the defined Dashboard name as entrypoint.
Warning: This field must only be added if the
type
isDashboards
, and the value is the numeric id of the selected dashboard, orDashboardTemplates
, and the value is the id (dotted name) of the selected dashboard template.
- type str
- Main entrypoint for the team.
Valid options are:
Explore
,Dashboards
,Events
,Alerts
,Settings
,DashboardTemplates
,Advisor
. - selection str
- Sets up the defined Dashboard name as entrypoint.
Warning: This field must only be added if the
type
isDashboards
, and the value is the numeric id of the selected dashboard, orDashboardTemplates
, and the value is the id (dotted name) of the selected dashboard template.
- type String
- Main entrypoint for the team.
Valid options are:
Explore
,Dashboards
,Events
,Alerts
,Settings
,DashboardTemplates
,Advisor
. - selection String
- Sets up the defined Dashboard name as entrypoint.
Warning: This field must only be added if the
type
isDashboards
, and the value is the numeric id of the selected dashboard, orDashboardTemplates
, and the value is the id (dotted name) of the selected dashboard template.
MonitorTeamTimeouts, MonitorTeamTimeoutsArgs
MonitorTeamUserRole, MonitorTeamUserRoleArgs
- Email string
- The email of the user in the group.
- Role string
- The role for the user in this group.
Valid roles are:
ROLE_TEAM_STANDARD
,ROLE_TEAM_EDIT
,ROLE_TEAM_READ
,ROLE_TEAM_MANAGER
or CustomRole ID. Default:ROLE_TEAM_STANDARD
. Note: CustomRole ID can be referenced fromsysdig.CustomRole
resource orsysdig.CustomRole
data source
- Email string
- The email of the user in the group.
- Role string
- The role for the user in this group.
Valid roles are:
ROLE_TEAM_STANDARD
,ROLE_TEAM_EDIT
,ROLE_TEAM_READ
,ROLE_TEAM_MANAGER
or CustomRole ID. Default:ROLE_TEAM_STANDARD
. Note: CustomRole ID can be referenced fromsysdig.CustomRole
resource orsysdig.CustomRole
data source
- email String
- The email of the user in the group.
- role String
- The role for the user in this group.
Valid roles are:
ROLE_TEAM_STANDARD
,ROLE_TEAM_EDIT
,ROLE_TEAM_READ
,ROLE_TEAM_MANAGER
or CustomRole ID. Default:ROLE_TEAM_STANDARD
. Note: CustomRole ID can be referenced fromsysdig.CustomRole
resource orsysdig.CustomRole
data source
- email string
- The email of the user in the group.
- role string
- The role for the user in this group.
Valid roles are:
ROLE_TEAM_STANDARD
,ROLE_TEAM_EDIT
,ROLE_TEAM_READ
,ROLE_TEAM_MANAGER
or CustomRole ID. Default:ROLE_TEAM_STANDARD
. Note: CustomRole ID can be referenced fromsysdig.CustomRole
resource orsysdig.CustomRole
data source
- email str
- The email of the user in the group.
- role str
- The role for the user in this group.
Valid roles are:
ROLE_TEAM_STANDARD
,ROLE_TEAM_EDIT
,ROLE_TEAM_READ
,ROLE_TEAM_MANAGER
or CustomRole ID. Default:ROLE_TEAM_STANDARD
. Note: CustomRole ID can be referenced fromsysdig.CustomRole
resource orsysdig.CustomRole
data source
- email String
- The email of the user in the group.
- role String
- The role for the user in this group.
Valid roles are:
ROLE_TEAM_STANDARD
,ROLE_TEAM_EDIT
,ROLE_TEAM_READ
,ROLE_TEAM_MANAGER
or CustomRole ID. Default:ROLE_TEAM_STANDARD
. Note: CustomRole ID can be referenced fromsysdig.CustomRole
resource orsysdig.CustomRole
data source
Import
Monitor Teams can be imported using the ID, e.g.
$ pulumi import sysdig:index/monitorTeam:MonitorTeam example 12345
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- sysdig sysdiglabs/terraform-provider-sysdig
- License
- Notes
- This Pulumi package is based on the
sysdig
Terraform Provider.