Metadata
  • 08 Mar 2024
  • 1 Minute to read
  • Contributors
  • Dark
    Light

Metadata

  • Dark
    Light

Article summary

Overview

Most of RealTheory's object and data models include rich metadata that enhances content discoverability and categorization.

This metadata combined with a custom query support within the RealTheory APIs provides the ability to quickly discover and find important and relevent content.

Examples

Below is an example of the metadata included within a Pod summary, which is an object that summarizes key information related to Kubernetes Pod workloads:

{
  "metadata": {
  "id": "a6095791-7552-474a-8865-85bfa2efd4b9",
  "name": "activity-6c467dfcd-jn2qg",
  "clusterId": "04fee66e-0078-4ed2-b1f1-0c234557fca3",
  "clusterName": "realtheory-cluster-01",
  "nodeId": "1206f66c-65a1-4ae6-a7cc-e5ced6cc2ae4",
  "nodeName": "aks-userpool-15373879-vmss000029",
  "customResourceDefinitionId": "00000000-0000-0000-0000-000000000000",
  "customResourceDefinitionName": "",
  "namespaceId": "53214960-fda3-4089-9e12-a7f476317352",
  "namespaceName": "real-theory-example",
  "serviceId": "2c5ac6e8-b806-4771-96db-f9f85bf1dca2",
  "serviceName": "activitysvc",
  "replicaSetId": "16bd764a-fa01-45e2-8854-46602dfeb3d4",
  "replicaSetName": "activity-6c467dfcd",
  "deploymentId": "1284d4ef-558a-4d57-8a2e-21e218f9a9f3",
  "deploymentName": "activity",
  "daemonSetId": "00000000-0000-0000-0000-000000000000",
  "daemonSetName": "",
  "statefulSetId": "00000000-0000-0000-0000-000000000000",
  "statefulSetName": "",
  "customResourceId": "00000000-0000-0000-0000-000000000000",
  "customResourceName": "",
  "jobId": "00000000-0000-0000-0000-000000000000",
  "jobName": "",
  "cronJobId": "00000000-0000-0000-0000-000000000000",
  "cronJobName": "",
  "owners": [
    {
      "kind": "ReplicaSet",
      "id": "16bd764a-fa01-45e2-8854-46602dfeb3d4",
      "name": "activity-6c467dfcd"
    }
  ],
  "timestamp": "2024-03-06T11:18:19.3938781Z"
},
...

In the example above, the metadata fields enables the user to quickly discover that the pod was scheduled via a Deployment called 'activity', which created a ReplicaSet called 'activity-6c467dfcd', within a Namespace called 'real-theory-example', and is accessible through a Service called 'activitysvc', which is running on Node 'aks-userpool-15373879-vmss000029', which is part of Cluster 'realtheory-cluster-01'.


Was this article helpful?

What's Next