nOps 7.1 Release Cycle Announcement

With the monitoring powers that nOps brings to your infrastructure, it might be a little tricky to organize and manage your communication preferences. 

Change management alerts, rules, dashboards, and reports are different places where you can get notified. We’ve added the option to organize and get on top of your communication preferences on one page to get what you want, when you want it. 

Start organizing your communication preferences by clicking here.

Workloads are your building blocks to manage and improve your infrastructure. 🌏 

With nOps workloads, you can validate and measure the effectiveness of workload resources. Now, you can even get more than that by integrating workloads features with your workflow using nOps APIs for workloads! ⚡  Learn more about how you can pull your workload

Click here for more info

nOps has enhanced the partner sign-up flow. Now partners can be on-boarded and using nOps in minutes. nOps has also added a new dashboard that highlights the major features available on the nOps Partner Portal.

Click to go to partner portal 🚀 

Workloads provide a level of abstraction to describe and group resources

with a well-defined function and purpose to facilitate observation and

management. Once a workload is defined on nOps, a corresponding

workload is automatically created on your AWS account.

Workload type and resources are defined by using filters like Regions or Services.

It’s now possible to receive notifications about rules violations on

dashboards even when not on nOps.

Navigate to your custom dashboard (Reports -> Custom dashboards).

Click ‘Configure Notifications.’

Many resources in AWS have not supported tags upon creation. Now, by

default, tags can be attached to resources so that the root of any

violations can easily be highlighted and managed. 

To access, go to your: Profile Settings -> Default tagging.

When you see a spike in your daily spend you probably will need to identify where and who caused this increase in cost. But going to your resources list doesn’t tell you a lot about it. But now you can get more into the root cause by grouping your resources by your own resources tag to understand which team, which project, or which user was responsible for the cost. However the tags structure you follow, you can group resources by those tags, and get a summarized list of resources related to that tag, and the cost they caused. 

You can now export any of your custom dashboards to a PDF file that you can share easily across different mediums.

You will find a new option on the top right of your custom dashboard to export: 

It’s usually challenging to filter your infrastructure based on specific criteria, especially if you have more than one AWS account. Let’s say you need to list all your EC2 instances that have a specific CPU usage across your accounts, it would be a long trip to go with traditional tools. nOps allows you to do that easily now thanks to our new query language feature, which works in the same way SQL and JQL works. You describe a query, and then nOps processes this query to get you the results you need.

You can use things like: service types, cpu usage, creation dates, etc… for complete list of the options you can use currently, please refer to nOps documentation page

You can also save your queries to further use them quickly without the need to rewrite them.