{"id":47635,"date":"2026-10-23T13:09:17","date_gmt":"2026-10-23T11:09:17","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=47635"},"modified":"2026-10-23T13:15:46","modified_gmt":"2026-10-23T11:15:46","slug":"metric-extension-export-format-enterprise-manager","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/","title":{"rendered":"Anatomy of an Enterprise Manager metric extension"},"content":{"rendered":"\n

Recently, I was working on deploying Metric Extensions automatically in Enterprise Manager, but the more I looked into it, the more it turned into a different question: what does a Metric Extension look like ? In a previous blog<\/a>, I presented the SYSMAN<\/code> tables containing the metric extensions definitions. I also showed how to retrieve the targets where a metric extension is deployed. Now, it\u2019s time to look at formatting metric extensions<\/strong>.<\/p>\n\n\n\n

Once again, emcli help<\/code> does not show any verb for creating metric extensions:<\/p>\n\n\n\n

$ emcli help | grep -i metric_extension\n    export_metric_extension           -- Export a metric extension to an archive file\n    get_unused_metric_extensions      -- Get a list of unused metric extensions\n    import_metric_extension           -- Import a metric extension archive file\n    publish_metric_extension          -- Publish a metric extension for use by all administrators\n    save_metric_extension_draft       -- Save a deployable draft of a metric extension<\/code><\/pre>\n\n\n\n
Unfortunately, nothing in the documentation will help us to create a metric extension outside of the web UI. So let\u2019s reverse engineer them. The plan is the following:<\/p>\n\n\n\n
    \n
  • Create metric extensions in the web UI<\/li>\n\n\n\n
  • Export the XML files with emcli<\/code><\/li>\n\n\n\n
  • Later, create new metric extensions or update existing metrics more easily, directly with emcli<\/code><\/li>\n<\/ul>\n\n\n\n
    Building a minimal metric extension<\/h2>\n\n\n\n
    Let\u2019s build the most basic metric extension first, with Host<\/code> as the target type. I will choose the OS Command - Multiple Columns<\/code> adapter, and just an echo<\/code> command.<\/p>\n\n\n
    \n
    \"\"<\/figure>\n<\/div>\n\n\n
    The adapter itself is \/bin\/echo<\/code> with em_result=1<\/code> as its argument and em_result=<\/code> as the Starts With<\/em> prefix. It is the same em_result=<\/code>-prefixed, delimiter-tokenized convention the OEM plugin\u2019s OSLineToken<\/code> fetchlet uses, which turned out not to be a coincidence (more on that below). One column, value<\/code>, type Number:<\/p>\n\n\n
    \n
    \"\"<\/figure>\n<\/div>\n\n\n
    The Test<\/strong><\/em> step lets you run the metric job for real against a live target before committing to anything. Since the idea is to have a valid archive that we can play with, it should definitely be tested.<\/p>\n\n\n
    \n
    \"\"<\/figure>\n<\/div>\n\n\n
    Exporting the metric extension<\/h2>\n\n\n\n
    You cannot export an Editable<\/em> metric. The docs restrict export_metric_extension<\/code> to Production, Deployable Draft, and Published<\/em> versions. So the first step is promoting it, either via the UI or with emcli<\/code>:<\/p>\n\n\n\n
    $ emcli save_metric_extension_draft -target_type=host -name='ME$minimal_uptime_check' -version=1<\/code><\/pre>\n\n\n\n
    Don\u2019t worry if you receive no output, this is expected. Then, you can export the metric:<\/p>\n\n\n\n
    $ emcli export_metric_extension -file_name=\/tmp\/minimal_uptime_check_v1.zip -target_type=host -name='ME$minimal_uptime_check' -version=1\nMetric extension [host, ME$minimal_uptime_check, 1] exported successfully to file \/tmp\/minimal_uptime_check_v1.zip<\/code><\/pre>\n\n\n\n
    There are three files in the archive:<\/p>\n\n\n\n
    metadata\/ME#24#minimal_uptime_check.xml\ncollection\/ME#24#minimal_uptime_check.xml\nmea.xml<\/code><\/pre>\n\n\n\n
    The first one is the manifest, mea.xml<\/code>:<\/p>\n\n\n\n
    <MetricExtensionArchive name=\"MEAME$minimal_uptime_check\">\n<MetricExtension name=\"ME$minimal_uptime_check\" type=\"host\" version=\"1\" is_repos=\"FALSE\" display_name=\"Minimal Uptime Check\" description=\"Minimal test ME - single OS command column, no credentials.\" version_comment=\" \" metadata_digest=\"18147044f9d9fab88c8ebbee213d2e1e\" coll_digest=\"e1a287a6df820c5e7d7fda0bd0bfcb3f\" attach_digest=\"d41d8cd98f00b204e9800998ecf8427e\">\n<\/MetricExtension>\n<\/MetricExtensionArchive><\/code><\/pre>\n\n\n\n
    The metric definition is in metadata\/ME#24#minimal_uptime_check.xml<\/code>:<\/p>\n\n\n\n
    <TargetMetadataExt EXT_NAME=\"ME$minimal_uptime_check\" EXT_VERSION=\"1\" TARGET_TYPE=\"host\"><Metric NAME=\"ME$minimal_uptime_check\" TYPE=\"TABLE\">\n<Display>\n<Label NLSID=\"NLS_METRIC_hostME$minimal_uptime_check\">Minimal Uptime Check<\/Label>\n<Description NLSID=\"NLS_DESCRIPTION_hostME$minimal_uptime_check\">Minimal test ME - single OS command column, no credentials.<\/Description>\n<\/Display>\n<TableDescriptor>\n<ColumnDescriptor NAME=\"value\" TYPE=\"NUMBER\">\n<Display>\n<Label NLSID=\"NLS_COLUMN_hostME$minimal_uptime_checkvalue\">Value<\/Label>\n<\/Display>\n<\/ColumnDescriptor>\n<\/TableDescriptor>\n<QueryDescriptor FETCHLET_ID=\"OSLineToken\">\n<Property NAME=\"command\" SCOPE=\"GLOBAL\">\/bin\/echo<\/Property>\n<Property NAME=\"scriptLoc\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">%scriptsDir%<\/Property>\n<Property NAME=\"args\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=1<\/Property>\n<Property NAME=\"delimiter\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">|<\/Property>\n<Property NAME=\"startsWith\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=<\/Property>\n<Property NAME=\"ENVEM_TARGET_NAME\" SCOPE=\"INSTANCE\" OPTIONAL=\"TRUE\">NAME<\/Property>\n<CredentialRef NAME=\"OSCreds\"><\/CredentialRef>\n<\/QueryDescriptor>\n<\/Metric>\n<\/TargetMetadataExt><\/code><\/pre>\n\n\n\n
    Here, we can see that:<\/p>\n\n\n\n
      \n
    • FETCHLET_ID=\"OSLineToken\"<\/code> is the same fetchlet<\/strong> a full OEM plugin\u2019s TargetMetadata<\/code> XML uses for its OSLineToken<\/code>-based collectors. The wizard is just generating the same fetchlet configuration.<\/li>\n\n\n\n
    • command<\/code>, args<\/code>, delimiter<\/code> and startsWith<\/code> are the basic properties<\/strong> fields the adapter step.<\/li>\n\n\n\n
    • ENVEM_TARGET_NAME<\/code> is set even though I did not alter the Environment Variables section. This is the default.<\/li>\n<\/ul>\n\n\n\n
      The last file, collection\/ME#24#minimal_uptime_check.xml<\/code>, is the schedule:<\/p>\n\n\n\n
      <TargetCollectionExt EXT_NAME=\"ME$minimal_uptime_check\" EXT_VERSION=\"1\" TARGET_TYPE=\"host\"><CollectionItem NAME=\"ME$minimal_uptime_check\" UPLOAD=\"YES\">\n\t<Schedule>\n\t\t<IntervalSchedule INTERVAL=\"15\" TIME_UNIT=\"Min\"\/>\n\t<\/Schedule>\n\t<MetricColl NAME=\"ME$minimal_uptime_check\">\n\t<\/MetricColl>\n<\/CollectionItem>\n<\/TargetCollectionExt><\/code><\/pre>\n\n\n\n
      Adding a second column and a real environment variable<\/h2>\n\n\n\n
      Let\u2019s build a second metric extension from the UI with the same command, but with two columns instead of one. I will also add a custom environment variable this time.<\/p>\n\n\n
      \n
      \"\"<\/figure>\n<\/div>\n\n\n
      For comparison, this is what the Environment Variables table looks like before you add anything to it: EM_TARGET_NAME<\/code> is already there.<\/p>\n\n\n
      \n
      \"\"<\/figure>\n<\/div>\n\n\n
      And the second column added on the Columns<\/em> step:<\/p>\n\n\n
      \n
      \"\"<\/figure>\n<\/div>\n\n\n
      Exporting this metric extension and comparing the metadata against the first archive shows exactly what each choice changes:<\/p>\n\n\n\n
      $ diff unpacked\/metadata\/*.xml unpacked_v2\/metadata\/*.xml\n1c1\n< <TargetMetadataExt EXT_NAME=\"ME$minimal_uptime_check\" EXT_VERSION=\"1\" TARGET_TYPE=\"host\"><Metric NAME=\"ME$minimal_uptime_check\" TYPE=\"TABLE\">\n---\n> <TargetMetadataExt EXT_NAME=\"ME$minimal_uptime_check_v2\" EXT_VERSION=\"1\" TARGET_TYPE=\"host\"><Metric NAME=\"ME$minimal_uptime_check_v2\" TYPE=\"TABLE\">\n3,4c3,4\n< <Label NLSID=\"NLS_METRIC_hostME$minimal_uptime_check\">Minimal Uptime Check<\/Label>\n< <Description NLSID=\"NLS_DESCRIPTION_hostME$minimal_uptime_check\">Minimal test ME - single OS command column, no credentials.<\/Description>\n---\n> <Label NLSID=\"NLS_METRIC_hostME$minimal_uptime_check_v2\">Minimal Uptime Check V2<\/Label>\n> <Description NLSID=\"NLS_DESCRIPTION_hostME$minimal_uptime_check_v2\">Variant with env var and 2 columns, for archive-format comparison.<\/Description>\n9c9,14\n< <Label NLSID=\"NLS_COLUMN_hostME$minimal_uptime_checkvalue\">Value<\/Label>\n---\n> <Label NLSID=\"NLS_COLUMN_hostME$minimal_uptime_check_v2value\">Value<\/Label>\n> <\/Display>\n> <\/ColumnDescriptor>\n> <ColumnDescriptor NAME=\"state\" TYPE=\"STRING\">\n> <Display>\n> <Label NLSID=\"NLS_COLUMN_hostME$minimal_uptime_check_v2state\">State<\/Label>\n16c21\n< <Property NAME=\"args\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=1<\/Property>\n---\n> <Property NAME=\"args\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=1|running<\/Property>\n19a25\n> <Property NAME=\"ENVMY_CUSTOM_VAR\" SCOPE=\"INSTANCE\" OPTIONAL=\"TRUE\">hello_world<\/Property><\/code><\/pre>\n\n\n\n
      The second extension was saved under a new name, ME$minimal_uptime_check_v2<\/code>, so every EXT_NAME<\/code>, NAME<\/code> and NLSID<\/code> differs. Removing this noise, there are three changes that matter: the new state<\/code> column, the args<\/code> property, and the environment variable ENVMY_CUSTOM_VAR<\/code>.<\/p>\n\n\n\n
      ...\n> <ColumnDescriptor NAME=\"state\" TYPE=\"STRING\">\n> <Display>\n> <Label NLSID=\"NLS_COLUMN_hostME$minimal_uptime_checkstate\">State<\/Label>\n> <\/Display>\n> <\/ColumnDescriptor>\n\n...\n\n< <Property NAME=\"args\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=1<\/Property>\n---\n> <Property NAME=\"args\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=1|running<\/Property>\n\n...\n\n> <Property NAME=\"ENVMY_CUSTOM_VAR\" SCOPE=\"INSTANCE\" OPTIONAL=\"TRUE\">hello_world<\/Property><\/code><\/pre>\n\n\n\n
      The new column is a second ColumnDescriptor<\/code>, in the same order as the pipe-delimited output (em_result=1|running<\/code>). The environment variable becomes ENVMY_CUSTOM_VAR=hello_world<\/code>.<\/p>\n\n\n\n
      Adding an uploaded script<\/h2>\n\n\n\n
      Both examples above run an OS command directly. Let\u2019s create a metric extension that runs an uploaded script<\/strong> instead of a literal command. Exporting a metric extension with an uploaded Perl script adds a fourth path to the archive, alongside the usual mea.xml<\/code>\/metadata<\/code>\/collection<\/code>:<\/p>\n\n\n\n
      mea.xml\nmetadata\/ME#24#script_uptime_check.xml\ncollection\/ME#24#script_uptime_check.xml\nscripts\/uptime_check.pl<\/code><\/pre>\n\n\n\n
      The manifest lists the script by its real name, in a <scripts><\/code> element, with an updated attach_digest<\/code> parameter.<\/p>\n\n\n\n
      <MetricExtensionArchive name=\"MEAME$script_uptime_check\">\n<MetricExtension name=\"ME$script_uptime_check\" type=\"host\" version=\"1\" is_repos=\"FALSE\" display_name=\"Script Uptime Check\" description=\"ME cloned from minimal_uptime_check, adapter modified to run an uploaded script.\" version_comment=\" \" metadata_digest=\"e4778d5b4a756fed3d7e73aa55931d88\" coll_digest=\"bc223105d5b2e6e31d5123eadcbd929b\" attach_digest=\"d04278db542142ccb9a89be64c3e151e\">\n<scripts name=\"uptime_check.pl\">\n<\/scripts>\n<\/MetricExtension>\n<\/MetricExtensionArchive><\/code><\/pre>\n\n\n\n
      The QueryDescriptor<\/code> has a new property called script<\/code>, giving the script name. The command<\/code> property is also updated, pointing at perl<\/code> instead of \/bin\/echo<\/code>.<\/p>\n\n\n\n
      <QueryDescriptor FETCHLET_ID=\"OSLineToken\">\n<Property NAME=\"command\" SCOPE=\"GLOBAL\">%perlBin%\/perl<\/Property>\n<Property NAME=\"script\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">%scriptsDir%\/uptime_check.pl<\/Property>\n<Property NAME=\"scriptLoc\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">%scriptsDir%<\/Property>\n<Property NAME=\"delimiter\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">|<\/Property>\n<Property NAME=\"startsWith\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=<\/Property>\n<Property NAME=\"ENVEM_TARGET_NAME\" SCOPE=\"INSTANCE\" OPTIONAL=\"TRUE\">NAME<\/Property>\n<CredentialRef NAME=\"OSCreds\"><\/CredentialRef>\n<\/QueryDescriptor><\/code><\/pre>\n\n\n\n
      Repository-side metric extension<\/h2>\n\n\n\n
      Let\u2019s conclude by creating a repository-side<\/strong> metric extension, which runs SQL against the OMS repository. With a repository-side Metric Extension<\/strong>, the FETCHLET_ID<\/code> is REPOSITORY_SQL<\/code>, and the properties are replaced by a Source<\/code> property containing the SQL query:<\/p>\n\n\n\n
      <QueryDescriptor FETCHLET_ID=\"REPOSITORY_SQL\">\n<Property NAME=\"Type\" SCOPE=\"GLOBAL\">SQL<\/Property>\n<Property NAME=\"Source\" SCOPE=\"GLOBAL\">SELECT target_guid,\n       target_type,\n       1 AS host_count\nFROM mgmt$target\nWHERE target_type = 'host'<\/Property>\n<\/QueryDescriptor><\/code><\/pre>\n\n\n\n
      In the manifest, is_repos=\"TRUE\"<\/code> is what differentiates this kind of metric extension. The <Metric><\/code> element itself picks up REPOSITORY=\"TRUE\"<\/code> too, and the columns default to the query SELECT<\/code> list (TARGET_TYPE<\/code>, HOST_COUNT<\/code> here) rather than anything typed by hand on the Columns step.<\/p>\n\n\n\n
      <MetricExtensionArchive name=\"MEAME$sql_target_count\">\n<MetricExtension name=\"ME$sql_target_count\" type=\"host\" version=\"1\" is_repos=\"TRUE\" display_name=\"SQL Target Count\" description=\"Test ME using the repository-side SQL adapter: counts targets by status.\" version_comment=\" \" metadata_digest=\"0ca6af88e017fb535ae2d59f7f1b6143\" coll_digest=\"e7be6de5a24037de10846bc29391bf2f\" attach_digest=\"d41d8cd98f00b204e9800998ecf8427e\">\n<\/MetricExtension>\n<\/MetricExtensionArchive><\/code><\/pre>\n\n\n\n
      With all of this in mind, let\u2019s try to feed the Enterprise Manager a custom metric extension built entirely by hand, using a small Python script as the collector instead of a literal command.<\/p>\n\n\n\n
      Import our first custom metric extension<\/h2>\n\n\n\n
      Here is a script reading the 1-minute load average from \/proc\/loadavg<\/code> and printing it with the same em_result=<\/code> prefix expected by OSLineToken<\/code>.<\/p>\n\n\n\n
      #!\/usr\/bin\/env python3\nwith open(\"\/proc\/loadavg\") as f:\n    load1 = f.read().split()[0]\nprint(f\"em_result={load1}\")<\/code><\/pre>\n\n\n\n
      We have three XML files and the script, written by hand rather than exported from the wizard. metadata\/ME#24#python_load_check.xml<\/code>:<\/p>\n\n\n\n
      <TargetMetadataExt EXT_NAME=\"ME$python_load_check\" EXT_VERSION=\"1\" TARGET_TYPE=\"host\"><Metric NAME=\"ME$python_load_check\" TYPE=\"TABLE\">\n<Display>\n<Label NLSID=\"NLS_METRIC_hostME$python_load_check\">Python Load Check<\/Label>\n<Description NLSID=\"NLS_DESCRIPTION_hostME$python_load_check\">Runs an uploaded Python script that reads the 1-minute load average from \/proc\/loadavg.<\/Description>\n<\/Display>\n<TableDescriptor>\n<ColumnDescriptor NAME=\"value\" TYPE=\"NUMBER\">\n<Display>\n<Label NLSID=\"NLS_COLUMN_hostME$python_load_checkvalue\">Value<\/Label>\n<\/Display>\n<\/ColumnDescriptor>\n<\/TableDescriptor>\n<QueryDescriptor FETCHLET_ID=\"OSLineToken\">\n<Property NAME=\"command\" SCOPE=\"GLOBAL\">\/usr\/bin\/python3<\/Property>\n<Property NAME=\"script\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">%scriptsDir%\/load_check.py<\/Property>\n<Property NAME=\"scriptLoc\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">%scriptsDir%<\/Property>\n<Property NAME=\"delimiter\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">|<\/Property>\n<Property NAME=\"startsWith\" SCOPE=\"GLOBAL\" OPTIONAL=\"TRUE\">em_result=<\/Property>\n<Property NAME=\"ENVEM_TARGET_NAME\" SCOPE=\"INSTANCE\" OPTIONAL=\"TRUE\">NAME<\/Property>\n<CredentialRef NAME=\"OSCreds\"><\/CredentialRef>\n<\/QueryDescriptor>\n<\/Metric>\n<\/TargetMetadataExt><\/code><\/pre>\n\n\n\n
      The command<\/code> property points at the interpreter (\/usr\/bin\/python3<\/code> instead of %perlBin%\/perl<\/code>), while script<\/code> points at the uploaded file. Everything else is untouched. Here is the collection\/ME#24#python_load_check.xml<\/code> file:<\/p>\n\n\n\n
      <TargetCollectionExt EXT_NAME=\"ME$python_load_check\" EXT_VERSION=\"1\" TARGET_TYPE=\"host\"><CollectionItem NAME=\"ME$python_load_check\" UPLOAD=\"YES\">\n\t<Schedule>\n\t\t<IntervalSchedule INTERVAL=\"15\" TIME_UNIT=\"Min\"\/>\n\t<\/Schedule>\n\t<MetricColl NAME=\"ME$python_load_check\">\n\t<\/MetricColl>\n<\/CollectionItem>\n<\/TargetCollectionExt><\/code><\/pre>\n\n\n\n
      And the manifest mea.xml<\/code>:<\/p>\n\n\n\n
      <MetricExtensionArchive name=\"MEAME$python_load_check\">\n<MetricExtension name=\"ME$python_load_check\" type=\"host\" version=\"1\" is_repos=\"FALSE\" display_name=\"Python Load Check\" description=\"Runs an uploaded Python script that reads the 1-minute load average from \/proc\/loadavg.\" version_comment=\" \" metadata_digest=\"0000000000000000000000000000000\" coll_digest=\"0000000000000000000000000000000\" attach_digest=\"0000000000000000000000000000000\">\n<scripts name=\"load_check.py\">\n<\/scripts>\n<\/MetricExtension>\n<\/MetricExtensionArchive><\/code><\/pre>\n\n\n\n
      The digests are just zeroes here. The OMS recomputes and stores new digests when you import the metric.<\/p>\n\n\n\n
      Now, let\u2019s build the archive with the same layout export_metric_extension<\/code> produces, assembled by hand instead:<\/p>\n\n\n\n
      $ find build -type f\nbuild\/mea.xml\nbuild\/metadata\/ME#24#python_load_check.xml\nbuild\/collection\/ME#24#python_load_check.xml\nbuild\/scripts\/load_check.py\n\n$ cd build && zip -rq ..\/python_load_check.zip . && cd ..\n$ unzip -l python_load_check.zip\nArchive:  python_load_check.zip\n  Length      Date    Time    Name\n---------  ---------- -----   ----\n        0  08-27-2026 14:38   metadata\/\n     1212  08-27-2026 14:38   metadata\/ME#24#python_load_check.xml\n        0  08-27-2026 14:38   collection\/\n      321  08-27-2026 14:38   collection\/ME#24#python_load_check.xml\n        0  08-27-2026 14:38   scripts\/\n      116  08-27-2026 14:38   scripts\/load_check.py\n      529  08-27-2026 14:38   mea.xml\n---------                     -------\n     2178                     7 files<\/code><\/pre>\n\n\n\n
      The last step is to import the metric extension with emcli<\/code>:<\/p>\n\n\n\n
      $ emcli import_metric_extension -file_name=python_load_check.zip\nMetric extension file python_load_check.zip imported successfully<\/code><\/pre>\n\n\n\n
      You now know how to build metric extensions without going through the web UI.<\/p>\n","protected":false},"excerpt":{"rendered":"
      Recently, I was working on deploying Metric Extensions automatically in Enterprise Manager, but the more I looked into it, the more it turned into a different question: what does a Metric Extension look like ? In a previous blog, I presented the SYSMAN tables containing the metric extensions definitions. I also showed how to retrieve […]<\/p>\n","protected":false},"author":152,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_members_access_role":[],"_members_access_error":""},"categories":[3683,59],"tags":[4214,4047,4277,761],"type_dbi":[4216,4048,4278,4010],"class_list":["post-47635","post","type-post","status-publish","format-standard","hentry","category-monitoring","category-oracle","tag-emcli","tag-enterprise-manager","tag-metric-extension-2","tag-oem","type-emcli","type-enterprise-manager","type-metric-extension-3","type-oem"],"acf":[],"yoast_head":"\nAnatomy of an Enterprise Manager metric extension - dbi Blog<\/title>\n<meta name=\"description\" content=\"The archive format of an Enterprise Manager metric extension: no emcli verb defines one, so I built it by hand and exported it.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Anatomy of an Enterprise Manager metric extension\" \/>\n<meta property=\"og:description\" content=\"The archive format of an Enterprise Manager metric extension: no emcli verb defines one, so I built it by hand and exported it.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-23T11:09:17+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-23T11:15:46+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/10\/001_me-genprop-filled.png\" \/>\n\t<meta property=\"og:image:width\" content=\"720\" \/>\n\t<meta property=\"og:image:height\" content=\"405\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Julien Delattre\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Julien Delattre\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/\"},\"author\":{\"name\":\"Julien Delattre\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/812297b963933317cfcbbf006a273eec\"},\"headline\":\"Anatomy of an Enterprise Manager metric extension\",\"datePublished\":\"2026-10-23T11:09:17+00:00\",\"dateModified\":\"2026-10-23T11:15:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/\"},\"wordCount\":831,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/10\\\/001_me-genprop-filled.png\",\"keywords\":[\"emcli\",\"enterprise manager\",\"metric extension\",\"OEM\"],\"articleSection\":[\"Monitoring\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/\",\"name\":\"Anatomy of an Enterprise Manager metric extension - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/10\\\/001_me-genprop-filled.png\",\"datePublished\":\"2026-10-23T11:09:17+00:00\",\"dateModified\":\"2026-10-23T11:15:46+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/812297b963933317cfcbbf006a273eec\"},\"description\":\"The archive format of an Enterprise Manager metric extension: no emcli verb defines one, so I built it by hand and exported it.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/10\\\/001_me-genprop-filled.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/10\\\/001_me-genprop-filled.png\",\"width\":720,\"height\":405},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/metric-extension-export-format-enterprise-manager\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Anatomy of an Enterprise Manager metric extension\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/812297b963933317cfcbbf006a273eec\",\"name\":\"Julien Delattre\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a97d00e680bbf237126e24b65281cbcb66cd20bd1ed2d14bf928991b2bf68eb5?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a97d00e680bbf237126e24b65281cbcb66cd20bd1ed2d14bf928991b2bf68eb5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a97d00e680bbf237126e24b65281cbcb66cd20bd1ed2d14bf928991b2bf68eb5?s=96&d=mm&r=g\",\"caption\":\"Julien Delattre\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/juliendelattre\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Anatomy of an Enterprise Manager metric extension - dbi Blog","description":"The archive format of an Enterprise Manager metric extension: no emcli verb defines one, so I built it by hand and exported it.","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:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/","og_locale":"en_US","og_type":"article","og_title":"Anatomy of an Enterprise Manager metric extension","og_description":"The archive format of an Enterprise Manager metric extension: no emcli verb defines one, so I built it by hand and exported it.","og_url":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/","og_site_name":"dbi Blog","article_published_time":"2026-10-23T11:09:17+00:00","article_modified_time":"2026-10-23T11:15:46+00:00","og_image":[{"width":720,"height":405,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/10\/001_me-genprop-filled.png","type":"image\/png"}],"author":"Julien Delattre","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Julien Delattre","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/"},"author":{"name":"Julien Delattre","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/812297b963933317cfcbbf006a273eec"},"headline":"Anatomy of an Enterprise Manager metric extension","datePublished":"2026-10-23T11:09:17+00:00","dateModified":"2026-10-23T11:15:46+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/"},"wordCount":831,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/10\/001_me-genprop-filled.png","keywords":["emcli","enterprise manager","metric extension","OEM"],"articleSection":["Monitoring","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/","url":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/","name":"Anatomy of an Enterprise Manager metric extension - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/10\/001_me-genprop-filled.png","datePublished":"2026-10-23T11:09:17+00:00","dateModified":"2026-10-23T11:15:46+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/812297b963933317cfcbbf006a273eec"},"description":"The archive format of an Enterprise Manager metric extension: no emcli verb defines one, so I built it by hand and exported it.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/10\/001_me-genprop-filled.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/10\/001_me-genprop-filled.png","width":720,"height":405},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/metric-extension-export-format-enterprise-manager\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Anatomy of an Enterprise Manager metric extension"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/812297b963933317cfcbbf006a273eec","name":"Julien Delattre","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a97d00e680bbf237126e24b65281cbcb66cd20bd1ed2d14bf928991b2bf68eb5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a97d00e680bbf237126e24b65281cbcb66cd20bd1ed2d14bf928991b2bf68eb5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a97d00e680bbf237126e24b65281cbcb66cd20bd1ed2d14bf928991b2bf68eb5?s=96&d=mm&r=g","caption":"Julien Delattre"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/juliendelattre\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/47635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/152"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=47635"}],"version-history":[{"count":4,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/47635\/revisions"}],"predecessor-version":[{"id":48059,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/47635\/revisions\/48059"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=47635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=47635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=47635"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=47635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}