{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "item": { "id": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "slug": "bind-an-axis-analytics-publisher-to-a-discovered-data-source", "url": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source.md", "json": "https://update.dsesecurity.com/api/v1/posts/bind-an-axis-analytics-publisher-to-a-discovered-data-source/" }, "title": "Bind an Axis analytics publisher to a discovered data source", "summary": "Choose an actual discovered analytics producer key and explicitly review MQTT topic-prefix handling before creating a publisher. Demonstration keys do not establish the deployment’s data contract.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-30T06:05:05+00:00", "modified_at": "2026-10-30T06:05:13+00:00", "reviewed_on": "2026-10-30", "reading_minutes": 3, "word_count": 513, "potentially_affected": "Axis devices exposing the documented Analytics MQTT API; producer availability, payload contract and broker configuration require separate confirmation.", "dse_recommendation": "DSE recommends reviewing the discovered source key, publisher identity, topic and prefix selection as one explicit routing record.", "primary_source": { "name": "Axis Communications — Analytics MQTT API", "url": "https://developer.axis.com/vapix/device-configuration/analytics-mqtt-api/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Bind the publisher to an actual analytics data source and a reviewed MQTT destination. Resolve the prefix choice before looking for the message under a guessed topic.

\n

Source fact: documented behavior

\n

The Analytics MQTT API describes analytics data sources as camera-side producers whose data can be sent by publishers to MQTT topics.

\n

The documented data-source collection returns source keys, while adding a publisher requires id, data_source_key and mqtt_topic.

\n

The publisher’s use_topic_prefix property selects use of the topic prefix configured in the MQTT client.

\n

What the source does not establish

\n

This article selects a producer-to-topic mapping. It does not certify an analytics payload schema, availability of a demonstration producer, broker authorization or guaranteed message delivery. Keep example keys separate from the keys returned by the actual device and review the producer’s applicable contract independently.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends reviewing the discovered source key, publisher identity, topic and prefix selection as one explicit routing record.

\n
    \n
  1. Retrieve the available analytics source keys using the supported read workflow. Match the required producer to the actual returned identity and its applicable data documentation. Keep demonstration identifiers out of the deployment request unless the device itself returns that exact supported key. Record an unavailable producer as an applicability gap instead of substituting the nearest-looking name.
    2. \n
  2. Prepare a publisher record with a unique approved identifier and the intended topic. Review the MQTT client’s existing prefix alongside the publisher’s prefix-use choice. Ask the consumer owner to name the final destination they expect to observe. Preserve that agreement separately from evidence that a broker connection is established or an event-topic bridge is configured.
    3. \n
  3. Create only the approved test publisher through the documented administrative workflow and retrieve the resulting publisher list. Compare the source mapping and route with the reviewed record. Use a logging-only test consumer where practical, then inspect the actual received topic before allowing the data to drive another action. Remove the temporary publisher through its supported lifecycle after the exercise.
    4. \n
\n

Verification and evidence

\n

Proposed verification: use a permitted producer input and record the actual broker-side topic with a sanitized sample. Compare it with the expected prefixed or unprefixed route. Keep the producer key and publisher identity beside that observation so another reviewer can trace the message to the intended configuration.

\n

Review a desk fixture in which the consumer watches an unprefixed name while the configuration intentionally uses the client prefix. Require the reviewer to reconcile the route before changing credentials or broadening subscriptions. This is a proposed diagnostic case, not an observed outage. No publisher was created or MQTT delivery tested for this article.

\n

Official references

\n\n

Source review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.

\n", "content_text": "Bottom line: Bind the publisher to an actual analytics data source and a reviewed MQTT destination. Resolve the prefix choice before looking for the message under a guessed topic.\nSource fact: documented behavior\nThe Analytics MQTT API describes analytics data sources as camera-side producers whose data can be sent by publishers to MQTT topics.\nThe documented data-source collection returns source keys, while adding a publisher requires id, data_source_key and mqtt_topic.\nThe publisher’s use_topic_prefix property selects use of the topic prefix configured in the MQTT client.\nWhat the source does not establish\nThis article selects a producer-to-topic mapping. It does not certify an analytics payload schema, availability of a demonstration producer, broker authorization or guaranteed message delivery. Keep example keys separate from the keys returned by the actual device and review the producer’s applicable contract independently.\nApplicability questions\n\nWhich producer key does the actual device return?\nWhat publisher identifier and destination topic are approved?\nShould the MQTT client’s configured prefix participate?\nWhich consumer and broker-side observation will verify the final route?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reviewing the discovered source key, publisher identity, topic and prefix selection as one explicit routing record.\n\nRetrieve the available analytics source keys using the supported read workflow. Match the required producer to the actual returned identity and its applicable data documentation. Keep demonstration identifiers out of the deployment request unless the device itself returns that exact supported key. Record an unavailable producer as an applicability gap instead of substituting the nearest-looking name.\nPrepare a publisher record with a unique approved identifier and the intended topic. Review the MQTT client’s existing prefix alongside the publisher’s prefix-use choice. Ask the consumer owner to name the final destination they expect to observe. Preserve that agreement separately from evidence that a broker connection is established or an event-topic bridge is configured.\nCreate only the approved test publisher through the documented administrative workflow and retrieve the resulting publisher list. Compare the source mapping and route with the reviewed record. Use a logging-only test consumer where practical, then inspect the actual received topic before allowing the data to drive another action. Remove the temporary publisher through its supported lifecycle after the exercise.\n\nVerification and evidence\nProposed verification: use a permitted producer input and record the actual broker-side topic with a sanitized sample. Compare it with the expected prefixed or unprefixed route. Keep the producer key and publisher identity beside that observation so another reviewer can trace the message to the intended configuration.\nReview a desk fixture in which the consumer watches an unprefixed name while the configuration intentionally uses the client prefix. Require the reviewer to reconcile the route before changing credentials or broadening subscriptions. This is a proposed diagnostic case, not an observed outage. No publisher was created or MQTT delivery tested for this article.\nOfficial references\n\nAnalytics MQTT API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.", "content_markdown": "Bottom line: Bind the publisher to an actual analytics data source and a reviewed MQTT destination. Resolve the prefix choice before looking for the message under a guessed topic.\n\n## Source fact: documented behavior\n\nThe [Analytics MQTT API](https://developer.axis.com/vapix/device-configuration/analytics-mqtt-api/) describes analytics data sources as camera-side producers whose data can be sent by publishers to MQTT topics.\n\nThe documented data-source collection returns source keys, while adding a publisher requires id, data_source_key and mqtt_topic.\n\nThe publisher’s use_topic_prefix property selects use of the topic prefix configured in the MQTT client.\n\n## What the source does not establish\n\nThis article selects a producer-to-topic mapping. It does not certify an analytics payload schema, availability of a demonstration producer, broker authorization or guaranteed message delivery. Keep example keys separate from the keys returned by the actual device and review the producer’s applicable contract independently.\n\n## Applicability questions\n\n- Which producer key does the actual device return?\n\n- What publisher identifier and destination topic are approved?\n\n- Should the MQTT client’s configured prefix participate?\n\n- Which consumer and broker-side observation will verify the final route?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends reviewing the discovered source key, publisher identity, topic and prefix selection as one explicit routing record.\n\n- Retrieve the available analytics source keys using the supported read workflow. Match the required producer to the actual returned identity and its applicable data documentation. Keep demonstration identifiers out of the deployment request unless the device itself returns that exact supported key. Record an unavailable producer as an applicability gap instead of substituting the nearest-looking name.\n\n- Prepare a publisher record with a unique approved identifier and the intended topic. Review the MQTT client’s existing prefix alongside the publisher’s prefix-use choice. Ask the consumer owner to name the final destination they expect to observe. Preserve that agreement separately from evidence that a broker connection is established or an event-topic bridge is configured.\n\n- Create only the approved test publisher through the documented administrative workflow and retrieve the resulting publisher list. Compare the source mapping and route with the reviewed record. Use a logging-only test consumer where practical, then inspect the actual received topic before allowing the data to drive another action. Remove the temporary publisher through its supported lifecycle after the exercise.\n\n## Verification and evidence\n\nProposed verification: use a permitted producer input and record the actual broker-side topic with a sanitized sample. Compare it with the expected prefixed or unprefixed route. Keep the producer key and publisher identity beside that observation so another reviewer can trace the message to the intended configuration.\n\nReview a desk fixture in which the consumer watches an unprefixed name while the configuration intentionally uses the client prefix. Require the reviewer to reconcile the route before changing credentials or broadening subscriptions. This is a proposed diagnostic case, not an observed outage. No publisher was created or MQTT delivery tested for this article.\n\n## Official references\n\n- [Analytics MQTT API](https://developer.axis.com/vapix/device-configuration/analytics-mqtt-api/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "url": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-30" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Networks & Infrastructure", "item": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "@type": "ListItem", "position": 3, "name": "Bind an Axis analytics publisher to a discovered data source", "item": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/#article", "identifier": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "url": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/", "headline": "Bind an Axis analytics publisher to a discovered data source", "description": "Choose an actual discovered analytics producer key and explicitly review MQTT topic-prefix handling before creating a publisher.", "abstract": "Choose an actual discovered analytics producer key and explicitly review MQTT topic-prefix handling before creating a publisher. Demonstration keys do not establish the deployment’s data contract.", "articleBody": "Bottom line: Bind the publisher to an actual analytics data source and a reviewed MQTT destination. Resolve the prefix choice before looking for the message under a guessed topic.\nSource fact: documented behavior\nThe Analytics MQTT API describes analytics data sources as camera-side producers whose data can be sent by publishers to MQTT topics.\nThe documented data-source collection returns source keys, while adding a publisher requires id, data_source_key and mqtt_topic.\nThe publisher’s use_topic_prefix property selects use of the topic prefix configured in the MQTT client.\nWhat the source does not establish\nThis article selects a producer-to-topic mapping. It does not certify an analytics payload schema, availability of a demonstration producer, broker authorization or guaranteed message delivery. Keep example keys separate from the keys returned by the actual device and review the producer’s applicable contract independently.\nApplicability questions\n\nWhich producer key does the actual device return?\nWhat publisher identifier and destination topic are approved?\nShould the MQTT client’s configured prefix participate?\nWhich consumer and broker-side observation will verify the final route?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reviewing the discovered source key, publisher identity, topic and prefix selection as one explicit routing record.\n\nRetrieve the available analytics source keys using the supported read workflow. Match the required producer to the actual returned identity and its applicable data documentation. Keep demonstration identifiers out of the deployment request unless the device itself returns that exact supported key. Record an unavailable producer as an applicability gap instead of substituting the nearest-looking name.\nPrepare a publisher record with a unique approved identifier and the intended topic. Review the MQTT client’s existing prefix alongside the publisher’s prefix-use choice. Ask the consumer owner to name the final destination they expect to observe. Preserve that agreement separately from evidence that a broker connection is established or an event-topic bridge is configured.\nCreate only the approved test publisher through the documented administrative workflow and retrieve the resulting publisher list. Compare the source mapping and route with the reviewed record. Use a logging-only test consumer where practical, then inspect the actual received topic before allowing the data to drive another action. Remove the temporary publisher through its supported lifecycle after the exercise.\n\nVerification and evidence\nProposed verification: use a permitted producer input and record the actual broker-side topic with a sanitized sample. Compare it with the expected prefixed or unprefixed route. Keep the producer key and publisher identity beside that observation so another reviewer can trace the message to the intended configuration.\nReview a desk fixture in which the consumer watches an unprefixed name while the configuration intentionally uses the client prefix. Require the reviewer to reconcile the route before changing credentials or broadening subscriptions. This is a proposed diagnostic case, not an observed outage. No publisher was created or MQTT delivery tested for this article.\nOfficial references\n\nAnalytics MQTT API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 30, 2026. Recheck the official source and deployment-specific applicability before changing production settings.", "datePublished": "2026-10-30T06:05:05+00:00", "dateModified": "2026-10-30T06:05:13+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/bind-an-axis-analytics-publisher-to-a-discovered-data-source/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Bind an Axis analytics publisher to a discovered data source" }, "articleSection": [ "Networks & Infrastructure", "Video Surveillance" ], "keywords": [ "Networks & Infrastructure", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 513, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Analytics MQTT API", "url": "https://developer.axis.com/vapix/device-configuration/analytics-mqtt-api/" } } ] } }