Subject: Re: Cognizant : Memory Metrics Utilization
From: Greg Winfield <[email-masked]>
To: Rajesh Krishnan <[email-masked]>, Souvik Kumar Singha <[email-masked]>, Rakesh R <[email-masked]>
Cc: Sreyashi Basu <[email-masked]>, Navankur Arya <[email-masked]>, Smitha Kummur Basavaraj <[email-masked]>
Date: Mon, 21 Jul 2025 22:47:21 +0000

Thanks Rajesh,

Rakesh - per the below – can you ask Cognizant to raise an RFE for consideration, per my note, Cldy engineering aren’t about to pivot to meet Cognizant requirement, but I do like their suggestion and we should capture it for future consideration.

Greg Winfield
Cloud Solution Architect & FinOps Instructor, Customer Success – APAC
[signature_3490166860][signature_246175199][signature_2497796681][A white and orange hexagon with black text  Description automatically generated][signature_2186291366]
Apptio, an IBM Company
[email-masked]<mailto:[email-masked]> M +61434850518<tel:+61434850518>
Upcoming Leave : 28/7 – 8/8
[signature_3397100707]

From: Rajesh Krishnan <[email-masked]>
Date: Monday, 21 July 2025 at 5:02 PM
To: Souvik Kumar Singha <[email-masked]>, Greg Winfield <[email-masked]>
Cc: Sreyashi Basu <[email-masked]>, Navankur Arya <[email-masked]>, Smitha Kummur Basavaraj <[email-masked]>
Subject: Re: Cognizant : Memory Metrics Utilization
Thanks so much for your prompt inputs to the customer, Souvik. Much appreciated!

Greg – fully agree with your thoughts below. Could you please ask the customer to raise an RFE and we’ll evaluate for future roadmap.

Regards,
Rajesh

From: Souvik Kumar Singha <[email-masked]>
Date: Monday, 21 July 2025 at 12:02 PM
To: Greg Winfield <[email-masked]>, Rajesh Krishnan <[email-masked]>
Cc: Sreyashi Basu <[email-masked]>, Navankur Arya <[email-masked]>, Smitha Kummur Basavaraj <[email-masked]>
Subject: Re: Cognizant : Memory Metrics Utilization
Hi @Greg Winfield<mailto:[email-masked]> @Rajesh Krishnan<mailto:[email-masked]>

The customer is wanting an update on this. Are you updating or should we? Since it’s the design, and it’s a Product call, I was waiting for a response from your end.

Regards
Souvik

From: Greg Winfield <[email-masked]>
Date: Tuesday, 15 July 2025 at 12:27 PM
To: Souvik Kumar Singha <[email-masked]>, Rajesh Krishnan <[email-masked]>
Cc: Sreyashi Basu <[email-masked]>, Navankur Arya <[email-masked]>, Smitha Kummur Basavaraj <[email-masked]>
Subject: Re: Cognizant : Memory Metrics Utilization
Team; thank you very much for wading in here, appreciate you all 😊

They will need to raise an RFE for this. We’re not about to pivot to meet their requirement (@Rajesh Krishnan<mailto:[email-masked]> apologies if I am overstepping the mark here) - I do like their idea and it would simplify for us for many customers getting mem metrics with little to no fuss, but, at present our strategy is to use DCR and AMA – these can be deployed though policy so I don’t buy they can’t deploy to their workloads en masse,  they want us to change our product to suit them.

Let me know if I have misread, if you agree, I’m happy to email them back and tell them the same.

Greg Winfield
Cloud Solution Architect & FinOps Instructor, Customer Success – APAC
[signature_3490166860][signature_246175199][signature_2497796681][A white and orange hexagon with black text  Description automatically generated][signature_2991692431]
Apptio, an IBM Company
[email-masked]<mailto:[email-masked]> M +61434850518<tel:+61434850518>
Upcoming Leave : 28/7 – 8/8
[signature_2007646623]

From: Souvik Kumar Singha <[email-masked]>
Date: Tuesday, 15 July 2025 at 4:51 PM
To: Rajesh Krishnan <[email-masked]>, Greg Winfield <[email-masked]>
Cc: Sreyashi Basu <[email-masked]>, Navankur Arya <[email-masked]>, Smitha Kummur Basavaraj <[email-masked]>
Subject: Re: Cognizant : Memory Metrics Utilization
Hi Rajesh

From what I infer from their reply is:

  1.  They want the Available Memory Bytes and Available Memory percentage from the Platform metrics itself. Currently Utilisation is only pulling Available Memory Bytes(Preview) and NOT the non-preview and percentage. Even though we make the necessary changes to pull in these metrics data, currently the memory data that is being portrayed in Rightsizing UI is still the metrics that we receive from Guest OS metrics. This is the initial design and this is something the Product team needs to take a call on.
  2.  For memory, Azure had the option for more granularity, so Guest OS metrics was chosen to give the memory metrics via the AMA. This is again from the initial design.

Regards
Souvik

From: [email-masked] <[email-masked]>
Date: Tuesday, 15 July 2025 at 11:26 AM
To: Souvik Kumar Singha <[email-masked]>, Agarwal, Tanish (Cognizant) <[email-masked]>, R V, Krishnan (Cognizant) <[email-masked]>, Karanth, Pradeepa (Cognizant) <[email-masked]>, Rakesh R <[email-masked]>
Cc: Greg Winfield <[email-masked]>, Rajesh Krishnan <[email-masked]>, Matthew Belyus <[email-masked]>, Sreyashi Basu <[email-masked]>, Smitha Kummur Basavaraj <[email-masked]>, [email-masked] <[email-masked]>, [email-masked] <[email-masked]>
Subject: [EXTERNAL] RE: Cognizant : Memory Metrics Utilization
Hi Kumar & Team, Thanks for letting us know how cloud ability currently pulling the VM metrics for Azure VMs. We have below inputs and queries, kindly check and let us know. As how Cloudability is pulling the CPU, Network metrics without
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
Report Suspicious <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/AdhS1Rd-!-_FXHPseXk97uls5T-WAUTU214-TNdo6YdQ_8Fc3fq0Jo-Rb_AQLYbtyyy4Gc-2UDbLmkkIDDxRPIM0kxQhCr3Zm1OVrRd5VsH5csrjhGO1LuI3Mj__4r3P5RJMawQsIcDmaedOEOG8s$>

ZjQcmQRYFpfptBannerEnd
Hi Kumar & Team,

Thanks for letting us know how cloud ability currently pulling the VM metrics for Azure VMs. We have below inputs and queries, kindly check and let us know.

  1.  As how Cloudability is pulling the CPU, Network metrics without AMA installed, these are part of Platform Metrics which gets automatically pulled without agents.

We like to get the VM “available memory usage/bytes” as well pulled through platform metrics since its General available(not in preview), without agents automatically.

This is as well valid VM  metrics to get the VM memory utilization as per Microsoft confirmation, the change required from Cloudabily  is to convert this available to usage metrics.

Currently in azure platform we get below memory metrics for all VMs without Agents.

Available Memory percentage ( to calculate the usage% , 100- available%)

