stevenwhunt

It's still open for voting.

Dave, you can check out WHAT WE'RE WORKING ON FOR VIRTUALIZATION MANAGER (UPDATED July 30, 2015) for information about whats on our roadmap. You can also vote on this as a feature request here .

This version of core will also ship with the next release of SAM.

If computing were only that simple.

It does. Thanks.

Already had it and its one of my favorite places to go in Chi-town.

Tag away! Our customers are my first priority. If you are not getting the response that you expect, I am happy to make sure you get that response. I am always coming to our customers for product feedback, the least I can do is make sure they are getting the on going support they expect.

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 .

Trust me, I know. I wish there was more that I could say on here.

Yes, the beta is now closed. Keep an eye out for a RC announcement.

Hear you loud and clear, guys.

Paying very close attention.

All requests are taken seriously, but there is not a defined value.

See and .

Yeah, Azure is tricky from an external security standpoint.

I believe that is ding​.

You can also vote on native .

Orion Platform 2017.3 also shipped with SAM 6.5.

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.

Great feedback. Thanks!

Votes only count once.

True, but as long as my session is before lunch, we're good.

And don't forget, you get thwack points for beta participation!

Yes, because RC2 was not the RTM build.

That is correct, as we currently do not have offline support for this information. Due to the dynamic, and customer specific nature of this information, it would not be an easy problem to solve. I'll monitor this closely.

To be clear, you are looking for pagination of the widget, so the widget does not extend vertically when you have a large number of records?

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.

There are a number of reasons this could be. Have you tried search the Success Center for additional information?

There are some things that might address this for you in Server & Application Monitor 6.3 - Beta 2 Now Available.

I know this is something that we are looking at incorporating in a future release. First we wanted to get mute functionality implemented as mutes/reason would be associated with both.