Amazon AWS FastPack
dynaTrace - Michael Kopp
Fastpack Download contains:
The Instance Monitoring provides an overview of the relevant CloudWatch metrics for a specific cloud instance. The dashboard shows live and historical data about
This dashboard assists you in the verification of the health of your Amazon EC2 Instance. The CloudWatch monitor delivers the metrics for all attached EBS volumes separately as dynamic measures, but the dashboard simply charts a summary.
The load balancer dashboard provides an overview of load balancer specific metrics like Latency, the number of healthy and unhealthy hosts and the number of errors produced by the load balancer as opposed to the application itself.
The RDS Monitoring provides an overview of the relevant metrics of a specific RDS instances. It is meant to be viewed for a single RDS instance . The dashboard shows live and historical data about
This dashboard assists you in the verification of the health of your Amazon RDS Instance and can help explain why SQL statements executed against that instance might have been slow.
The Amazon CloudWatch Monitor supports monitoring of instances EC2 and RDS Instances as well as load balancers. If need it to be extended to any other CloudWatch provider please ask so in the forum. You will receive data even if you do not enable cloud watch specifically, but for most types of data it will have only a 5 minute granularity. If you enable detailed monitoring you will receive data every minute. If you have detailed monitoring for only some of the instances, set it up to be scheduled once a minute and the monitor will do the rest.
The Monitor is configured by supplying the following parameters:
The monitor will use the supplied host (or host list) to figure out the instances to monitor. In case you run completely in the EC2 Cloud you can just add the hostgroup "Local" to the monitor and it will automatically monitor all your ec2 instances that have a dynaTrace agent placed. In order to monitor RDS and ELB instances simply add the hostname to the infrastructure section of the server configuration and make sure it is within the monitored host group. You do not have to setup a separate monitor for EC2 or RDS, the monitor will figure this out on its own.
The monitor uses the auto discovered hostnames to identify the EC2 instance. While this works from outside the EC2 cloud, it works best if the collector that does the monitoring sits itself in the same EC2 region as the instances it monitors.
In addition to using the monitor we recommend using the dynaTrace Agent and Collector to get more detailed system and application metrics.
The Amazon AWS FastPack contains everything to get started with Amazon cloud monitoring.
Hi, I have dT version 184.108.40.20620. Would this plugin work for me?
yes it will
The installer doesn't install the dashboards or system profile with versions 5.5+. You can open the installer file with any archive manager e.g. 7zip and manually install them or overwrite the plugin.xml file with this one attached.
Hi, I have installed this pack, but I can't use it.
It looks like can not make any connections with AWS servers.
Is there any logs giving on dT client to figure it out?
I'm using dT version 220.127.116.1111
Monitors write logfiles on the collectors where they get executed. To find these log files use the System Information Dashlet and drill to that Collector
I want to use this plugin for monitoring certain AWS ec2 instances. Could you please explain the parameters required to configure the plugin.
accessKeyID, secretAccessKey, and the host list. Is the HTTP proxy and port necessary because if i dont give a port no it gives error even if i have not mentioned the HTTP proxy.
If i use pk.pem and cert.pem as the keys and some proxy add and port then its still failing.
Error message :- Execution of plugin failed. Calling setup() method failed.
I would really appreciate some help on this.
Is it mandatory work with Proxy and in case of yes, may I configure an user an password?
I'm asking because my collector is located on network that has no need to use proxy to access AWS,
I can to deploy the monitoring on a network with proxy, but in this case is mandatory to work with user and passowrd.
I am using dT 6.1.
Further to this. I have confirmed that our hosts are in EC2. It does not matter what Host I put in (or what port), I get the following error.
2015-07-16 07:03:01 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_32] Check EC2 Environment2015-07-16 07:03:01 INFO [AmazonHttpClient@New Amazon CloudWatch Monitor_62] Previous message was repeated 1 times.2015-07-16 07:03:01 INFO [AmazonHttpClient@New Amazon CloudWatch Monitor_62] Configuring Proxy. Proxy Host: Proxy Port: 31282015-07-16 07:03:01 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_62] Check EC2 Environment2015-07-16 07:03:02 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_59] Not In EC2 Environment, guess hostnames2015-07-16 07:03:02 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_51] Not In EC2 Environment, guess hostnames2015-07-16 07:03:02 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_43] Not In EC2 Environment, guess hostnames2015-07-16 07:03:02 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_67] Not In EC2 Environment, guess hostnames2015-07-16 07:03:02 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_12] Not In EC2 Environment, guess hostnames2015-07-16 07:03:02 SEVERE [CloudWatchMonitor@New Amazon CloudWatch Monitor_42] Not In EC2 Environment, guess hostnames
I'm also not seeing the dashboards or system profile that is supposed to get installed with the fastpack. I'm on v.6.2. The Plugin is installed but nothing else in the fastpack is showing up. Any ideas? Suggestions?
Can someone provide a hint how to configure the proxy fields in the monitor?
Hi Graeme. I recently had a conversation via email with one of our users who worked on this. I asked him to comment. stay tuned
Hi - Some request as Graeme - we do not have a proxy for the collectors yet it is mandatory. Any ideas?
I could configure it with Proxy Port "0" and no proxy-host, did you try that?
Dominik Stadler - is the source code available? We could update this to auto discover. That or we'll have to write a whole new plugin.
Yes, looks like that is the cause.
Unfortunately I am also not maintaining this plugin and am not working actively on Dynatrace at the moment. Can you post a support case to ask for the source-code.
Matthew Singleton I have added the source code to the GitHub repository: https://github.com/Dynatrace/Dynatrace-Amazon-AWS-FastpackIngo
did you change anything with this plugin? If yes it would be great if you could share your changes.
with this to work for the ec2 instance, i had to add the internal dns hostname as the host paramater and it works great. I am trying to get rds instance information and that is not something that amazon provides, I can see that it describes the rds instance but nothing that is found in that description allows this plugin to get the stats, what should I use for the host value when setting up rds?
Trying to set this up on 6.5 and I'm getting a "Unexpected AWS Error:: AWS was not able to validate the provided access credentials" although I'm convinced it's valid because I can get in via the Amazon CLI tool. Any ideas?