{"componentChunkName":"component---src-templates-default-template-tsx","path":"/documentation/best_practices/monitoring/","result":{"data":{"asciidoc":{"id":"7e334081-8310-57a7-8718-ddb0b12cc27b","html":"
\n
Table of Contents
\n\n
\n
\n

\"HIROMON\" monitoring issues

\n
\n
\n

To specifically mark an automation issue as \"monitoring\" issue that is only meant to verify proper operation of the platform, the ogit/subject attribute of such issues must start with the string HIROMON (all uppercase).

\n
\n
\n

As HIROMON issues are assumed to be purely for monitoring purpose, they will be handled slightly different by certain parts of the platform:

\n
\n
\n
    \n
  • \n

    No teaching sessions will be created out of these issues

    \n
    • \n
  • \n

    These issues will not be counted by statistics generated by the platform

    \n
    • \n
  • \n

    In order to see these issues in the Task Inspector, the \"Monitoring\" switch has to be enabled, otherwise they will be filtered from the list

    \n
    • \n
\n
\n
\n
","document":{"main":"Monitoring the HIRO platform","title":"Monitoring the HIRO platform","subtitle":""},"fields":{"toc":true,"location":["documentation","best_practices","monitoring"]}},"sidebarYaml":{"id":"6d066bdd-c982-5a69-b909-a31e6fc044e0","showIndex":null}},"pageContext":{"id":"7e334081-8310-57a7-8718-ddb0b12cc27b","parent":"documentation"}},"staticQueryHashes":["1010459453","1010459453","2356112386","2356112386","2603905930","2603905930","3026652197","3026652197","3167850324","3167850324","63159454","63159454"]}