[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[[["\u003cp\u003eThis API provides access to Datastore statistics, which track data like entity counts and property value sizes, for application analysis.\u003c/p\u003e\n"],["\u003cp\u003eDatastore statistics are represented as specially named entities, accessible via the Datastore API, with each statistic entity including properties like \u003ccode\u003ecount\u003c/code\u003e, \u003ccode\u003ebytes\u003c/code\u003e, and \u003ccode\u003etimestamp\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eStatistics are organized into different categories, including total statistics, namespace-specific statistics, and statistics specific to kinds, properties, and their types.\u003c/p\u003e\n"],["\u003cp\u003eDatastore progressively drops less critical statistics entities (e.g., per-namespace, per-kind, per-property) to manage storage overhead, while summary statistics like \u003ccode\u003e__Stat_Total__\u003c/code\u003e are always retained.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003e__Stat_Namespace__\u003c/code\u003e and \u003ccode\u003e__Stat_Ns_Total__\u003c/code\u003e entities both contain similar information, however they differ in their storage location and the presence of the \u003ccode\u003esubject_namespace\u003c/code\u003e field.\u003c/p\u003e\n"]]],[],null,["# Datastore Statistics in legacy bundled services\n\n| This API is supported for first-generation runtimes and can be used when [upgrading to corresponding second-generation runtimes](/appengine/docs/standard/\n| java-gen2\n|\n| /services/access). If you are updating to the App Engine Java 11/17 runtime, refer to the [migration guide](/appengine/migration-center/standard/migrate-to-second-gen/java-differences) to learn about your migration options for legacy bundled services.\n\nDatastore maintains statistics about the data stored for an\napplication, such as how many entities there are of a given kind, or how much\nspace is used by property values of a given type. You can view these statistics\nin the Google Cloud console, in the\n[Dashboard](https://console.cloud.google.com/datastore/stats) page.\n\nYou can also access these values programmatically within the application by\nquerying for specially named entities using the Datastore API.\nEach statistic is accessible as an entity whose kind name begins and ends with\ntwo underscores. For example, each app has exactly one entity of the kind\n`__Stat_Total__` that represents statistics about all of the entities in\nDatastore in total. Each statistic entity has the following\nproperties:\n\n- `count`, the number of items considered by the statistic (a long integer)\n- `bytes`, the total size of the items for this statistic (a long integer)\n- `timestamp`, the time of the most recent update to the statistic (a date-time value)\n\nSome statistic kinds also have additional properties, listed below.\n\nA Java application can access statistic entities using the low-level API. For\nexample: \n\n DatastoreService datastore = DatastoreServiceFactory.getDatastoreService();\n Entity globalStat = datastore.prepare(new Query(\"__Stat_Total__\")).asSingleEntity();\n Long totalBytes = (Long) globalStat.getProperty(\"bytes\");\n Long totalEntities = (Long) globalStat.getProperty(\"count\");\n\nWhen the statistics system creates new statistic entities, it does not delete\nthe old ones right away. The best way to get a consistent view of the\nstatistics is to query for the\n\n`__Stat_Total__`\nentity with the most recent\n`timestamp`, then use that timestamp value as a filter when fetching other\nstatistic entities.\n\nThe statistic entities are included in the calculated statistic values.\nStatistic entities take up space relative to the number of unique kinds and\nproperty names used by the application.\n\nThe statistics system will also create statistics specific to each\n[namespace](/appengine/docs/legacy/standard/java/multitenancy)\nNote that if an application does not use Datastore namespaces\nthen namespace specific statistics will not be created. Namespace specific stats\nare found in the namespace that they're specific to. The kind names for\nnamespace specific stats are prefixed with `__Stat_Ns_` and have the same\ncorresponding suffix as application wide statistics kinds.\n\nApplications with thousands of namespaces, kinds, or property names require a\nvery large number of statistics entities. To keep the overhead of storing and\nupdating the statistics reasonable, Datastore progressively\ndrops statistics entities, in the following order:\n\n- per-namespace, per-kind, and per-property statistics: `__Stat_Ns_PropertyName_Kind__`, `__Stat_Ns_PropertyType_PropertyName_Kind__`\n- per-kind and per-property statistics: `__Stat_PropertyName_Kind__`, `__Stat_PropertyType_PropertyName_Kind__`\n- per-namespace and per-kind statistics: `__Stat_Ns_Kind__`, `__Stat_Ns_Kind_IsRootEntity__`, `__Stat_Ns_Kind_NotRootEntity__`, `__Stat_Ns_PropertyType_Kind__`\n- per-kind statistics: `__Stat_Kind__`, `__Stat_Kind_IsRootEntity__`, `__Stat_Kind_NotRootEntity__`, `__Stat_PropertyType_Kind__`\n- per-namespace statistics: `__Stat_Namespace__`, `__Stat_Ns_Kind_CompositeIndex__`, `__Stat_Ns_PropertyType__`, `__Stat_Ns_Total__`\n\nThe summary statistics entities (`__Stat_Kind_CompositeIndex__`,\n`__Stat_PropertyType__`, `__Stat_Total__`) are never dropped.\n\nThe complete list of available statistics is as follows:\n\nSome statistics refer to Datastore property value types by\nname, as strings. These names are as follows:\n\n- `\"Blob\"`\n- `\"BlobKey\"`\n- `\"Boolean\"`\n- `\"Category\"`\n- `\"Date/Time\"`\n- `\"Email\"`\n- `\"Float\"`\n- `\"GeoPt\"`\n- `\"IM\"`\n- `\"Integer\"`\n- `\"Key\"`\n- `\"Link\"`\n- `\"NULL\"`\n- `\"PhoneNumber\"`\n- `\"PostalAddress\"`\n- `\"Rating\"`\n- `\"ShortBlob\"`\n- `\"String\"`\n- `\"Text\"`\n- `\"User\"`\n\n| **Note:** `__Stat_Namespace__` entities contain the same information found in `__Stat_Ns_Total__` records. `__Stat_Namespace__` entities are stored in the empty namespace and contain a `subject_namespace` field describing the namespace to which they belong. `__Stat_Ns_Total__` records are stored in the namespace to which they refer, and thus do not contain a `subject_namespace` field. Hence, a query on kind `__Stat_Namespace__` (from the empty string namespace) ordered descending by `bytes` will list the namespaces that consume the largest storage first. Because queries across namespaces are not possible, any query for `__Stat_Ns_Total__` entities will only ever produce at most a single record."]]