Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Performance data is currently not available for this entity" viewing the performance tab (79596)

Last Updated: 3/1/2023Categories: TroubleshootingTotal Views: 32204Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

While accessing the performance tab and navigating to Overview, you see:

No data available

The data is shown for Real time, but fails to retrieve it for past 1 day, week, month or year.

While selecting the advance parameter in performance tab, you see:

Performance data is currently not available for this entity

Cause

This issue is can happen when the vCenter Server database (Postgres) contains a stale or future time stamp reference for the ESXi host when the data was collected.

For vCenter Servers using SQL, see "Performance data is currently not available for this entity" error after updating rollup in vSphere

Resolution

Ensure that the system time on the affected ESXi is in sync with the vCenter

Backup the vCenter database. For more information, see Back up and restore vCenter Server Appliance/vCenter Server 6.x vPostgres database

Create a snapshot of the vCenter Server Appliance.

Log in to the vSphere Web Client and navigate to Advanced Settings:

Add a new advanced setting with the name config.vpxd.stats.maxQueryMetrics and the value 256.

Connect to vCenter Server Appliance through the console or using an SSH session along with root credentials.

Enable the shell by running this command:

# shell.set --enabled true

Type shell and press Enter.

Run this command to log in to the vCenter Server Appliance database:

# /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres

The next steps are depending on the version of vCenter Server. If you are using vCenter Server 6.7 or earlier, run steps 10 to 13. If you are using vCenter Server 7.0, run steps 14 to 17 instead.

For vCenter 6.7 or earlier, run the following query:

select id,dns_name,last_perf_time from vpx_host;

Example output:

id |      dns_name      |   last_perf_time
----+--------------------+---------------------
15 | esxi1.labs.org | 2020-06-10 17:45:00
18 | esxi2.labs.org | 2020-06-10 17:25:00
52 | esxi3.labs.org | 2020-06-10 17:40:00

Look for last_perf_time entries that are not close in time to the other entries:

id |      dns_name      |   last_perf_time
----+--------------------+---------------------
15 | esxi1.labs.org | 2020-06-10 17:45:00
18 | esxi2.labs.org | 2020-04-15 13:05:00    <-------- Problem host
52 | esxi3.labs.org | 2020-06-10 17:40:00

Run the following query to update the time stamp:

update vpx_host set last_perf_time=now() where id=’HOST_ID’;

In vCenter database confirm that host time has been updated ( After update)

id |      dns_name      |   last_perf_time
----+--------------------+---------------------
15 | esxi1.labs.org | 2020-06-10 17:45:00
18 | esxi2.labs.org | 2020-06-10 17:55:00
52 | esxi3.labs.org | 2020-06-10 17:28:00

In vCenter Server 7.0, the last_perf_time column was moved to the table vpx_host_perfinfo. Therefore run this command to list the hosts with their last_perf_time information:

select * from vpx_host_perfinfo;

Look for last_perf_time entries that are not close in time to the other entries:

host_id |       last_perf_time       | perf_refresh_rate
---------+----------------------------+-------------------
18022 | 2022-04-21 07:52:00        |                20
10029 | 2022-04-21 07:52:55        |                20
10011 | 2022-04-21 02:32:55        |                20  <----
10035 | 2022-04-21 07:52:55        |                20

Run the following query to update the time stamp:

update vpx_host_perfinfo set last_perf_time=now() where host_id='HOST_ID';

Verify that the field has been updated:

select * from vpx_host_perfinfo;
host_id |       last_perf_time       | perf_refresh_rate
---------+----------------------------+-------------------
18022 | 2022-04-21 07:52:00        |                20
10029 | 2022-04-21 07:52:55        |                20
10011 | 2022-04-21 07:54:00.123445 |                20
10035 | 2022-04-21 07:52:55        |                20

About 30-40 mins after running the steps above, the vCenter Server performance chart will start populating. Data collection of month, week will take more time.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
VMware AirWatch MDM Agent 6.5.11 for Windows Mobile/CE リリースのお知らせ (79610)

KB
•
Workspace ONE Intelligence 2020/06/17 リリースのお知らせ (79631)

KB
•
在 vRealize Automation 8.x 中，容器状态为 "挂起" 或 "已退出" (78929)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant