With the recent release of the VMware Aria Operations for Applications product we have made some improvements to the Usage Portal. In addition to the dashboard for analyzing overall usage, VMware Aria Operations for Applications supports ingestion policies for usage by particular accounts, groups, sources, metric namespaces, or even point tags. As an administrator, it is valuable to you to understand the ingestion rates of different teams in your organization or the ingestion rates of the different sources and be able to manage their consumption, cost, overage, etc.
VMware Aria Operations for Applications makes it easy to do this by creating an ingestion policy, an administrator can define on a set of accounts, groups, sources, metric namespaces, or even point tags. Optionally, the administrator can set a PPS limit associated with an alert for excessive or very low usage. An ingestion policy helps you to start monitoring the policy PPS usage for a billing period from the ingestion policy dashboard, which shows:
- The P95 PPS usage out of the limit, if configured
- The month-to-month percentage change in the PPS usage
- The hourly PPS usage
- The list of accounts that ingest most data
- The usage by ingestion mechanism (proxy and direct ingestions)
- The usage by ingestion type (time series, histograms, and delta counters)
Ingestion Policy Basics
Ingestion policies allow you to combine user and service accounts, groups, sources, metric namespaces, or point tags, so that you can analyze their usage of the VMware Aria Operations for Applications service. The administrator could decide to create a policy for a group of interns or new hires. He/She can also create a policy for one or more virtual machines, kubernetes cluster or a cloud native application. The administrator can also choose to set a Points per Second (PPS) limit for the policy or even create an alert, so that you can receive notifications if the PPS usage exceeds certain thresholds of the limit.
Tracking the PPS usage by ingestion policy helps the administrator understand how the overall usage is distributed and whether a particular team or group will need more PPS in the future or will need to reduce their overhead ingestions. As you can see ingestion policies provide very useful data from a costing and forecasting perspective.
Note:
- The scope of a policy can be accounts, groups, sources, namespaces, or point tags.
- Once you set the scope, you cannot change it.
- You can only make changes to the accounts or objects assigned to the policy in accordance with the scope.
- Accounts or objects can belong to more than one policy.
- Only Super Admin users can create and edit ingestion policies.
- Only Super Admin users can edit or delete alerts associated with ingestions policies. Make note that even if you have the Alerts permission, you cannot edit or delete ingestion policy alerts unless you are a Super Admin user.
- Only Super Admin users can view ingestion policy versions.
- From the gear icon on the toolbar, select Usage and Subscriptions and click the Ingestion Policies tab.
- Click the ellipsis icon next to the policy and select Versions.
- However, all users can view the ingestion policies, the ingestion policy dashboards, and the ingestion policy alerts.
- You can now sort the ingestion policies by PPS usage within the last 1 hour.
All users can also export the Usage Summary dashboard and the ingestion policy dashboards in PDF format.
Now that we have learnt in detail about the Usage Portal Improvements by VMware Aria Operations for Applications (Wavefont) we suggest you give this a try and report any suggestions and improvements based on your usage and provide feedback via official channels if any …! You can also learn more about other VMware Aria Operations for Applications features on TechZone !
