{"id":2601,"date":"2026-11-19T15:09:50","date_gmt":"2026-11-19T14:09:50","guid":{"rendered":"https:\/\/thomas-kopton.de\/vblog\/?p=2601"},"modified":"2026-11-19T15:10:13","modified_gmt":"2026-11-19T14:10:13","slug":"calculating-metric-deltas-in-vcf-operations-with-a-small-management-pack","status":"publish","type":"post","link":"https:\/\/thomas-kopton.de\/vblog\/?p=2601","title":{"rendered":"Calculating Metric Deltas in VCF Operations with a Small Management Pack"},"content":{"rendered":"\n<h3 class=\"wp-block-heading\">Scenario<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most metrics in VCF Operations answer the question &#8220;what is the value right now&#8221;. A lot of the questions I get from customers are about something else: &#8220;how much did this move since the last collection cycle?&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Think of a counter that only ever goes up, a capacity number that should stay flat, or a metric where the interesting part is the jump and not the level. In all of those cases you do not want the value, you want the difference between the last two values.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is harder than it sounds. A super metric formula works with the values of the current cycle, across objects, and there is no &#8220;the value one cycle ago&#8221; to put in the formula. So the difference between the last and the previous collection is not something you can build in the formula editor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So I built a small management pack with the <a href=\"https:\/\/github.com\/vmware\/vmware-vcf-operations-integration-sdk\">VCF Operations Integration SDK<\/a> that does exactly one thing: it calculates that difference and writes it back as a new metric on the same object.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The Metric Delta Management Pack<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You give it a list of object types and stat keys in a configuration file:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  \"metricSets\": &#91;\n    {\n      \"adapterKind\": \"VMWARE\",\n      \"resourceKind\": \"VirtualMachine\",\n      \"maxSampleAgeMinutes\": 15,\n      \"metrics\": &#91;\"disk|usage_average\", \"net|usage_average\"]\n    }\n  ]\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">and after two collection cycles every VM carries the deltas:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Source metric<\/th><th>New metric<\/th><\/tr><\/thead><tbody><tr><td><code>disk|usage_average<\/code><\/td><td><code>Custom Metrics|Delta|disk|usage_average<\/code><\/td><\/tr><tr><td><code>net|usage_average<\/code><\/td><td><code>Custom Metrics|Delta|net|usage_average<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A few properties of the pack worth naming up front:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>It attaches the deltas to the <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">existing<\/mark><\/strong> objects of the vCenter adapter. No new objects, no second inventory tree.<\/li>\n\n\n\n<li>It never connects to vCenter. The only thing it talks to is the Suite API of the local VCF Operations instance.<\/li>\n\n\n\n<li><strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">If there is no delta, nothing is written.<\/mark><\/strong> More on that below, because it is the one design decision in the whole pack.<\/li>\n\n\n\n<li>The metric sets are configured in the UI, not in the adapter code, so adding a metric does not mean rebuilding anything.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How It Works<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Every collection cycle the adapter:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>reads its configuration file with <code>GET api\/configurations\/files?path=SolutionConfig\/&lt;file&gt;<\/code>,<\/li>\n\n\n\n<li>lists all objects of the configured <code>adapterKind<\/code> and <code>resourceKind<\/code> via <code>GET api\/resources<\/code>,<\/li>\n\n\n\n<li>asks for the <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">last two samples<\/mark><\/strong> of the configured stat keys with <code>POST api\/resources\/stats\/latest\/query<\/code> and <code>maxSamples: 2<\/code>, in batches of 200 object IDs,<\/li>\n\n\n\n<li>returns <code>last - previous<\/code> as a metric on those same objects, using the SDK&#8217;s <code>key_to_object()<\/code> so the keys match the existing ones.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The &#8220;extending an existing management pack&#8221; pattern from the SDK documentation is what makes step 4 work. You rebuild the resource key of an object another adapter owns, and whatever metrics you return land on that object.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Why no value is better than zero<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Here is the decision I mentioned. What should the adapter write when an object does not have two samples of a metric? A new VM, a metric that is not collected for that object, a collection that was skipped?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zero would be wrong. Zero is a perfectly valid delta: it means the value did not change. If you write zero for &#8220;I do not know&#8221;, every average, every alert threshold and every view column silently mixes &#8220;no change&#8221; with &#8220;no data&#8221;, and you will not see the difference.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So the adapter writes nothing in that case. The metric simply does not appear on that object for that cycle. It is one <code>if<\/code> in the code and it is the single most important line in the whole pack.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same thinking produced the optional <code>maxSampleAgeMinutes<\/code>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">What maxSampleAgeMinutes does<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">It is a freshness check on the <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">newest of the two samples<\/mark><\/strong>, nothing else. At collection time the adapter compares the timestamp of the newest sample with the current time:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>now - timestamp(newest sample) &gt; maxSampleAgeMinutes  -&gt;  no value is written<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Without the setting there is no such check: a delta is calculated whenever two samples exist, however old they are.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Why it matters: when a metric stops being collected, because the VM is powered off, the source adapter stopped or the metric was removed from a policy, its last two samples stay in the database. The delta is still calculable, and every cycle would write the same number again with a current timestamp. The delta metric would look alive while its source is dead. With the setting, the delta simply stops, which is the honest answer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sensible value is a little more than the collection interval of the source metric, for example 15 minutes for a metric collected every 5 minutes, so one missed cycle does not blank the delta.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One thing it does <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">not<\/mark><\/strong> do: it does not limit the gap <em>between<\/em> the two samples. If an object was not collected for a day and comes back, the two newest samples can be a day apart, and the delta covers that whole gap. The newest sample is fresh, so the check passes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lessons Learned in the Lab<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">1. The configuration file does not have to be XML<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">The files under <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">Configurations > Management Packs Configuration<\/mark><\/strong> are usually XML, but the content of those files is free format. The UI gives you a text editor and the Suite API hands your adapter back whatever is in the file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That means you can use JSON, which is both easier to read and a single <code>json.loads()<\/code> away from a Python dict. The only loss is comments, so the reference file keeps its documentation in a <code>_comment<\/code> key that the adapter ignores.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Reading the file is one call:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>GET api\/configurations\/files?path=SolutionConfig\/&lt;name&gt;.json<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">2. The Suite API is not available during Test Connection<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">My first version read and validated the configuration file in the <code>test()<\/code> method, which is the obvious place for it. On a live VCF Operations instance the test connection then failed with:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>TypeError(\"'NoneType' object does not support the context manager protocol\")<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>suite_api_client<\/code> of the adapter instance was <code>None<\/code>. VCF Operations passes Suite API credentials to an adapter <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">during collection<\/mark><\/strong>, not during test connection.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So the test connection now validates the adapter instance parameters only, and the configuration file is read and validated at the start of every collection. An error there shows up as a collection error on the adapter instance and in the adapter log. The downside is honest: a typo in the file name is only visible after the first collection, not when you save the account.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">3. mp-test and file permissions<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Before any of that, my very first <code>mp-test<\/code> run died with:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/usr\/local\/bin\/python: can't open file '\/home\/aria-ops-adapter-user\/src\/app\/app\/adapter.py': &#91;Errno 13] Permission denied<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The container runs as an unprivileged user, and Docker&#8217;s <code>COPY<\/code> keeps the permissions your files have on your machine. My <code>adapter.py<\/code> was <code>600<\/code>, so the container user could not read it. A <code>chmod -R a+rX app content conf<\/code> and the problem was gone. Worth remembering if your umask is <code>077<\/code>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4. Read your own configuration file before debugging the code<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">The VM deltas showed up on the first try. The host deltas did not, and the log did not even mention the host metric set. I checked the stat keys, I checked the object type, I was halfway into the Suite API queries when I looked at the configuration file again and found <code>\"enabled\": false<\/code> on that metric set, left over from the example file I had cloned.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The pack now logs every metric set it loads and every one it skips. That is a cheap line of code that would have saved me twenty minutes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Get It and Set It Up<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Everything is on GitHub: <a href=\"https:\/\/github.com\/tkopton\/vcf-operations-content\/tree\/main\/Metric-Delta-MP\">Metric-Delta-MP<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Install the ready-made .pak<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Download <a href=\"https:\/\/github.com\/tkopton\/vcf-operations-content\/blob\/main\/Metric-Delta-MP\/pak\/\">MetricDeltaAdapter_1.0.0.pak<\/a> and:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">Data Sources &gt; Integrations &gt; Repository &gt; Add<\/mark><\/strong> and upload the .pak.<\/li>\n\n\n\n<li>Under <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">Configurations &gt; Management Packs Configuration<\/mark><\/strong>, clone the shipped <code>metric_delta_config.json<\/code> and edit the clone. Do not edit the shipped file, an upgrade of the pack overwrites it.<\/li>\n\n\n\n<li>Under <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">Accounts &gt; Add Account<\/mark><\/strong>, choose <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">Metric Delta<\/mark><\/strong>, enter the name of your configuration file, pick the cloud proxy and save.<\/li>\n\n\n\n<li>Wait two collection cycles, then open one of the configured objects and look under <mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\"><code>Custom Metrics | Delta<\/code><\/mark>.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The .pak itself contains no adapter code. It points to a container image on Docker Hub, which the cloud proxy pulls when the account starts, so the cloud proxy needs access to Docker Hub. In an air-gapped environment, build your own .pak and push the image to a registry your proxy can reach.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Configuration file keys<\/h4>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Key<\/th><th>Required<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td><code>adapterKind<\/code><\/td><td>yes<\/td><td>Adapter kind owning the objects, e.g. <code>VMWARE<\/code><\/td><\/tr><tr><td><code>resourceKind<\/code><\/td><td>yes<\/td><td>Object type, e.g. <code>VirtualMachine<\/code>, <code>HostSystem<\/code><\/td><\/tr><tr><td><code>metrics<\/code><\/td><td>yes<\/td><td>Stat keys, case-sensitive, exactly as the source adapter publishes them<\/td><\/tr><tr><td><code>maxSampleAgeMinutes<\/code><\/td><td>no<\/td><td>Freshness check on the newest sample, see above<\/td><\/tr><tr><td><code>enabled<\/code><\/td><td>no<\/td><td><code>false<\/code> skips the whole set, default <code>true<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Build it yourself<\/h4>\n\n\n\n<pre class=\"wp-block-code\"><code>pip install vmware-aria-operations-integration-sdk\ncd vcf-operations-content\/Metric-Delta-MP\npython3 -m venv \"venv-Metric Delta Adapter\"\n. \"venv-Metric Delta Adapter\/bin\/activate\"\npip install -r adapter_requirements.txt pytest\n\npython -m pytest -q tests     # unit tests, no VCF Operations needed\nmp-test collect               # against a live instance\nmp-build                      # build the .pak<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For <code>mp-test collect<\/code>, answer <strong><mark style=\"background-color:rgba(0,0,0,0);color:#1a5fb4\" class=\"has-inline-color\">Yes<\/mark><\/strong> to &#8220;Set connection information for SuiteAPI calls?&#8221;. Without it the collection has no Suite API client, and you will meet lesson 2 from the other side.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Putting the Deltas to Work<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once the deltas are on the objects they behave like any other metric:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>as a column in a view or a report,<\/li>\n\n\n\n<li>as the input of a symptom definition, so you can alert on a jump instead of a level,<\/li>\n\n\n\n<li>in a super metric, where the delta is now just another stat key you can reference,<\/li>\n\n\n\n<li>as the metric of a custom group membership rule.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Known Limitations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Metrics added to another adapter&#8217;s objects cannot carry metadata, so the delta appears with the raw stat key of the source metric, without unit or label.<\/li>\n\n\n\n<li>The delta is always one collection cycle behind the source metric.<\/li>\n\n\n\n<li>A delta is a difference per collection interval, not a rate. If the collection interval of the source metric changes, deltas from before and after are not comparable.<\/li>\n\n\n\n<li>Stat keys are case-sensitive. A wrong key is not an error, it simply produces no value, which looks exactly like &#8220;no data&#8221;.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Give it a try in your lab and let me know what you would want it to do next. Issues and pull requests are welcome on the GitHub project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Disclaimer: this is a community project, not a Broadcom product. It is not supported by Broadcom. Test it in your lab before you let it anywhere near production.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-cyan-blue-color\">Stay<\/mark><\/strong> <strong><mark style=\"background-color:rgba(0, 0, 0, 0);color:#f5d800\" class=\"has-inline-color\">safe<\/mark><\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Thomas \u2013&nbsp;<a href=\"https:\/\/twitter.com\/ThomasKopton\">https:\/\/twitter.com\/ThomasKopton<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Scenario Most metrics in VCF Operations answer the question &#8220;what is the value right now&#8221;. A lot of the questions I get from customers are about something else: &#8220;how much did this move since the last collection cycle?&#8221; Think of a counter that only ever goes up, a capacity number that should stay flat, or &#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[57,81,95,93,34,2],"tags":[58,94],"class_list":["post-2601","post","type-post","status-publish","format-standard","hentry","category-aria-operations","category-integration-sdk","category-vcf","category-vcf-operations","category-vrealize-operations","category-vrops","tag-aria-operations","tag-vcf-operations"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Calculating Metric Deltas in VCF Operations with a Small Management Pack - TOMsOps<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thomas-kopton.de\/vblog\/?p=2601\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Calculating Metric Deltas in VCF Operations with a Small Management Pack - TOMsOps\" \/>\n<meta property=\"og:description\" content=\"Scenario Most metrics in VCF Operations answer the question &#8220;what is the value right now&#8221;. A lot of the questions I get from customers are about something else: &#8220;how much did this move since the last collection cycle?&#8221; Think of a counter that only ever goes up, a capacity number that should stay flat, or ...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thomas-kopton.de\/vblog\/?p=2601\" \/>\n<meta property=\"og:site_name\" content=\"TOMsOps\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-19T14:09:50+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-19T14:10:13+00:00\" \/>\n<meta name=\"author\" content=\"Thomas Kopton\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Thomas Kopton\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601\"},\"author\":{\"name\":\"Thomas Kopton\",\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/#\\\/schema\\\/person\\\/892d6b96c66b1dd4b75c6e32fdbfea82\"},\"headline\":\"Calculating Metric Deltas in VCF Operations with a Small Management Pack\",\"datePublished\":\"2026-11-19T14:09:50+00:00\",\"dateModified\":\"2026-11-19T14:10:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601\"},\"wordCount\":1595,\"commentCount\":0,\"keywords\":[\"Aria Operations\",\"VCF Operations\"],\"articleSection\":[\"Aria Operations\",\"Integration SDK\",\"VCF\",\"VCF Operations\",\"vRealize Operations\",\"vROps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601\",\"url\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601\",\"name\":\"Calculating Metric Deltas in VCF Operations with a Small Management Pack - TOMsOps\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/#website\"},\"datePublished\":\"2026-11-19T14:09:50+00:00\",\"dateModified\":\"2026-11-19T14:10:13+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/#\\\/schema\\\/person\\\/892d6b96c66b1dd4b75c6e32fdbfea82\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?p=2601#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Calculating Metric Deltas in VCF Operations with a Small Management Pack\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/#website\",\"url\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/\",\"name\":\"TOMsOps\",\"description\":\"Just another VMware Cloud Management Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/#\\\/schema\\\/person\\\/892d6b96c66b1dd4b75c6e32fdbfea82\",\"name\":\"Thomas Kopton\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e746aafbd3733172ceb4d600ba1feda61bc87cd3b70f5a9dfb581907cc7973b1?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e746aafbd3733172ceb4d600ba1feda61bc87cd3b70f5a9dfb581907cc7973b1?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e746aafbd3733172ceb4d600ba1feda61bc87cd3b70f5a9dfb581907cc7973b1?s=96&d=mm&r=g\",\"caption\":\"Thomas Kopton\"},\"url\":\"https:\\\/\\\/thomas-kopton.de\\\/vblog\\\/?author=1\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Calculating Metric Deltas in VCF Operations with a Small Management Pack - TOMsOps","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thomas-kopton.de\/vblog\/?p=2601","og_locale":"en_US","og_type":"article","og_title":"Calculating Metric Deltas in VCF Operations with a Small Management Pack - TOMsOps","og_description":"Scenario Most metrics in VCF Operations answer the question &#8220;what is the value right now&#8221;. A lot of the questions I get from customers are about something else: &#8220;how much did this move since the last collection cycle?&#8221; Think of a counter that only ever goes up, a capacity number that should stay flat, or ...","og_url":"https:\/\/thomas-kopton.de\/vblog\/?p=2601","og_site_name":"TOMsOps","article_published_time":"2026-11-19T14:09:50+00:00","article_modified_time":"2026-11-19T14:10:13+00:00","author":"Thomas Kopton","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Thomas Kopton","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thomas-kopton.de\/vblog\/?p=2601#article","isPartOf":{"@id":"https:\/\/thomas-kopton.de\/vblog\/?p=2601"},"author":{"name":"Thomas Kopton","@id":"https:\/\/thomas-kopton.de\/vblog\/#\/schema\/person\/892d6b96c66b1dd4b75c6e32fdbfea82"},"headline":"Calculating Metric Deltas in VCF Operations with a Small Management Pack","datePublished":"2026-11-19T14:09:50+00:00","dateModified":"2026-11-19T14:10:13+00:00","mainEntityOfPage":{"@id":"https:\/\/thomas-kopton.de\/vblog\/?p=2601"},"wordCount":1595,"commentCount":0,"keywords":["Aria Operations","VCF Operations"],"articleSection":["Aria Operations","Integration SDK","VCF","VCF Operations","vRealize Operations","vROps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/thomas-kopton.de\/vblog\/?p=2601#respond"]}]},{"@type":"WebPage","@id":"https:\/\/thomas-kopton.de\/vblog\/?p=2601","url":"https:\/\/thomas-kopton.de\/vblog\/?p=2601","name":"Calculating Metric Deltas in VCF Operations with a Small Management Pack - TOMsOps","isPartOf":{"@id":"https:\/\/thomas-kopton.de\/vblog\/#website"},"datePublished":"2026-11-19T14:09:50+00:00","dateModified":"2026-11-19T14:10:13+00:00","author":{"@id":"https:\/\/thomas-kopton.de\/vblog\/#\/schema\/person\/892d6b96c66b1dd4b75c6e32fdbfea82"},"breadcrumb":{"@id":"https:\/\/thomas-kopton.de\/vblog\/?p=2601#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thomas-kopton.de\/vblog\/?p=2601"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/thomas-kopton.de\/vblog\/?p=2601#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thomas-kopton.de\/vblog"},{"@type":"ListItem","position":2,"name":"Calculating Metric Deltas in VCF Operations with a Small Management Pack"}]},{"@type":"WebSite","@id":"https:\/\/thomas-kopton.de\/vblog\/#website","url":"https:\/\/thomas-kopton.de\/vblog\/","name":"TOMsOps","description":"Just another VMware Cloud Management Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thomas-kopton.de\/vblog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/thomas-kopton.de\/vblog\/#\/schema\/person\/892d6b96c66b1dd4b75c6e32fdbfea82","name":"Thomas Kopton","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/e746aafbd3733172ceb4d600ba1feda61bc87cd3b70f5a9dfb581907cc7973b1?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/e746aafbd3733172ceb4d600ba1feda61bc87cd3b70f5a9dfb581907cc7973b1?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/e746aafbd3733172ceb4d600ba1feda61bc87cd3b70f5a9dfb581907cc7973b1?s=96&d=mm&r=g","caption":"Thomas Kopton"},"url":"https:\/\/thomas-kopton.de\/vblog\/?author=1"}]}},"_links":{"self":[{"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=\/wp\/v2\/posts\/2601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2601"}],"version-history":[{"count":12,"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=\/wp\/v2\/posts\/2601\/revisions"}],"predecessor-version":[{"id":2613,"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=\/wp\/v2\/posts\/2601\/revisions\/2613"}],"wp:attachment":[{"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thomas-kopton.de\/vblog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}