Available Memory Bytes( to calculate the usage Bytes % , (Available Bytes/(1024*1024*1024))/Total Memory in GB*100

If this is done on Cloudability level, we do not need any other configuration on the customer end.

Reasons:

We do have challenges enabling guest OS level metrics for memory , as we are managing larger cloud infrastructure, day by day its dynamically azure cloud accounts and VMs provisioned and deprovisioned. We could not follow up with all cloud accounts owners to enable this metrics.

Enabling guest Os metrics also required additional cost( Log analytics, storage accounts…etc) even if we go with some automations or other policy methods that most of the cloud account owners will not agree for additional cost. it may not possible for all Azure accounts too. This will also create duplicate logs enablement, if customer is enabled for different purposes.

Hence we like Cloudability to pull the memory usage data from platform metrics itself. Since currently its available from platform metrics feature and can be consumed by Cloudability similar to CPU %, Network,.,etc.

  1.  Cloudability is able to pull both Platform metrics as well as Guest OS Metrics, but since Guest OS Metrics gives a more granular context, this is used to portray the memory in the Rightsizing UI.
How CPU and for other usage metrics is referred from platform metrics instead of guest OS performance counters(DCR) which will give more granular insights and why only for memory this is still enforced when natively available?

We are eager to know if this change will be incorporated in Cloudablity if so any tentative timeline ? Or

There is no plan to incorporate the available Memory platform metrics and Cloudability will continue to go with Guest OS memory metrics for Azure?

Let us know if you need more information for the platform Memory metrics, We will setup call with Microsoft to clarify any further details on this.

+ Deva and Koushik,

Snapshot of general availability of the platform memory metrics.

Regards,
Aron
IT - Technology Services

From: Souvik Kumar Singha <[email-masked]>
Sent: 14 July 2025 08:05 PM
To: S, Aronbabu (Cognizant) <[email-masked]>; Agarwal, Tanish (Cognizant) <[email-masked]>; R V, Krishnan (Cognizant) <[email-masked]>; Karanth, Pradeepa (Cognizant) <[email-masked]>; Rakesh R <[email-masked]>
Cc: Greg Winfield <[email-masked]>; Rajesh Krishnan <[email-masked]>; Matthew Belyus <[email-masked]>; Sreyashi Basu <[email-masked]>; Smitha Kummur Basavaraj <[email-masked]>
Subject: Re: Cognizant : Memory Metrics Utilization

CAUTION: External Email
Hi All

So to put into perspective for everyone’s understanding, this is what’s happening in Cloudability Rightsizing for Azure VM:

  1.  Azure has two sources: Platform Metric and Guest OS Metric
  2.  Platform Metric has Available Memory Bytes(Preview) which is high level, whereas, Guest OS Metric has Memory Available Bytes/ Memory Committed Bytes for Windows VM and mem/available and mem/used for Linux VMs which are more granular.
  3.  Cloudability is able to pull both Platform metrics as well as Guest OS Metrics, but since Guest OS Metrics gives a more granular context, this is used to portray the memory in the Rightsizing UI.
  4.  So, for pulling Guest OS Metrics, there should be AMA and DCR enabled in Azure.
  5.  As how Cloudability is pulling the CPU, Network metrics without AMA installed, these are part of Platform Metrics which gets automatically pulled without agents.

Regards
Souvik

From: Rajesh Krishnan <[email-masked]<mailto:[email-masked]>>
Date: Monday, 14 July 2025 at 6:14 PM
To: Greg Winfield <[email-masked]<mailto:[email-masked]>>, Souvik Kumar Singha <[email-masked]<mailto:[email-masked]>>, Sreyashi Basu <[email-masked]<mailto:[email-masked]>>
Cc: Smitha Kummur Basavaraj <[email-masked]<mailto:[email-masked]>>
Subject: Re: Cognizant : Memory Metrics Utilization
Adding @Souvik Kumar Singha<mailto:[email-masked]> and @Sreyashi Basu<mailto:[email-masked]>

Souvik/Sreyashi – refer to the customer’s email below. Could you please help to comment on how we currently get the azure memory metrics for Cognizant? And if the customer doesn’t want us to deploy any agents, how would we fetch their azure memory metrics into Cloudability?

Regards,
Rajesh

From: Greg Winfield <[email-masked]<mailto:[email-masked]>>
Date: Monday, 14 July 2025 at 6:02 PM
To: Rajesh Krishnan <[email-masked]<mailto:[email-masked]>>
Subject: FW: Cognizant : Memory Metrics Utilization
FYi – keen on your thoughts

Greg Winfield
Cloud Solution Architect & FinOps Instructor, Customer Success – APAC
[signature_3490166860][signature_246175199][signature_2497796681][A white and orange hexagon with black text    Description automatically generated][signature_2496595933]
Apptio, an IBM Company
[email-masked]<mailto:[email-masked]> M +61434850518<tel:+61434850518>
Upcoming Leave : 8/7, 28/7 – 1/8
[signature_899805738]

From: [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Date: Friday, 11 July 2025 at 7:32 PM
To: Greg Winfield <[email-masked]<mailto:[email-masked]>>, Rakesh R <[email-masked]<mailto:[email-masked]>>, Agarwal, Tanish (Cognizant) <[email-masked]<mailto:[email-masked]>>, R V, Krishnan (Cognizant) <[email-masked]<mailto:[email-masked]>>, pradeepa.karanth <[email-masked]<mailto:[email-masked]>>
Cc: Matthew Belyus <[email-masked]<mailto:[email-masked]>>, [email-masked]<mailto:[email-masked]> <[email-masked]<mailto:[email-masked]>>
Subject: [EXTERNAL] RE: Cognizant : Memory Metrics Utilization
Hi Greg, I think , you are still referring to Microsoft monitoring agent(MMA)/Log analytics agent , Our point itself, we do not required agent for this azure monitor data. Hence we are seeing the usage metrics in azure monitor for all components

Hi Greg,

I think , you are still referring to Microsoft monitoring agent(MMA)/Log analytics agent ,  Our point itself, we do not required agent for this azure monitor data.

Hence we are seeing the usage metrics in azure monitor for all components CPU, Disk, Network and memory. Etc

If you point azure monitor is depreciated, how and where cloudability is are getting the CPU, Network metrics currently? And how we are still seeing the usage metrics in Azure monitor.

We have got confirmation from Microsoft support team, that the metrics currently available for each of VMs is by default from hypervisor level to this azure monitor, which does not have dependency to deploy extension or agents(AMA). Attached the mail

We do not want to install agent and configure DCR as per new agent AMA for azure servers. Its not required as data is available already in azure monitor that we have verified today aswell, we are not referring to guest OS level metrics data.

This is certainly need changes on the cloud ability.

Pls fine the relevant article for MMA to AMA agent Migrate to Azure Monitor Agent from Log Analytics agent - Azure Monitor | Microsoft Learn<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.microsoft.com_en-2Dus_azure_azure-2Dmonitor_agents_azure-2Dmonitor-2Dagent-2Dmigration&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=UVANt5Zc2qcvZ4emxT03eoR270ZOQMfMfiOZihZqip8&e=>

Let us know , if you still need any more details, I will setup call along with Microsoft team.

@Rakesh R<mailto:[email-masked]>, pls share the recording link for our reference.

+ Deva

Regards,
Aron
IT - Technology Services

From: Greg Winfield [email-masked]<mailto:[email-masked]>
Sent: 11 July 2025 12:22 PM
To: Rakesh R <[email-masked]<mailto:[email-masked]>>; S, Aronbabu (Cognizant) <[email-masked]<mailto:[email-masked]>>; Agarwal, Tanish (Cognizant) <[email-masked]<mailto:[email-masked]>>; R V, Krishnan (Cognizant) <[email-masked]<mailto:[email-masked]>>; Karanth, Pradeepa (Cognizant) <[email-masked]<mailto:[email-masked]>>
Cc: Matthew Belyus <[email-masked]<mailto:[email-masked]>>
Subject: Re: Cognizant : Memory Metrics Utilization

CAUTION: External Email
Hi Team

Thanks for the call before.
I have just finished my discussion with Engineering.

To confirm – yes we do require an agent in Azure for memory metrics in Cloudability.  Apologies I understood that it was agentless – it used to be. However this has been changed. The reason behind this change is that Azure have deprecated Azure Monitor  in 2024 and replaced it with AMA and DCR (per your architects note) and as such ; it will no longer work with Cloudability. We have moved onto using PS to install the agent in the OS (which can also be pushed via policy)

https://www.ibm.com/docs/en/cloudability-commercial/cloudability-enterprise/saas?topic=ccma-cloudability-set-up-azure-memory-metrics-collection-using-azure-monitoring-agent

Hope this helps clarify why you are not seeing data in rightsizing with respect to memory.

Greg Winfield
Cloud Solution Architect & FinOps Instructor, Customer Success – APAC
[signature_3490166860][signature_246175199][signature_2497796681][A white and orange hexagon with black text    Description automatically generated][signature_3030986296]
Apptio, an IBM Company
[email-masked]<mailto:[email-masked]> M +61434850518<tel:+61434850518>
Upcoming Leave : 8/7, 28/7 – 1/8
[signature_538498607]

From: [email-masked]<mailto:[email-masked]>
When: 3:30 PM - 4:30 PM 11 July 2025
Subject: Cognizant : Memory Metrics Utilization
Location: Microsoft Teams Meeting

Hi Team,

As requested, scheduling the meeting to discuss on memory metric integration and utilization in cloudability.
Agenda:
•  Overview of Current Setup
•  Cloudability Requirements
•  Integration Options
•  Recommendations & Next Steps

Regards,
Rakesh Rajendran
Customer Success Manager - Cloud
Apptio, an IBM Company | FinOps | Technology Business Management
[email-masked]<mailto:[email-masked]>

________________________________________________________________________________
Microsoft Teams Need help?<https://urldefense.proofpoint.com/v2/url?u=https-3A__aka.ms_JoinTeamsMeeting-3Fomkt-3Den-2DIN&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=qU1VYOnAneK_4UEL3gnhfBVhgfKazrXwxTh9hEmrTdU&e=>
Join the meeting now<https://urldefense.proofpoint.com/v2/url?u=https-3A__teams.microsoft.com_l_meetup-2Djoin_19-253ameeting-5FZjIwY2Q3NmQtOTQzZC00ODE5LTk3ZWUtNzhjMzA3ZWE0MTlk-2540thread.v2_0-3Fcontext-3D-257b-2522Tid-2522-253a-2522fcf67057-2D50c9-2D4ad4-2D98f3-2Dffca64add9e9-2522-252c-2522Oid-2522-253a-2522210f0a46-2D336c-2D4af4-2D845c-2D39a653de4bab-2522-257d&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=lEQ6TH3hzvcGox-XcckWS9AfZANJjGkirjJeoWHabpI&e=>
Meeting ID: 297 101 665 822 6
Passcode: ML7fy9SS
________________________________
Dial in by phone
+91 22 6259 1389,,,,385454648#<tel:+912262591389,,,,385454648> India, Mumbai
Find a local number<https://urldefense.proofpoint.com/v2/url?u=https-3A__dialin.teams.microsoft.com_05ba6fbc-2Dcd5c-2D478f-2Da5ce-2D0352e02bd69d-3Fid-3D385454648&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=octBrkjB0IdQORwzBaEsZiWsTqDb1zDhv7AKZ50NBCI&e=>
Phone conference ID: 385 454 648#
Join on a video conferencing device
Tenant key: [email-masked]<mailto:[email-masked]>
Video ID: 113 970 736 7
More info<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.webex.com_msteams-3Fconfid-3D1139707367-26tenantkey-3Dibm-26domain-3Dm.webex.com&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=pSAwT_MtprXoQRFeezV4UnmyQmd1bEovjnVrz5zi5G0&e=>
For organizers: Meeting options<https://urldefense.proofpoint.com/v2/url?u=https-3A__teams.microsoft.com_meetingOptions_-3ForganizerId-3D210f0a46-2D336c-2D4af4-2D845c-2D39a653de4bab-26tenantId-3Dfcf67057-2D50c9-2D4ad4-2D98f3-2Dffca64add9e9-26threadId-3D19-5Fmeeting-5FZjIwY2Q3NmQtOTQzZC00ODE5LTk3ZWUtNzhjMzA3ZWE0MTlk-40thread.v2-26messageId-3D0-26language-3Den-2DIN&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=GnN0QIOlS-EnO5N4sipopusSG1CYc1DhCe9MfORub2k&e=> | Reset dial-in PIN<https://urldefense.proofpoint.com/v2/url?u=https-3A__dialin.teams.microsoft.com_usp_pstnconferencing&d=DwMGaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=Yuwj5JKWRMeY5L_x6dGIUAI9Kwqvf_YkEuBsJ3fQJMc&m=RMiwmdggTvoV0e7l9HLDjhPNdEYG0ufPPgv-uKwO8u8Pn-8Ez6487ce0bAKBeUEl&s=5Xkx088jVWPcw5YYmxHx-o7RXDCZi9kk9ueloI5FMi8&e=>
________________________________________________________________________________
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.