CLI to monitor connection pool in OpenShift










0














I have used Istio's circuitbreaker settings that ejects a host from connection pool based on number of consecutive errors. Is there a way to monitor the connection pool using command line and see the changes to host id or something like that?










share|improve this question


























    0














    I have used Istio's circuitbreaker settings that ejects a host from connection pool based on number of consecutive errors. Is there a way to monitor the connection pool using command line and see the changes to host id or something like that?










    share|improve this question
























      0












      0








      0







      I have used Istio's circuitbreaker settings that ejects a host from connection pool based on number of consecutive errors. Is there a way to monitor the connection pool using command line and see the changes to host id or something like that?










      share|improve this question













      I have used Istio's circuitbreaker settings that ejects a host from connection pool based on number of consecutive errors. Is there a way to monitor the connection pool using command line and see the changes to host id or something like that?







      openshift istio






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 5:46









      AruAru

      1




      1






















          1 Answer
          1






          active

          oldest

          votes


















          1














          Using the command line tool, I'm not sure. But the load-balancing pool size is stored in Envoy metrics (see membership healthy / total and outlier detection stats: https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_stats#health-check-statistics ). So, if you have istio's prometheus running, you can open its UI and view the values (or curl it with prometheus rest api).



          Example of metric name:
          envoy_cluster_inbound_8080__my_service_my_namespace_svc_cluster_local_membership_healthy



          Where 8080 is the port of your service, my_service is its name, my_namespace its namespace. There's also a similiar one for outbound: envoy_cluster_outbound_(etc.)



          In Istio 1.1 these metrics are reorganized into a format more suitable for Prometheus, so the names change a little bit and service name / namespace become label instead of being part of the name.



          Note that Kiali ( https://www.kiali.io/ ) shows this health information.






          share|improve this answer




















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53274571%2fcli-to-monitor-connection-pool-in-openshift%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Using the command line tool, I'm not sure. But the load-balancing pool size is stored in Envoy metrics (see membership healthy / total and outlier detection stats: https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_stats#health-check-statistics ). So, if you have istio's prometheus running, you can open its UI and view the values (or curl it with prometheus rest api).



            Example of metric name:
            envoy_cluster_inbound_8080__my_service_my_namespace_svc_cluster_local_membership_healthy



            Where 8080 is the port of your service, my_service is its name, my_namespace its namespace. There's also a similiar one for outbound: envoy_cluster_outbound_(etc.)



            In Istio 1.1 these metrics are reorganized into a format more suitable for Prometheus, so the names change a little bit and service name / namespace become label instead of being part of the name.



            Note that Kiali ( https://www.kiali.io/ ) shows this health information.






            share|improve this answer

























              1














              Using the command line tool, I'm not sure. But the load-balancing pool size is stored in Envoy metrics (see membership healthy / total and outlier detection stats: https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_stats#health-check-statistics ). So, if you have istio's prometheus running, you can open its UI and view the values (or curl it with prometheus rest api).



              Example of metric name:
              envoy_cluster_inbound_8080__my_service_my_namespace_svc_cluster_local_membership_healthy



              Where 8080 is the port of your service, my_service is its name, my_namespace its namespace. There's also a similiar one for outbound: envoy_cluster_outbound_(etc.)



              In Istio 1.1 these metrics are reorganized into a format more suitable for Prometheus, so the names change a little bit and service name / namespace become label instead of being part of the name.



              Note that Kiali ( https://www.kiali.io/ ) shows this health information.






              share|improve this answer























                1












                1








                1






                Using the command line tool, I'm not sure. But the load-balancing pool size is stored in Envoy metrics (see membership healthy / total and outlier detection stats: https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_stats#health-check-statistics ). So, if you have istio's prometheus running, you can open its UI and view the values (or curl it with prometheus rest api).



                Example of metric name:
                envoy_cluster_inbound_8080__my_service_my_namespace_svc_cluster_local_membership_healthy



                Where 8080 is the port of your service, my_service is its name, my_namespace its namespace. There's also a similiar one for outbound: envoy_cluster_outbound_(etc.)



                In Istio 1.1 these metrics are reorganized into a format more suitable for Prometheus, so the names change a little bit and service name / namespace become label instead of being part of the name.



                Note that Kiali ( https://www.kiali.io/ ) shows this health information.






                share|improve this answer












                Using the command line tool, I'm not sure. But the load-balancing pool size is stored in Envoy metrics (see membership healthy / total and outlier detection stats: https://www.envoyproxy.io/docs/envoy/latest/configuration/cluster_manager/cluster_stats#health-check-statistics ). So, if you have istio's prometheus running, you can open its UI and view the values (or curl it with prometheus rest api).



                Example of metric name:
                envoy_cluster_inbound_8080__my_service_my_namespace_svc_cluster_local_membership_healthy



                Where 8080 is the port of your service, my_service is its name, my_namespace its namespace. There's also a similiar one for outbound: envoy_cluster_outbound_(etc.)



                In Istio 1.1 these metrics are reorganized into a format more suitable for Prometheus, so the names change a little bit and service name / namespace become label instead of being part of the name.



                Note that Kiali ( https://www.kiali.io/ ) shows this health information.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 13 '18 at 10:18









                JoelJoel

                1,4201119




                1,4201119



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53274571%2fcli-to-monitor-connection-pool-in-openshift%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Top Tejano songwriter Luis Silva dead of heart attack at 64

                    政党

                    天津地下鉄3号線