Monitoring AWS Beanstalk

Tracked Configuration

Environment details:

• Application name
• Environment ID
• Environment Name
• Environment Description
• Environment ARN
• Environment Status
• Date created
• Version Label
• Solution Stack
• Environment URL
• Application name
• Application name
• Application name
• Grouping zone (region)

Instance details:

• Instance ID
• Instance Status
• Instance Type
• Instance started Date

Metrics

Configuration

Beanstalk instances are refreshed every 60 seconds. Due to an asynchronous nature of detection instance metrics can be late. This delay depends on the specified poll rate (cloudwatch_period) and by default that it is not longer than a minute before they appear on the dashboard. Metrics for Beanstalk are pulled every 60 seconds, and it can be changed through agent configuration in /opt/instana/agent/etc/instana/configuration.yml:

com.instana.plugin.aws.beanstalk:
  cloudwatch_period: 60

To disable monitoring of Beanstalk instances use the following configuration,

com.instana.plugin.aws.beanstalk:
  enabled: false

Proxy configuration

To configure the specific AWS Sensor to use proxy configuration, add the following agent configuration settings:

com.instana.plugin.aws.beanstalk:
  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.

com.instana.plugin.aws.beanstalk:
  profile_names:
    - 'profile2'
    - 'profile3'

com.instana.plugin.aws.beanstalk:
  role_arns:
    - 'arn:aws:iam::<account_1_id>:role/<role_2_name>'
    - 'arn:aws:iam::<account_2_id>:role/<role_3_name>'

Filtering

Multiple tags can be defined, separated by a comma. Tags should 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. To define 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 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).

Tags are only available with the AWS Agent.

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.beanstalk:
  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.beanstalk:
  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 false:

com.instana.plugin.aws.beanstalk:
  include_untagged: false # True value by default

Poll Rate

To define how often sensors poll the tagged resources use following configuration:

com.instana.plugin.aws:
  tagged-services-poll-rate: 60 #default 300