Monitoring AWS Kinesis
The AWS Kinesis sensor is automatically deployed and installed after you install the Instana agent.
Note: Learn about the other supported AWS services with AWS documentation.
- Sensor (Data Collection)
- Required Permissions
Sensor (Data Collection)
- Kinesis Data Streams Instance Details
- Stream name
- Stream ARN
- Stream status
- Stream encryption type
- Stream retention period (hours)
- Stream creation time
- AWS Grouping Zone
Metrics for Kinesis are pulled every 5 minutes, which can be changed through agent configuration in
com.instana.plugin.aws.kinesis: cloudwatch_period: 300
To disable monitoring of Kinesis streams, use the following configuration:
com.instana.plugin.aws.kinesis: enabled: false
To configure the specific AWS Sensor to use proxy configuration, add the following agent configuration settings:
com.instana.plugin.aws.kinesis: proxy_host: 'example.com' # proxy host name or ip address proxy_port: 3128 # proxy port proxy_protocol: 'HTTP' # proxy protocol: HTTP or HTTPS proxy_username: 'username' # OPTIONAL: proxy username proxy_password: 'password' # OPTIONAL: proxy password
Monitoring multiple AWS accounts
Refer to the Monitoring multiple AWS accounts documentation to set up monitoring of multiple AWS accounts with one AWS agent in the same region.
AWS named profiles approach
To override which profiles can be used to monitor Kinesis, use the following configuration:
com.instana.plugin.aws.kinesis: profile_names: - 'profile2' - 'profile3'
Note: Defining profiles on service level overrides the global AWS profiles configuration.
AWS STS approach
To override which IAM Roles are used to monitor Kinesis, use the following configuration:
com.instana.plugin.aws.kinesis: role_arns: - 'arn:aws:iam::<account_1_id>:role/<role_1_name>' - 'arn:aws:iam::<account_2_id>:role/<role_2_name>'
Note: Defining IAM roles on service level overrides the global AWS IAM roles configuration.
Multiple tags can be defined, separated by a comma. Tags are be provided as a key-value pair separated by: To make configuration easier, it is possible to define which tags you want to include in discovery or exclude from discovery. If defining tag in both lists (include and exclude), exclude list has higher priority. If there is no need for filtering services, the configuration should not be defined. It’s not mandatory to define all values in order to enable filtering.
Users are able to specify how often sensors poll the AWS tagged resources that use the
tagged-services-poll-rate configuration property (default 300 seconds).
Note: Tags are only available with the AWS Agent.
To define how often sensors poll the tagged resources use following configuration:
com.instana.plugin.aws: tagged-services-poll-rate: 60 #default 300
To include services by tags into discovery, use following configuration:
com.instana.plugin.aws.kinesis: include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)
To exclude services by tags from discovery, use following configuration:
com.instana.plugin.aws.kinesis: exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)
AWS services without tags are monitored by default but can be excluded by setting the
include_untagged field to
com.instana.plugin.aws.kinesis: include_untagged: false # True value by default