<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:18:08 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-2089] SPIKE: determine FOLIO log aggregation approach on AWS EKS</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-2089</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Getting access to hosted FOLIO container logs on a single-server deployment where Okapi is managing the deployment hasn&apos;t really necessitated the need for a proper log aggregation strategy since Okapi provided much of this functionality.    However, distributed container deployments across K8 pods and hosts by non-Okapi mechanisms combined with clustered instances of Okapi need a proper log aggregation strategy in order to provide easier access to log files and to correlate log events.    There a few different options.    The following link provides a fluentd-based approach to log file aggregation on AWS.   &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://aws.amazon.com/blogs/compute/building-a-scalable-log-solution-aggregator-with-aws-fargate-fluentd-and-amazon-kinesis-data-firehose/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://aws.amazon.com/blogs/compute/building-a-scalable-log-solution-aggregator-with-aws-fargate-fluentd-and-amazon-kinesis-data-firehose/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Additionally, we should determine where to output and access logs.  Possibilities include S3 buckets or an Elasticsearch datastore. &lt;/p&gt;</description>
                <environment></environment>
        <key id="81361">FOLIO-2089</key>
            <summary>SPIKE: determine FOLIO log aggregation approach on AWS EKS</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="5f9abc1eb45b2e007453f423">John Malconian</assignee>
                                                                <reporter accountid="5f9abc1eb45b2e007453f423">John Malconian</reporter>
                                    <labels>
                            <label>platform-backlog</label>
                    </labels>
                <created>Mon, 10 Jun 2019 12:27:02 +0000</created>
                <updated>Wed, 3 Jun 2020 16:39:54 +0000</updated>
                            <resolved>Fri, 26 Jul 2019 14:55:11 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                                                            <comment id="195853" author="5f9abc1eb45b2e007453f423" created="Mon, 10 Jun 2019 12:29:04 +0000"  >&lt;p&gt;In addition to FOLIO container logs, there are also Rancher logs and EKS control plane logs that may need to be considered as well. &lt;/p&gt;</comment>
                                                            <comment id="195855" author="5f9abc1eb45b2e007453f423" created="Thu, 25 Jul 2019 18:23:13 +0000"  >&lt;p&gt;The easiest path forward is to implement a EFK logging stack (Elasticsearch to store and index the container logs, Fluentd to ship and aggregate container logs to Elasticsearch, and a Kibana dashboard to interface with logs).   As it so happens there is a EFK stack helmchart that will install all components of the stack within the K8 cluster making installation fairly easy.   There are a few customizations that need to made to deal with Ingress.     Access the dashboard is open to the world, by default.   I think we&apos;d like to make those logs available to all members of Github folio-org.   In order to do that we need to configure OAUTH integration with the NGINX ingress controller on the cluster and github.com/folio-org.    The last step would be setting up some default dashboards in the Kibana UI.  &lt;/p&gt;</comment>
                                                            <comment id="195858" author="5f9abc1eb45b2e007453f423" created="Fri, 26 Jul 2019 14:55:11 +0000"  >&lt;p&gt;Create 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-2195&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-2195&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Implement EFK logging stack on folio-eks-oregon-1 K8 cluster&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-2195
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 to implement EFK logging stack.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="10721">UXPROD-1827</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="81266">FOLIO-2054</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="81259">FOLIO-2195</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10144"><![CDATA[Core: Platform]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzx6pr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="994">CP: ready for planning</customfieldvalue>
    <customfieldvalue id="1158">CP: sprint 68</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10044" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>