cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Get Your Head Out of the Clouds, and Your Data Too

Level 13

I have been bursting at the seams to write about this topic. Now that the Server & Application Monitor (SAM) Release Candidate is available, I can tell you all about it. As many of you may know, SAM already has an ability to monitor workloads that are running in the cloud. The Orion® agent and agentless based technology allows SAM the flexibility to monitor all of your workloads on-premises as well as in the public cloud.

Now with SAM 6.4 or VMAN 7.1, you can collect configuration and metric data directly from Amazon Web Services® (AWS), and have that data visualized along with the rest of the environment you are already monitoring. All you need are your AWS account credentials.

Once you have your account configured in the Orion console, you will then be able to see all of your EC2™ instances and EBS volumes within one summary screen.

cloud_summary.png

If you have multiple AWS accounts, no problem. Add each one, so the Orion platform can discover all of the associated cloud instances and know which AWS region they are running in.

cloud_infra.png

Just like the detail that is available with existing Orion Nodes, you can drill down and see more information about individual cloud instances, including attached EBS volumes, default CloudWatch™ metrics, and configuration settings like Auto Scaling Group membership.

cloud_details.png

Now, if you want to go deeper into monitoring your workloads running in the cloud, beyond what AWS provides, all you have to do is manage the cloud instance as an Orion Node. We even created a handy mechanism for you to do so, directly from the Cloud Instance Details page.

manage_instance.png

This will give you the ability to monitor what’s running on the OS, directly from the cloud instances. At that point, all you have to do is switch between the Orion Node Details view and the Cloud Instance Details view to have complete visibility.

node_details1.pngnode_details2.png

As an added benefit, you can apply your existing SAM Application Templates and visualize the end to end infrastructure relationships with AppStack™.

app_details.png

Our goal with introducing this feature was to ensure that no matter where your workloads are running, you will have the information you need to ensure their health and availability. We know that the landscape of IT is changing, and as increasing public cloud adoption transforms traditional IT environments into hybrid ones, we need to deliver the tools necessary for adapting to this new complexity.

But wait, there’s more!

Since you made it to the bottom of this post, I thought I would share something extra with you. If you have read the recent post, Drag & Drop Answers to Your Toughest IT Questions, you will be aware of the new PerfStack feature that is also available. What you may not have known is that the cloud instance data, mentioned above, is also available in PerfStack, allowing hybrid environment comparisons and correlations with on-premises workloads.

perfstack_cloud.png

So, what are you waiting for? Log into the Customer Portal and download SAM 6.4. If you have any feedback or questions, feel free to post them in the Server & Applications Monitor Release Candidate group as well.

20 Comments
Level 15

CloudWatch you say?

Autoscale groups you say?

Zoidberg feels like king of the AWS!

MVP
MVP

I've been testing SAM 6.4 in a test VM - looking forward to installing the Release Candidate in production tomorrow morning.

Level 8

node_details2.png

How about the AWS EC2 instance tags, can that be retrieved , maybe is under CONFIGURATION DETAILS.

Can someone check please?

Level 13

That feature will not be available in this release. However, it is something that we are working on for a future release. I'll reach out to you offline to better understand how you are using tags for your environment.

I'd love to see this added to my Orion suite this year.

Level 13

As would I.

Level 12

This is something we have been looking for. Hopefully it meets our needs. Tags will be useful as well since we use them to distinguish department and who to present the bills to! LOL

Speaking of bills, is there a cost management that will be part of this so we could determine what each instance is running up?

Level 13

Great to hear, ACDII. We are looking to address tagging and aspects of what resource consumption impact costs in a future release.

Level 10

This looks really interesting, is there plans to do this on other cloud vendors - specifically Azure?

I see the website page says: "The optional agent (for Windows® and Linux®) extends the scope of monitoring to the cloud (Amazon® AWS, Microsoft® Azure®, Rackspace®, etc.) "

Level 13

Yes there are.

Level 10

Awesome, shout if you want a guinea pig when its ready! Any idea of timescales, are we talking this year?

Level 13

Will do. Unfortunately, I do not have any timelines I can communicate at this time.

Make that 2 guinea pigs!

Level 7

Not to be negative, but since the AWS Cloudwatch API contains a lot of metrics, why is Solarwinds limiting it down to EC2 and EBS Volumes.  For example, I would like to grab my metrics for my AWS Lambda functions.

Level 7

Not to be negative, but since the AWS Cloudwatch API contains a lot of metrics, why is Solarwinds limiting it down to EC2 and EBS Volumes.  For example, I would like to grab my metrics for my AWS Lambda functions.

Many of our applications teams use other AWS Services.

Level 13

The most common use case we found revolved around the need to monitor EC2 instances and the related EBS volumes, so we set out to solve this problem first. We continue to evaluate the need to monitor additional cloud services, like AWS Lambda.

Level 12

What about private cloud based on solution like Mesos / Maraton / Docker?

Level 13

This is independent of container management and orchestration solutions. We are continuing to evaluate our customers' need to monitor container related solutions. You can vote for .

I have been reading up on Solarwinds and AWS monitoring and am a bit more confused than when I started.  I use Amazon S3 for storage can I not monitor that if its up or not?  I have seen a few different articles and I have setup a Solarwinds user in my AWS to get either some metrics or just an up or down alert but not sure where to go after I create the AWS account in Amazon and in Solarwinds.  Can I only monitor if I have VMs in AWS?  If anyone can direct me to any other articles for clarity that would be great.  Thanks! - Dave

Level 13

The particular feature that is referenced in this blog is associated with monitoring AWS EC2 instances. Currently, you can use the existing script component monitors to collect other data from the AWS APIs and monitor in SAM.

About the Author
I have been involved in the IT industry for more than 15 years, focusing on end user computing, server-based computing, and server and desktop virtualization solutions for SMB to enterprise environments. My start was as a very humble IT desktop and server support person for family owned insurance company. From there, I have held various roles in the enterprise software world, including both on the customer and vendor sides.