AIOps

 View Only
  • 1.  Mobile to Mainframe Observability Webinar

    Posted Thu May 05, 2022 03:36 PM
    Edited by Portia Melita Tue June 21, 2022 02:58 PM
    With Instana on z/OS, the critical work that is taking place is no longer a mystery to the rest of the organization. Calls to the mainframe can be viewed in application-context and show up integrated alongside the rest of the services being monitored by Instana. Regardless of your familiarity with the mainframe, you can identify Z-specific middleware resources supporting the given application (like CICS and IMS), get details on the API calls being made to those Z resources or gain insights into z/OS databases (like Db2 and VSAM) at the end of a transaction's journey.

    Please join us in this on-demand recording. Share your questions below and register to watch here.

    ------------------------------
    Trent Shupe
    ------------------------------


  • 2.  RE: Mobile to Mainframe Observability Webinar

    Posted Tue June 21, 2022 03:16 PM

    Hi everyone,

    You can watch the on demand recording here and download the slides here.

    Please share any of your questions below.



    ------------------------------
    Trent Shupe
    ------------------------------



  • 3.  RE: Mobile to Mainframe Observability Webinar

    Posted Wed June 22, 2022 01:59 AM
    -What are the list of errornuos code available for each application specifically the tomcat and dot net?
    -How to get this information from documentation? 
    -Do these erroneous code differ for application implemented on a regular VM, containerized or there is no difference?

    ------------------------------
    Mohamed Hassan
    Fingerprint Consultancy
    ------------------------------



  • 4.  RE: Mobile to Mainframe Observability Webinar

    Posted Thu June 23, 2022 09:32 AM
    Hi @Mohamed Hassan -
    Instana collects all HTTP status codes as per call results and shows them. So we don't have a list of them in our docs as we follow the w3c spec for this (I believe https://www.rfc-editor.org/rfc/rfc9110.html#name-server-error-5xx)
    rfc-editor.orgrfc-editor.org
    The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.


    ------------------------------
    Trent Shupe
    ------------------------------



  • 5.  RE: Mobile to Mainframe Observability Webinar

    Posted Thu June 23, 2022 10:36 AM
    Thanks Trent for update.

    Does this means Instana covers only the HTTP/HTTPS/URI errornuos codes only, I see in play with instana other errors like the uploaded screenshot.
    is it detected by instana by monitoring application log files or from where instana detect these errors?

    Thanks.


    ------------------------------
    Mohamed Hassan
    Fingerprint Consultancy
    ------------------------------



  • 6.  RE: Mobile to Mainframe Observability Webinar

    Posted Fri June 24, 2022 10:13 AM
    Hi Mohamed,

    In the case depicted in your screens, let me start explaining that  Instana has many sensors applied over the process:
    1. JVM sensor (infrastructure metrics)
    2. Java Tracer (calls)
    3. Elastic Search [ES] (API/operations)
    Each one provides information. The traces you attached are obtained by Java Tracer, there was an exception that's captured by the sensor, and the ES sensor provides more context.

    Instana cannot (yet) monitor log files. It detects language exceptions like the example, and messages with ERROR/WAR level of the logging framework used by the application.

    I hope the explanation helps.

    Luis