|
Start Time,Last Updated,Originator,Unique Users,Unique Users Count,Summary,Message Count,Positive Topics,Negative Topics,Overall Sentiment,,Predicted Status
|
|
2023-08-30T08:43:15.545539,2023-09-11T20:55:44.574959,svummidi,"{'pjha', 'svummidi', 'snangia', 'aganivada', 'rtaraniganty', 'hchintamreddy'}",6,The team discusses event bridge failures and suspects that the issue may be related to an unauthorized response from the backend. They plan to investigate the root cause and fix the failing event bridges in production. They also mention deploying alerts for failing event bridge rules and provide links to the specific rules. Reference: <https://pinstripe.atlassian.net/browse/COLL-2702>,95,"['investigate root cause', 'fix failing event bridges', 'deploy alerts']","['event bridge failures', 'unauthorized response']",,"['COLL-2702', 'COLL-2857']",UNKNOWN
|
|
2023-09-08T01:24:21.533839,2023-09-11T00:26:54.998129,aganivada,"{'aganivada', 'amishra', 'bganganna'}",3,"The discussion thread is about a deployment of fixes related to user removal. There are three JIRA tickets mentioned: PLAT-2540, PLAT-2541, and PLAT-2542. bganganna reports that PLAT-2540 is still happening, and aganivada suggests reviewing the steps in the ticket. bganganna adds a step to invite a new collaborator as a PO for engagement. There is a mention of a backend issue and bganganna plans to test the issues in the stage environment. PLAT-2542 is reported to be working fine in the stage environment. aganivada marks PLAT-2541 and PLAT-2542 as qa-ready.",19,"['deployment of fixes', 'PLAT-2542 working fine']",['PLAT-2540 still happening'],,"['PLAT-2540', 'PLAT-2541', 'PLAT-2542', 'PLAT-2540', 'PLAT-2542', 'PLAT-2540', 'PLAT-2540', 'PLAT-2542', 'PLAT-2542']",ON_GOING
|
|
2023-09-06T02:46:36.265039,2023-09-07T01:56:24.212979,aganivada,"{'aganivada', 'pmangalapuri', 'rvaidya'}",3,"The discussion is about a bug in the admins page where clicking on re-send sends an invitation but does not trigger the delete invitation API. The team is discussing whether this should be done from the UI or if apps can handle it. They also consider using the delete invitation API from tenancy and adding an additional parameter for re-sending. Reference: PLAT-2522, <https://api.integration.axiamatic.cloud/dashboard-app/swagger-ui/webjars/swagger-ui/index.html?configUrl=/dashboard-app/v3/api-docs/swagger-config#/collaborator/deleteInvitation|https://api.integration.axiamatic.cloud/dashboard-app/swagger-ui/webjars/swagger-ui/index.ht[…]l?configUrl=/dashboard-app/v3/api-docs/swagger-config>",4,"['Bug in admins page', 'Re-send invitation', 'UI handling', 'Delete invitation API', 'Tenancy', 'Additional parameter for re-sending']",[],,['PLAT-2522'],ON_GOING
|
|
2023-09-06T08:53:30.021479,2023-09-07T00:23:39.146849,rsrinivasan,"{'mnirmal', 'aganivada', 'rsrinivasan', 'hchintamreddy'}",4,"The discussion thread is about a user receiving multiple notifications for completing a survey and submitting a pulse. The team investigates and confirms that the user was nudged multiple times, and the messages were edited instead of sending new ones. The team also discusses updating the knowledge base with this information. No specific JIRA ticket or other links are mentioned in the conversation.",20,"['Investigation of multiple notifications', 'Confirmation of nudging', 'Updating knowledge base']",[],,[],UNKNOWN
|
|
2023-08-22T21:00:34.256229,2023-09-06T20:26:46.670349,aganivada,"{'bot_message', 'askumar', 'aganivada', 'anair', 'bganganna'}",5,"The discussion thread is about making changes to the system_user masking in invitation emails. The changes were made to the template and deployed to the STAGE. However, there were issues with the system_user name still appearing in the email and on the sign-up page. It was suggested to remove the inviter's email entirely from the text in Auth0. An alternative suggestion was to rename the system_user in the database to ""your org"" to handle the issue.",24,"['changes to system_user masking', 'template deployment']","['system_user name appearing', 'issues with email', 'issues with sign-up page', ""removing inviter's email"", 'renaming system_user']",,['TEST-1095'],UNKNOWN
|
|
2023-08-17T02:18:55.187779,2023-09-04T23:33:19.343119,aganivada,"{'bot_message', 'pmangalapuri', 'rvaidya', 'amishra', 'aganivada', 'bganganna'}",6,"The discussion thread is about the deployment of backend changes for the updated invitation flow in the int environment. The changes aim to improve the in-flight invitation flow by sending only one invitation instead of multiple invitations when a user is added to an engagement. The flow also ensures that removing a user from engagement does not delete the invitation. After onboarding, an API call needs to be manually invoked. There is a request to automate page reload after closing membership to display all permissions. A UI ticket has been created for this. The API order at login time is also discussed, with a suggestion to change it to org > token > login > token > info instead of org > token > info > login. A JIRA ticket (UI-2605) has been created for this change.",20,"['improved invitation flow', 'automated page reload', 'API order change']","['multiple invitations', 'deleting invitations', 'manual API call', 'current API order']",NEUTRAL,"['UI-2605', 'UI-2605']",ON_GOING
|
|
2023-06-15T21:40:20.610789,2023-09-04T22:51:43.690779,svummidi,"{'aganivada', 'svummidi', 'bot_message', 'rsrinivasan'}",4,The discussion thread is about integrating Imply Polaris metrics with Lightstep. They consider using Amazon Open Telemetry Distro to publish metrics to Lightstep and discuss the possibility of adding it to the existing stack. They also discuss the metrics they are currently collecting and the need to filter and create separate dashboards for each environment. They mention creating alerts for certain metrics and discuss the scrape interval and the use of the same cluster for all three environments. A JIRA ticket (PLAT-2518) is created for this task.,29,"['Integrating Imply Polaris metrics with Lightstep', 'Using Amazon Open Telemetry Distro to publish metrics to Lightstep', 'Creating separate dashboards for each environment', 'Creating alerts for certain metrics', 'Creating a JIRA ticket (PLAT-2518)']",['None'],POSITIVE,"['PLAT-2478', 'PLAT-2518']",UNKNOWN
|
|
2023-09-03T21:58:32.798009,2023-09-04T15:56:53.482329,aganivada,"{'aganivada', 'snangia', 'bganganna', 'mli'}",4,The discussion thread is about an error message that occurs when trying to configure pulse for a platform tenant. It is discovered that the configuration was still active due to a cancelled instance. The solution is to disable the configuration in the database. There is a tracker ticket to modify the user experience for cancelled instances. The team also discusses options for handling cancelled pulses and creating new pulses with the same configuration. The JIRA tickets mentioned are DISC-3573 and COLL-2590.,13,"['Solution to disable configuration in the database', 'Tracker ticket to modify user experience for cancelled instances', 'Options for handling cancelled pulses', 'Creating new pulses with the same configuration']",['Error message when configuring pulse for a platform tenant'],POSITIVE,"['DISC-3573', 'COLL-2590', 'DISC-3573']",UNKNOWN
|
|
2023-09-04T00:28:50.681339,2023-09-04T02:16:54.147239,aganivada,"{'aganivada', 'U05PCBD9SHE', 'psomasamudram563', 'pjha'}",4,"There is a licensing issue with Perimeter 81, preventing access for Vishal. A support ticket has been raised and the severity of the issue has been communicated. In the meantime, Dejan's account can be removed, and access to int and stage is still available. Anandhi does not have an account.",15,"['support ticket raised', 'severity communicated', 'access to int and stage available']","['licensing issue with Perimeter 81', 'Vishal unable to access', ""Dejan's account to be removed"", 'Anandhi does not have an account']",,[],UNKNOWN
|
|
2023-08-31T20:48:11.898339,2023-09-01T21:45:53.381329,aganivada,"{'aganivada', 'anair'}",2,"The discussion is about handling the flow where an SSO admin assigns an app to a user without an invitation. The team wants to check when they can target this change, considering other new asks that have come up recently. The flow being discussed is the pacden flow, where an admin added a user directly in IDP and the user was seeing a blank page on login because the org/role was not assigned to them. No specific details about a JIRA ticket or other links are mentioned.",3,"['Handling flow for SSO admin assigning app to user without invitation', 'Targeting change for SSO admin assigning app to user without invitation', 'Pacden flow discussion', 'Directly adding user in IDP', 'Identifying and resolving blank page issue on login']",[],,[],ON_GOING
|
|
2023-08-31T03:19:55.981009,2023-08-31T21:02:07.781989,aganivada,"{'aganivada', 'rtaraniganty', 'pmangalapuri', 'amishra'}",4,"The discussion thread is about making UI stack deployment changes. The points discussed include adding a new S3 bucket and linking it to CloudFront, making changes to CDK CloudFront, finalizing the CICD model, hydrating env.js during deployment, updating UI CDK deployment code, adding a command to invalidate CloudFront cache, adding CloudWatch alarms for error responses, evaluating checksum validation, and evaluating the process to cleanup stale files in S3. The main driver for these changes is to speed up the UI and serve directly from CloudFront. The tasks are reviewed under the JIRA ticket PLAT-2488 and targeted for sprint ""PLAT Sprint 110 - 0.9.16.""",11,"['adding a new S3 bucket', 'linking S3 bucket to CloudFront', 'making changes to CDK CloudFront', 'finalizing CICD model', 'hydrating env.js during deployment', 'updating UI CDK deployment code', 'adding command to invalidate CloudFront cache', 'adding CloudWatch alarms for error responses', 'evaluating checksum validation', 'evaluating process to cleanup stale files in S3', 'speeding up UI', 'serving directly from CloudFront']",[],,"['PLAT-2488', 'PLAT-2488']",UNKNOWN
|
|
2023-08-30T23:41:44.836679,2023-08-31T10:03:51.709219,akasim,"{'rtaraniganty', 'akasim', 'pjha'}",3,The Gitlab pipeline for the collaboration services sentiment collector is stuck in a pending state. Akasim requested assistance as they need to rollout the HF today. Pjha is investigating the root cause and will document the fix under HowTO.,7,[],['Gitlab pipeline stuck in pending state'],NEGATIVE,[],ON_GOING
|
|
2023-08-30T00:41:56.844789,2023-08-30T08:25:30.596299,psomasamudram563,"{'psomasamudram563', 'aganivada'}",2,The user psomasamudram563 asks if they can shut down some things in the AWS Core Account as they are running a $300 billing. Aganivada agrees and informs the team that all the zones added to the devx account have been deleted and the bastion host has been shut down.,5,"['shut down things in AWS Core Account', 'deleted zones in devx account', 'shut down bastion host']",['$300 billing'],,[],UNKNOWN
|
|
2023-08-30T06:54:29.267489,2023-08-30T07:26:44.037519,aganivada,"{'aganivada', 'pjha'}",2,aganivada asked pjha if they could sync up on an AWS network diagram using the cloudmapper tool. pjha asked for a good time to connect. aganivada suggested connecting now and mentioned starting a collect job from cloudmapper to generate a report once the data is available.,4,"['sync up on AWS network diagram', 'using cloudmapper tool', 'connecting now', 'starting a collect job', 'generating a report']",[],,[],UNKNOWN
|
|
2023-08-29T05:41:55.384959,2023-08-29T06:13:59.037619,aganivada,"{'aganivada', 'askumar'}",2,Aganivada asks Askumar if they can close the tenancy HF branch. Askumar agrees. Aganivada then asks Askumar to review a merge conflict in the branch and ensure all changes are present. Askumar confirms that their changes are included in the merge commit. No specific details or references are mentioned.,4,"['Closing tenancy HF branch', 'Agreement to close branch', 'Confirmation of changes in merge commit']",['Merge conflict in branch'],,[],UNKNOWN
|
|
2023-08-28T20:39:52.926099,2023-08-28T22:06:01.495969,aganivada,"{'aganivada', 'pjha'}",2,aganivada asks pjha if they can move the ask-ai job to the GitLab runner because there is only 30% or less space available in the shared runner. Rama had raised this issue in a previous thread. pjha agrees to move the job to the custom GitLab runner and also mentions that they will check other costly pipelines that can be moved as well.,2,"['move ask-ai job to GitLab runner', 'check other costly pipelines']",['30% or less space available in shared runner'],,[],UNKNOWN
|
|
2023-08-27T21:51:04.002789,2023-08-27T21:51:36.927019,aganivada,"{'aganivada', 'askumar'}",2,aganivada asks askumar not to close the tenancy HF yet as they have a couple of fixes to make. They suggest deploying tenancy 20.1 to the stage for testing. askumar agrees to do so. No specific details or references are mentioned in the conversation.,2,['Deploying tenancy 20.1 to stage for testing'],['Closing the tenancy HF'],,[],UNKNOWN
|
|
2023-08-24T09:33:38.879419,2023-08-27T20:39:46.044769,aganivada,"{'aganivada', 'araman'}",2,"aganivada added a JIRA ticket (PLAT-2479) for version 0.9.14 HF, requesting to rename the vendor admin role in the dashboard. They will update the core-data-commons and dashboard-app pom files. araman asked to be assigned the ticket when it's QA-Ready. aganivada confirmed and mentioned that the change has been deployed to the stage.",4,"['JIRA ticket added', 'Version 0.9.14 HF', 'Vendor admin role rename', 'Change deployed to stage']",[],,['PLAT-2479'],UNKNOWN
|
|
2023-08-24T22:54:23.174719,2023-08-24T23:09:11.976179,aganivada,"{'aganivada', 'pjha'}",2,"During the discussion, aganivada points out that the maximum ACU in two instances is 5 and 3, suggesting that there should not be any issues. However, pjha mentions that during the first upgrade attempt, the minimum ACU was 0.5 and the maximum ACU was 1, resulting in only 1 GiB of available memory. pjha suggests increasing the minimum ACU for safety. No references to JIRA or other links are mentioned.",3,"['maximum ACU is 5', 'maximum ACU is 3', 'no issues']","['minimum ACU was 0.5', 'maximum ACU was 1', 'only 1 GiB of available memory', 'increase minimum ACU for safety']",,[],UNKNOWN
|
|
2023-08-23T09:01:19.254729,2023-08-24T22:02:38.849999,pjha,"{'rtaraniganty', 'pjha'}",2,"The discussion thread is about reviewing a weekly report analysis using CUR for stage c.c aganivada. rtaraniganty asks for the raw data, and pjha provides the AWS CLI command to retrieve the data from S3. pjha mentions that they are querying Athena instead of directly querying the file. rtaraniganty requests pjha to create a Confluence page with flow details and sample queries.",8,"['Reviewing weekly report analysis', 'Using CUR for stage c.c aganivada', 'Providing AWS CLI command to retrieve data from S3', 'Querying Athena instead of directly querying the file', 'Creating Confluence page with flow details and sample queries']",[],,[],UNKNOWN
|
|
2023-08-24T08:30:34.145749,2023-08-24T10:10:43.175859,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,The discussion thread is about enabling SAML for 'Unbound' users in Auth0. They fixed one user who had both username-pwd and SAML enabled and shared a list of users to re-invite. The issue occurred because they missed turning on the flag for SSO. They also discussed updating the instructions for enabling SSO and removing a flag. The reason for marking a flag as not required was due to targeting being turned on after creating the ticket.,14,"['Fixed user with both username-pwd and SAML enabled', 'Shared list of users to re-invite', 'Turned on flag for SSO', 'Discussed updating instructions for enabling SSO', 'Removing a flag', 'Targeting turned on after creating the ticket']",[],,['PLAT-1760'],ON_GOING
|
|
2023-08-23T20:48:53.959189,2023-08-24T09:52:55.640899,rtaraniganty,"{'araman', 'rtaraniganty'}",2,"The discussion thread mentions the process of generating a shout-out message using ChatGPT and editing it to reduce repetition. It also mentions that ChatGPT did not acknowledge QA or systest, while Ask-AI highlighted the systest team in the retro summary. No specific JIRA ticket or other links are mentioned.",4,"['generating shout-out message', 'editing to reduce repetition']",['ChatGPT not acknowledging QA or systest'],NEUTRAL,[],UNKNOWN
|
|
2023-08-24T05:02:43.301209,2023-08-24T05:17:13.442019,aganivada,"{'aganivada', 'pjha'}",2,The discussion thread involves aganivada and pjha discussing the issue of the CPU crossing 100% in the GL-runner instance. They consider reducing the number of parallel pipelines running from 7 to 5 to address the issue. There is also a mention of an alert for disk space. No references to JIRA tickets or other links are provided.,7,"['CPU issue', 'Reducing parallel pipelines']",['Disk space alert'],,[],UNKNOWN
|
|
2023-08-23T13:45:31.019669,2023-08-24T04:11:55.416469,anair,"{'bot_message', 'rsrinivasan', 'aganivada', 'anair', 'bganganna'}",5,"The discussion thread is about enabling SAML as the default login for the PacDen/17160 platform. They discuss the issue of new users not being invited via SSO and decide to enable the feature for all tenants. They also mention testing the admin invitation flow and enabling SAML for a tenant in the stage. They mention a JIRA ticket (PLAT-1760) that was set to ""NOT REQUIRED"" and can be picked up in version 0.9.15.",23,"['Enabling SAML as default login', 'Enabling SSO for new users', 'Testing admin invitation flow', 'Enabling SAML for a tenant in stage']","['Issue of new users not being invited via SSO', ""JIRA ticket PLAT-1760 set to 'NOT REQUIRED'""]",POSITIVE,"['TEST-1100', 'TEST-1100', 'PLAT-1760']",RESOLVED_OR_CLOSED
|
|
2023-08-23T16:43:45.323139,2023-08-23T20:16:26.103219,rtaraniganty,"{'askumar', 'rtaraniganty', 'rsrinivasan'}",3,"In a code review, rtaraniganty shares their Python code formatting setup using VS Code, Black, and Flake8 extensions. rsrinivasan suggests setting up pre-commit hooks in PyCharm for automatic formatting before committing changes. askumar expresses gratitude to rtaraniganty.",4,[],[],,[],UNKNOWN
|
|
2023-08-23T16:03:19.469639,2023-08-23T20:15:55.580629,rtaraniganty,"{'araman', 'rtaraniganty', 'aganivada'}",3,"The discussion thread involves a problem with the Stage Retro tenant, specifically the axm_retro_survey tenant (17203) becoming a tenant with no products. Satya tried to invite rtaraniganty to the tenant, but rtaraniganty is unable to access it. Aganivada closed the invite for operations to fix the issue. Rtaraniganty later confirms that the issue is still present.",10,[],"['Stage Retro tenant problem', 'axm_retro_survey tenant becoming a tenant with no products', 'Unable to access tenant', 'Issue still present']",,[],UNKNOWN
|
|
2023-08-21T01:14:23.262809,2023-08-22T14:32:55.569299,mnirmal,"{'mnirmal', 'askumar', 'rtaraniganty'}",3,"The discussion thread is about a build failure in the PMS due to a missing jar file. mnirmal commented out the plugin code to unblock the build. askumar suggested trying to build with the latest release version, but it didn't work. rtaraniganty mentioned that there should be a pluginRepositories section in the pom file and apologized for not notifying everyone about the branch update. mnirmal asked why the update is not in develop yet and shared the code snippet for the pluginRepositories section. rtaraniganty said they will check.",9,"['build failure', 'unblocking the build']","['missing jar file', 'failed build with latest release version', 'missing pluginRepositories section in pom file', 'lack of communication about branch update']",,[],UNKNOWN
|
|
2023-08-10T05:18:33.833899,2023-08-22T03:24:01.112699,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion thread is about testing the upgrade of the collab database instance. They plan to update a timestamp in a record using Retool or a curl request. They have tested the behavior of the upgrade and experienced downtime for around 20 minutes. They also encountered a 500 error during the upgrade. They have raised a support ticket to inquire about memory configuration for a smooth upgrade.,19,"['Testing upgrade of collab database instance', 'Behavior of upgrade tested', 'Support ticket raised for memory configuration']","['Downtime during upgrade', 'Encountered 500 error during upgrade']",NEGATIVE,[],ON_GOING
|
|
2023-08-18T17:37:41.473719,2023-08-21T06:01:32.181729,svummidi,"{'aganivada', 'svummidi', 'gdahiya', 'rtaraniganty'}",4,"The discussion thread is about the recommended practice for deploying hot-fixes in production. It is suggested to test the hot-fix build in int and stage before deploying and merging. Deploying from the main branch is considered the safest option, although it may require an additional round of validation. The team currently deploys from the hot-fix branch during testing and merges to main and develop before deploying to production. They ensure that only one hot-fix branch is active at a time to avoid losing changes. The team manually updates the pom file versions in sub-branches when necessary.",8,"['recommended practice', 'testing hot-fix build', 'deploying from main branch', 'avoiding losing changes', 'manually updating pom file versions']","['additional round of validation', 'deploying from hot-fix branch', 'merging to main and develop', 'deploying to production']",NEUTRAL,[],UNKNOWN
|
|
2023-08-17T03:29:39.127169,2023-08-21T04:07:05.185019,aganivada,"{'aganivada', 'askumar', 'sjain'}",3,The discussion thread is about access to Snowflake. Aganivada asks if Snowflake supports read-only access and if they can restrict access to production data. Askumar confirms that Snowflake supports read-only access but cannot restrict access to production data due to the same tables being used for both INT and PROD data. Askumar adds a user named Sanket with view-only access and provides a replica of the dashboard for testing new queries. Sjain confirms that they were able to add new tiles to the dashboard and asks to revert Sanket's access. Askumar revokes Sanket's access. No JIRA ticket or other links are mentioned.,12,"['Snowflake supports read-only access', 'Askumar adds user Sanket with view-only access', 'Askumar provides replica of dashboard for testing new queries', 'Sjain confirms ability to add new tiles to dashboard']","['Cannot restrict access to production data', ""Askumar revokes Sanket's access""]",,[],UNKNOWN
|
|
2023-08-19T04:58:01.934289,2023-08-20T21:23:51.594089,aganivada,"{'aganivada', 'rtaraniganty'}",2,"Aganivada asks if they can close the CDK release branch on Monday, suggesting it could be used for changes if needed. Rtaraniganty agrees to keep it open until Monday. Aganivada confirms and asks PJha to close the branch today. No JIRA ticket or other links are mentioned.",3,"['closing CDK release branch', 'keeping branch open until Monday']",['no JIRA ticket or other links mentioned'],POSITIVE,[],RESOLVED_OR_CLOSED
|
|
2023-08-18T05:14:01.807399,2023-08-18T09:00:33.134509,aganivada,"{'aganivada', 'mnirmal'}",2,The discussion thread is about marking a branch as protected and encountering an error while trying to finish a hotfix. Mnirmal asks if a branch is protected and requests it to be marked as protected. Aganivada confirms and marks it as protected. Mnirmal then encounters an error while trying to finish a hotfix and Aganivada checks and updates the restrictions on the main branch.,10,"['branch protection', 'marking branch as protected', 'updating restrictions on main branch']",['encountering error while finishing hotfix'],,[],UNKNOWN
|
|
2023-08-17T09:16:13.889709,2023-08-17T09:19:54.303319,aganivada,"{'aganivada', 'bkathi', 'rsrinivasan'}",3,"The discussion thread is about a demo and work done by bkathi. Aganivada and rsrinivasan appreciate the work. Bkathi apologizes for missing the initial slot for the platform, but Aganivada says it's not a problem as they didn't find bkathi's name in the teams invitee's list.",5,"['demo', 'work done', 'appreciate']","['missing initial slot', 'apologize', ""not in invitee's list""]",,[],UNKNOWN
|
|
2023-08-15T22:28:54.970809,2023-08-15T23:07:31.566859,aganivada,"{'aganivada', 'ppant'}",2,"The discussion is about adding a default with error response in a method. ppant mentions that the default invitation type specified in the API specs is always INVITE, so the default block won't be executed. However, they suggest adding it for safety. They confirm that the default will always be INVITE at the API level. No references or links are mentioned.",4,"['default with error response', 'API specs', 'safety']",['no references or links mentioned'],,[],UNKNOWN
|
|
2023-07-28T07:39:52.578209,2023-08-15T22:12:54.633499,aganivada,"{'aganivada', 'askumar', 'rtaraniganty'}",3,"The discussion thread revolves around an issue with the job-manager service, which restarted due to high CPU usage and picked up the latest code. The team updated the main branch and deployed the changes to stabilize the service. There is also a concern about the job-manager being attacked occasionally in production. The team plans to enable API Gateway and VPN protection to secure the service. The jobs running on the job-manager include auth0 backups, data cleanup, and Microsoft account refreshing. The auth0 backups are running successfully, but the data cleanup job is failing due to a missing 'imply_password'. The access issue with the job-manager has been fixed in all three environments.",15,"['Job-manager service restart', 'Main branch update', 'Service stabilization', 'Enabling API Gateway', 'Enabling VPN protection', 'Auth0 backups', 'Access issue fix']","['High CPU usage', 'Job-manager attacks', 'Data cleanup job failure']",NEUTRAL,[],ON_GOING
|
|
2023-08-11T10:54:08.652279,2023-08-14T06:11:12.036479,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"rtaraniganty suggests running ""askai build"" on the EC2 runner. aganivada mentions attempting to move askai to the GL-runner but then reverts back. They ask pjha to look into the issue of the job not getting picked up by the GL-runner, despite the webhook working.",3,"['askai build', 'EC2 runner', 'webhook working']","['GL-runner', 'job not getting picked up']",,[],UNKNOWN
|
|
2023-08-03T10:42:30.001809,2023-08-11T14:05:48.070349,nsrivastava,"{'rtaraniganty', 'rsrinivasan', 'nsrivastava'}",3,"The discussion thread is about a user trying to publish an npm package onto GitLab registry but facing issues with overwriting the same version. They tried unpublishing but received an error stating that the last version cannot be deleted for 24 hours. The user is looking for a way to overwrite or bypass the 24-hour timeline. A team member suggests deleting the package explicitly using a Python script. Another team member opens a case with GitLab for support. GitLab responds by mentioning that they are working on implementing a feature to enable/disable duplicate package uploads, but it is not yet available for npm packages. A link to the feature request is provided for upvoting and following updates. The team finds it strange that the feature is available for other package types but not for npm.",10,"['publishing npm package', 'overwriting package version']","['issues with GitLab registry', 'unable to delete last version', 'bypassing 24-hour timeline']",NEGATIVE,[],UNKNOWN
|
|
2023-08-10T22:37:16.853499,2023-08-11T00:31:20.427719,akasim,"{'aganivada', 'akasim'}",2,Akasim reported an error in the MB develop branch build on GitLab. Aganivada investigated and suggested a change to resolve the issue. Akasim mentioned that the build was successful locally. Aganivada confirmed that the build is now working and mentioned a previous response regarding a possible race condition.,9,"['successful build', 'resolved issue']","['error in build', 'race condition']",,[],UNKNOWN
|
|
2023-08-10T03:38:39.190519,2023-08-10T08:58:20.753929,askumar,"{'askumar', 'aganivada'}",2,The discussion thread is about configuring ILM policies. The team is discussing how to test the policies on a single instance in the INT environment and considering enabling cluster mode. They also discuss the possibility of changing the index names to include a timestamp for easier policy application. The cost of enabling cluster mode and the minimum number of nodes required are also mentioned. The team plans to copy data to a test cluster in INT for testing and then switch back to non-cluster mode. Reference: <https://pinstripe.atlassian.net/wiki/spaces/PRODUCT/pages/647364697/ES+Index+Lifecycle+Management+ILM+Policies#Moving-Data-from-cold-to-ultra-warm-on-demand-for-viewing-historical-data|https://pinstripe.atlassian.net/wiki/spaces/PRODUCT/pages/647364697/ES+Index+Lifecycle+Management+ILM+Policies#Moving-Data-from-[…]g-historical-data>,8,"['configuring ILM policies', 'testing policies on a single instance', 'enabling cluster mode', 'changing index names', 'copying data to a test cluster']","['cost of enabling cluster mode', 'minimum number of nodes required']",NEUTRAL,[],UNKNOWN
|
|
2023-08-09T22:58:54.784389,2023-08-10T03:49:17.318839,aganivada,"{'aganivada', 'akasim', 'hchintamreddy'}",3,Akasim deployed a change in MB with whitelisting. Subscription renewal started again in MB. Brokering works now. Hchintamreddy suggests updating the release thread with these findings. Aganivada agrees. Aganivada shares a filter for Event bridge invocation failures.,8,"['MB change deployment', 'Subscription renewal', 'Brokering works']",['Event bridge invocation failures'],,[],UNKNOWN
|
|
2023-08-08T20:32:20.939979,2023-08-08T20:50:22.372469,aganivada,"{'aganivada', 'pjha'}",2,"The discussion thread is about investigating why a job terminated in the runner. Pjha agrees to check the issue. Later, it is mentioned that the job was re-run successfully, but there is an issue with the generation of the Auth0 token, specifically a TypeError related to 'chrome_options'. No JIRA ticket or other links are mentioned.",4,"['job terminated investigation', 'job re-run successfully']","['issue with Auth0 token generation', ""TypeError related to 'chrome_options'""]",,[],UNKNOWN
|
|
2023-08-08T08:42:08.712319,2023-08-08T08:43:50.217539,rtaraniganty,{'rtaraniganty'},1,"The discussion thread is about the addition of ""scale-gl-runner.sh"" to release-tools. There was a missing end-quote in line 30, which was fixed in a subsequent commit. They also discussed adding a way to poll for the instance state and automatically start it if it is ""stopped"" after a minute. No specific JIRA ticket or other links were mentioned.",2,"['scale-gl-runner.sh added to release-tools', 'Missing end-quote fixed', 'Automatic instance start on stopped state']",[],,[],UNKNOWN
|
|
2023-08-08T08:04:30.318739,2023-08-08T08:36:01.255479,gdahiya,"{'askumar', 'rtaraniganty', 'gdahiya', 'aganivada'}",4,"During the discussion, gdahiya reported that the Tenancy was down in the INT environment. It was discovered that the service was redeployed due to port 8080 being unhealthy. The issue was caused by Auth0 taking too long to respond, but it eventually recovered. A support ticket was opened with Auth0 to investigate the problem further.",13,[],"['Tenancy down', 'Port 8080 unhealthy', 'Auth0 slow to respond']",NEGATIVE,[],UNKNOWN
|
|
2023-08-07T21:06:29.197369,2023-08-07T21:16:00.766129,aganivada,"{'aganivada', 'askumar'}",2,"The discussion thread is about a thread that was moved to a different location. There is confusion about whether the thread was updated later or if it was manually updated. The commit was merged on July 7th, but the develop branch shows a different date of June 20th. It is suggested that the thread may have been updated directly at a later time. No specific JIRA ticket or other links are mentioned.",5,"['thread moved to different location', 'thread updated later']","['confusion about thread update', 'no specific JIRA ticket or links mentioned']",NEUTRAL,[],UNKNOWN
|
|
2023-08-07T18:58:24.371619,2023-08-07T20:26:02.234169,aganivada,"{'aganivada', 'askumar'}",2,The discussion thread is about a specific issue related to a new database instance during migration. Askumar confirms that the issue occurred after all the migrations were completed in the stage environment. No specific details or references to JIRA tickets or other links are mentioned.,2,[],"['issue', 'migration', 'database instance']",,[],ON_GOING
|
|
2023-08-03T09:27:14.249959,2023-08-04T09:43:40.056369,rsrinivasan,"{'rtaraniganty', 'rsrinivasan'}",2,The discussion thread is about the use of Celery for horizontal scaling in the system setup. The team plans to auto-scale based on the length of pending messages in the SQS queue. They have configured the scaling steps and are testing the scaling functionality. The details of the configuration and testing are documented in the provided Confluence link.,9,"['Celery', 'horizontal scaling', 'auto-scaling', 'SQS queue']",[],,[],UNKNOWN
|
|
2023-07-28T17:18:50.189259,2023-08-04T00:17:53.299259,svummidi,"{'pjha', 'svummidi', 'rsrinivasan', 'aganivada', 'rtaraniganty'}",5,The team is experiencing an error when trying to access Secrets Manager from an EC2 instance. It is believed that the error is due to VPN access and user-based identity. They are considering switching to role-based access and moving the code to their integration VPC. A new EC2 instance is being provisioned for backup purposes.,26,"['Switching to role-based access', 'Moving code to integration VPC', 'Provisioning new EC2 instance for backup']","['Error accessing Secrets Manager from EC2 instance', 'VPN access and user-based identity']",NEGATIVE,[],UNKNOWN
|
|
2023-08-01T09:03:47.239689,2023-08-03T23:44:42.327989,pjha,"{'askumar', 'rtaraniganty', 'pjha'}",3,"The team is discussing the need for a time-based cleanup for temporary bastion access. Currently, there is no automatic cleanup, and keys have to be manually removed from the S3 bucket. The possibility of implementing a lambda function for cleanup is mentioned, and pjha agrees to work on it.",6,"['time-based cleanup', 'implementing lambda function']","['no automatic cleanup', 'manual removal of keys']",,[],UNKNOWN
|
|
2023-07-25T21:23:35.964489,2023-08-03T11:31:34.504389,askumar,"{'askumar', 'ppant', 'aganivada'}",3,"The discussion thread is about reviewing and making changes to a proposal document for Auth0 User permission replication in Core. ppant added some questions, aganivada was occupied with cxo dashboard work but will review it the next morning. aganivada suggested using a design template and filling in sections, as well as using puml and component diagrams for better representation. askumar agreed to make the changes and thanked aganivada. askumar mentioned addressing the comments and getting in touch for further review and changes. No specific JIRA ticket or other links were mentioned.",9,"['reviewing proposal document', 'making changes', 'using design template', 'using puml and component diagrams', 'addressing comments', 'further review and changes']",['no specific JIRA ticket or links mentioned'],,[],UNKNOWN
|
|
2023-07-31T00:55:35.941269,2023-08-01T21:47:24.682729,askumar,"{'askumar', 'rtaraniganty', 'gshenoy'}",3,The discussion thread is about setting up ILM policies and analyzing pricing for a proposed solution. They discuss the need to analyze product discovery events in Elasticsearch (ES) and consider stopping the flow and dropping the index if not needed. They also mention deprecating AWS batch processing and moving it to the event framework. They discuss projected costs and suggest starting with configuration #2.,11,"['Setting up ILM policies', 'Analyzing pricing for a proposed solution', 'Analyzing product discovery events in Elasticsearch (ES)', 'Considering stopping the flow and dropping the index if not needed', 'Moving AWS batch processing to the event framework', 'Projected costs', 'Starting with configuration #2']",[],,[],UNKNOWN
|
|
2023-07-31T22:46:02.739819,2023-08-01T00:21:28.700779,pjha,"{'aganivada', 'askumar', 'pjha'}",3,The discussion thread is about the RDS Proxy reader endpoint connecting to the underlying reader replica of the RDS cluster. They discuss the distribution of requests and the possibility of forcing the reader instance from property/env-var if the proxy is enabled. They also mention routing other services to the proxy and identify the most active service in int. They plan to add the proxy to services and discuss enabling it by service and env. They decide to submit an MR for the changes and turn off the proxy for now.,20,"['RDS Proxy reader endpoint', 'distribution of requests', 'routing other services to the proxy', 'enabling RDS Proxy by service and env']","['forcing reader instance from property/env-var', 'turning off the proxy']",NEUTRAL,[],UNKNOWN
|
|
2023-07-31T21:35:15.078989,2023-07-31T23:35:42.081119,svummidi,"{'svummidi', 'rsrinivasan'}",2,"The discussion thread is about an issue with the askAI celery service not picking up the latest builds and executing old code. The team suspects that another cluster may be connected to the same task queue. They discuss the issue, share curl commands for testing, and plan to trigger a build and deploy to resolve the issue. No specific JIRA ticket or other links are mentioned.",25,"['askAI celery service', 'trigger build and deploy']","['issue with askAI celery service', 'old code', 'another cluster connected to task queue']",,[],UNKNOWN
|
|
2023-07-28T14:53:33.247069,2023-07-30T21:58:06.023039,rtaraniganty,"{'askumar', 'rtaraniganty', 'akasim', 'aganivada'}",4,"Akasim inadvertently reverted changes made by multiple people in the cdk-artifacts repository. Svummidi found that the askai changes were gone, but rtaraniganty undid the undo. There was a conflict in the core/cdk.json file. They need to check if everything is back as it should be. They also need to see if the merges made between July 26 and now are available or if they need to replay them. The challenge seems to be with branches created after July 26 and merged back. Aganivada and Askumar confirmed that their changes are in place.",5,"['changes reverted', 'undo undone', 'conflict resolved', 'changes restored', 'merges available', 'changes confirmed']","['changes missing', 'conflict unresolved', 'merges missing']",,[],UNKNOWN
|
|
2023-07-28T10:20:03.511329,2023-07-30T20:22:05.363959,rtaraniganty,"{'aganivada', 'rtaraniganty', 'askumar', 'rvaidya'}",4,The discussion thread is about the usage of the epoch service and whether tagging should be taken down. It is mentioned that the only invocation of the epoch service is from the tenant deletion workflow in logs. It is also stated that the plan for the 0.9.14 deployment is to retire the tagging app.,4,['usage of epoch service'],['tagging'],,[],UNKNOWN
|
|
2023-07-27T22:53:28.265049,2023-07-27T22:53:38.883449,aganivada,{'aganivada'},1,The discussion thread is about updating the default logout time for users on P81 from 30 days to 60 days. The link provided is for editing the configuration. No JIRA ticket or other links are mentioned.,2,['updating default logout time to 60 days'],[],,[],UNKNOWN
|
|
2023-07-27T21:27:01.919599,2023-07-27T21:27:41.412029,aganivada,"{'aganivada', 'askumar'}",2,"The discussion thread is about an issue with Auth0 where it is case sensitive while sending invitations, but converts the email to lowercase once the invitation is accepted. To maintain consistency, it is suggested to lowercase emails before sending them to Auth0. The JIRA ticket related to this issue is PLAT-2370.",2,"['case sensitivity issue', 'lowercasing emails']","['Auth0', 'inconsistent email handling']",NEUTRAL,['PLAT-2370'],RESOLVED_OR_CLOSED
|
|
2023-07-26T08:58:50.221609,2023-07-27T12:19:30.688529,aganivada,"{'aganivada', 'rtaraniganty'}",2,aganivada asks pjha to check the gitlab runner instance as builds are taking longer than usual. rtaraniganty asks if the issue has been resolved and cc's pjha. rtaraniganty asks pjha to close the loop on the resolution.,4,"['gitlab runner instance', 'builds']","['longer than usual', 'issue not resolved']",,[],ON_GOING
|
|
2023-07-27T02:47:42.108649,2023-07-27T05:24:34.659349,aganivada,"{'aganivada', 'rvaidya'}",2,"Due to recent rains causing network failures, aganivada informs the team to expect delays in response, hoping for a resolution by tomorrow. Rvaidya mentions that even Slack experienced an outage. Aganivada expresses surprise at others cheering for the break from work.",3,['resolution by tomorrow'],"['network failures', 'delays in response', 'Slack outage']",MIXED,[],UNKNOWN
|
|
2023-07-26T02:51:55.404429,2023-07-26T03:04:05.973949,aganivada,"{'aganivada', 'ppant'}",2,ppant is asked if multi-instance by tenant id is enabled in all apps in int. He says it is only enabled in tenancy and core. He mentions that he might have changes stashed for all Axiamatic services and can make the changes in 2 hours. Aganivada suggests holding off until the branch cut is done to avoid regression.,5,"['multi-instance by tenant id', 'enabled in tenancy', 'enabled in core', 'changes stashed for all Axiamatic services', 'changes can be made in 2 hours']","['holding off until branch cut is done', 'avoid regression']",,[],UNKNOWN
|
|
2023-07-24T14:08:09.947669,2023-07-24T23:19:17.958989,anair,"{'askumar', 'anair'}",2,Anair requested to add PacDen/17160 and Cisco/18096 to the snowflake dashboard. Askumar agreed and confirmed that the tenants have been added. No further details or references were provided.,3,"['PacDen/17160 added to snowflake dashboard', 'Cisco/18096 added to snowflake dashboard']",[],,[],UNKNOWN
|
|
2023-07-22T14:02:40.859809,2023-07-24T20:32:50.217879,rtaraniganty,"{'aganivada', 'rtaraniganty', 'rsrinivasan'}",3,The discussion thread is about the increase in RDS spend in the INT account and the need to measure performance insights and cost of key elements week over week. They discuss using the AWS console and configuring CUR to generate reports on the top few items with the biggest deltas in cost. They also mention the need to set up CUR in a private bucket and explore if it can be done for multiple accounts. No specific JIRA ticket or other links are mentioned.,13,"['Increase in RDS spend in INT account', 'Measuring performance insights', 'Cost of key elements week over week', 'Using AWS console', 'Configuring CUR to generate reports', 'Identifying top items with biggest deltas in cost', 'Setting up CUR in a private bucket', 'Exploring CUR for multiple accounts']",[],,[],UNKNOWN
|
|
2023-07-21T16:54:14.559019,2023-07-24T10:46:53.446309,svummidi,"{'svummidi', 'rsrinivasan'}",2,"The discussion thread is about an issue with deserializing a core data response for UserAttributesDTO. The generated code is failing if the value for metadata is a string. One suggestion is to change the metadata type to Optional[Dict[str, Any]]. Another suggestion is to modify the core openapi json to define additionalProperties as true. The purpose of this flag is to allow non-dictionary type objects like strings as values. The issue will be further discussed with gshenoy. No JIRA ticket or other links are mentioned.",5,"['deserializing core data response', 'UserAttributesDTO', 'change metadata type', 'modify core openapi json', 'additionalProperties flag', 'allow non-dictionary type objects', 'discussion with gshenoy']","['generated code failing', 'value for metadata is a string']",NEUTRAL,[],ON_GOING
|
|
2023-07-20T08:41:16.716119,2023-07-20T09:30:13.953459,aganivada,"{'aganivada', 'pjha'}",2,The discussion thread is about enabling VPN for the metrics-manager service. Aganivada suggests checking and updating the VPN for the service. Pjha acknowledges that they missed updating the service after it was merged to develop and has deployed the necessary changes. No specific JIRA ticket or links are mentioned.,2,['enabling VPN for metrics-manager service'],[],,[],UNKNOWN
|
|
2023-07-20T02:54:20.478529,2023-07-20T02:59:52.453389,aganivada,"{'aganivada', 'ppant'}",2,"aganivada asks ppant why only accountAdmin and productAdmin invites have permissions, skipping orgadmin. ppant explains that it was the requirement at that time. aganivada suggests removing the check based on roles and testing it. ppant agrees. No references or links are mentioned.",4,"['Removing check based on roles', 'Testing the new approach']",['Skipping orgadmin'],,[],UNKNOWN
|
|
2023-07-20T00:37:34.208169,2023-07-20T00:48:17.118849,kagarwal,"{'aganivada', 'kagarwal'}",2,Kagarwal requested access to the Gitlab repo at <https://gitlab.com/axiamatic-main> and cc'd the team @plat. Kagarwal also cc'd psomasamudram563. Aganivada mentioned that Kagarwal sent an invitation to join the axiamatic-main repo. Kagarwal acknowledged and thanked for the invitation.,4,"['access request', 'Gitlab repo', 'invitation']",[],,[],UNKNOWN
|
|
2023-07-19T22:41:42.731509,2023-07-19T22:48:02.324829,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"The discussion is about accessing the ECS panel in the AWS console. rtaraniganty asks if anyone can see the panel, and aganivada confirms that they can. rtaraniganty asks for the URL and suggests trying a different URL. aganivada shares a URL that works for them. rtaraniganty mentions having a white page issue on Safari but can see the page on Chrome.",15,"['accessing ECS panel', 'URL works']",['white page issue on Safari'],,[],UNKNOWN
|
|
2023-07-18T00:39:01.234589,2023-07-18T04:15:17.691419,akasim,"{'askumar', 'akasim', 'pjha', 'aganivada'}",4,"The deployment of the score provider in INT failed due to an error related to the existing service. It was suggested to check the latest code and ensure that the lb was merged instead of the ecs ip change. The code was confirmed to be merged, and the user was advised to pull the latest changes and try deploying again. The issue was resolved by updating the CDK changes in the user's workspace.",13,"['deployment of score provider', 'code merge', 'issue resolution']","['error related to existing service', 'failed deployment']",,['COLL-2690'],UNKNOWN
|
|
2023-07-13T16:20:15.384039,2023-07-17T22:23:26.647069,rtaraniganty,"{'aganivada', 'rtaraniganty', 'bganganna', 'mnirmal'}",4,The team discussed the need to clean up junk data in the production database. They found that there were no more junk entries after June 23rd in four tables. They decided not to invoke tenant deletion flow for thousands of entries and instead run scripts to clear them up. They also discussed checking for stale pulses in prod and deleting them. They planned to schedule a call to go over the cleanup process and agreed to be cautious and take a database backup before running the cleanup. No specific JIRA ticket or links were mentioned in the discussion.,30,"['Cleaning up junk data in production database', 'No more junk entries after June 23rd in four tables', 'Running scripts to clear up junk entries', 'Checking for stale pulses in prod', 'Scheduling a call to go over cleanup process', 'Taking database backup before running cleanup']",[],,[],UNKNOWN
|
|
2023-07-17T12:48:41.990129,2023-07-17T22:00:05.281339,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"The discussion is about subscribing to multiple channels. Aganivada added integration to both the engg and on-call channels, and the subscription will be managed by operations@axiamatic.com, with pjha copied on the email. No JIRA ticket or other links are mentioned.",2,"['subscribing to multiple channels', 'integration to engg channel', 'integration to on-call channel']",[],,[],UNKNOWN
|
|
2023-07-14T12:18:35.020609,2023-07-16T23:19:59.588679,rtaraniganty,"{'rtaraniganty', 'rsrinivasan', 'sfarooqh', 'rvaidya'}",4,"The discussion thread revolves around the use of @Async in the notification service for REST to SQS transition. The main purpose of using @Async is to handle bulk email sending, where each recipient has a separate SQS message. However, there is a concern about potential message loss if a node crashes before the messages are posted to SQS. The discussion also touches on the need for cleaning up the email-tracking table and the possibility of adding new states to track the email lifecycle. There is a mention of a JIRA ticket for backlog cleanup and a link to a page tracking completed vs pending features. The maximum number of users for bulk email sending is not known, but the current limit is set to 10 users.",29,"['@Async', 'bulk email sending', 'separate SQS message', 'cleaning up email-tracking table', 'adding new states to track email lifecycle']","['potential message loss', 'node crashes', 'JIRA ticket for backlog cleanup', 'maximum number of users for bulk email sending']",NEUTRAL,['N-1'],ON_GOING
|
|
2023-07-14T01:54:25.208239,2023-07-14T01:58:46.992009,aganivada,"{'aganivada', 'pjha'}",2,aganivada asks if GitLab allows updating the default maximum TTL for a job beyond 1 hour. pjha says they think it is possible and will check. pjha confirms that the timeout can be modified. aganivada thanks pjha.,5,['GitLab allows updating maximum TTL for a job'],[],,[],UNKNOWN
|
|
2023-07-13T23:16:38.223649,2023-07-14T00:48:06.555019,rsrinivasan,"{'hsingh', 'askumar', 'rsrinivasan', 'aganivada', 'rtaraniganty', 'akasim'}",6,"rsrinivasan informs the team about his left hand injury, specifically a cartilage tear, and mentions that he will work from home until he recovers. The team members respond with messages of support and well wishes. The injury was caused by a bike accident.",7,"['support', 'well wishes']","['injury', 'cartilage tear', 'bike accident']",POSITIVE,[],ON_GOING
|
|
2023-06-27T06:03:55.398049,2023-07-13T23:28:29.708619,aganivada,"{'aganivada', 'rtaraniganty', 'rvaidya'}",3,The team discussed two approaches for fetching product admins for the CISO dashboard. Approach 1 involves using the auth0 query API to search for product owners based on user metadata. Approach 2 suggests making core changes to maintain a DB table with web-app access users and their roles. They agreed to start with Approach 1 and later switch to Approach 2. A JIRA epic will be created for Approach 2.,5,"['Approach 1', 'auth0 query API', 'search for product owners', 'user metadata']","['Approach 2', 'core changes', 'DB table', 'web-app access users', 'roles', 'switching']",,[],UNKNOWN
|
|
2023-07-12T23:48:41.402539,2023-07-13T23:19:16.955279,aganivada,"{'aganivada', 'ppant'}",2,aganivada asks the subteam to review the FAQ's on deploying multiple instances of a service. ppant approves and says it looks good.,3,"[""reviewing FAQ's on deploying multiple instances of a service""]",[],,[],UNKNOWN
|
|
2023-07-13T03:34:46.577699,2023-07-13T22:54:45.851459,akasim,"{'pjha', 'askumar', 'aganivada', 'rtaraniganty', 'akasim'}",5,"The discussion thread is about a deployment issue with the scoring_service in INT. The error occurred due to a lack of permissions to call RDS to describe the cluster. The team suggests giving permissions at the group level and adding permissions to the powerusergroup in IAM. Anz was given explicit RDS-Full access permission, and the deployment was successful. The team plans to have a quality check (QC) later.",24,"['deployment issue', 'permissions', 'RDS-Full access permission', 'successful deployment']","['scoring_service', 'error', 'lack of permissions']",POSITIVE,[],UNKNOWN
|
|
2023-07-13T06:56:31.686259,2023-07-13T09:36:27.691229,rsrinivasan,"{'aganivada', 'rtaraniganty', 'rsrinivasan', 'mnirmal'}",4,The team discusses the availability of the pulse manager in the INT environment. They mention that there was a restart but it shouldn't have caused a gap in availability. They also discuss a memory leak issue and plan to monitor and take memory dumps to investigate further. A JIRA ticket is created for tracking the issue.,24,"['pulse manager availability', 'monitoring memory leak']",['gap in availability'],,['COLL-2713'],ON_GOING
|
|
2023-07-13T07:51:28.626099,2023-07-13T08:30:44.749569,aganivada,"{'aganivada', 'askumar'}",2,Askumar and aganivada discuss shutting down the commons RDS in the stage. Askumar confirms that he will remove it and asks if there are any connections to it. Aganivada confirms that there are no more connections. Askumar thanks aganivada and removes the commons RDS instances. No specific details or references are mentioned.,6,['shutting down commons RDS'],[],,[],UNKNOWN
|
|
2023-07-12T22:37:45.101559,2023-07-13T04:32:21.711659,aganivada,"{'aganivada', 'araman', 'bganganna'}",3,"The discussion thread is about a request to update the default invitation expiry from 7 days to 30 days in a system. The change has been made and tested in the int environment. The team plans to deploy the build in the stage environment for validation. Various invitation flows, including customer inviting vendor and vendor inviting customer, are being tested. The build has been deployed to the stage environment, and the customer and vendor collaborator flows have been tested successfully. The change only affects the invitation flow, and there is no change in the onboarding flow. The team does not need to test the invite expiration as it is controlled by auth0. The HF has been deployed in prod, and the invitation's default TTL should now be 30 days instead of 7 days. The JIRA ticket for the request is <https://pinstripe.atlassian.net/browse/PLAT-2304>.",15,"['Update default invitation expiry to 30 days', 'Successful testing in int environment', 'Successful testing in stage environment', 'No change in onboarding flow', 'HF deployed in prod']",['No need to test invite expiration'],POSITIVE,['PLAT-2304'],RESOLVED_OR_CLOSED
|
|
2023-07-12T21:15:28.497939,2023-07-12T22:43:25.587249,pjha,"{'aganivada', 'pjha'}",2,"The discussion is about upgrading the PostgreSQL engine version in RDS Aurora. Strategy 1 is recommended by AWS, which involves performing an upgrade dry run. There will be no downtime until step 9, and it is possible to test three production DB clusters for any inconsistencies. The discussion took place on the JIRA ticket: <https://pinstripe.atlassian.net/wiki/spaces/PRODUCT/pages/642711657/Upgrade+RDS-Aurora-PostgreSQL+production>.",4,"['upgrading PostgreSQL engine version', 'Strategy 1', 'upgrade dry run', 'no downtime', 'test production DB clusters', 'inconsistencies']",['none'],POSITIVE,[],UNKNOWN
|
|
2023-07-11T22:55:51.400469,2023-07-12T00:44:22.144059,aganivada,"{'aganivada', 'askumar'}",2,"The discussion thread is about triggering a scheduled job for testing without updating the schedule. It is mentioned that the backup job failed to trigger due to an error. The conversation also includes a discussion about deploying the job-executor in stage and prod, with the need for CDK changes and verification of Azure account refresh changes. No additional keys are required for deployment.",16,"['triggering a scheduled job for testing', 'deploying the job-executor in stage and prod', 'CDK changes', 'verification of Azure account refresh changes']","['backup job failed to trigger', 'error']",NEUTRAL,[],ON_GOING
|
|
2023-07-11T22:36:58.535949,2023-07-11T23:03:12.757359,rtaraniganty,"{'rtaraniganty', 'pjha'}",2,The discussion thread is about the cost of using ACUs in different environments. The user rtaraniganty calculates that they would spend a minimum of $87.6 per month for 8 ACUs. They suggest trying it in INT first to see if they can reduce the maximum ACU and save money. User pjha confirms that they will be billed for a minimum of 8 ACUs per hour. No references or links are mentioned.,2,"['cost reduction', 'trying in INT']","['high cost', 'minimum billing']",,[],UNKNOWN
|
|
2023-07-11T22:41:56.958359,2023-07-11T22:46:42.775659,aganivada,"{'aganivada', 'pjha'}",2,"The discussion is about whether AWS allows one proxy to serve multiple RDS instances for production. It is mentioned that based on pricing logic, it doesn't seem possible as each proxy can have a single target. No specific JIRA ticket or other links are mentioned.",2,[],"[""AWS doesn't allow one proxy to serve multiple RDS instances for production""]",NEGATIVE,[],ON_GOING
|
|
2023-07-10T08:53:14.218519,2023-07-10T09:31:50.684549,rsrinivasan,"{'aganivada', 'rtaraniganty', 'rsrinivasan'}",3,"The discussion thread is about enabling the ""Newline delimiter"" for Kinesis streams sent to S3 in order to easily load them into Athena for SQL filtering and grouping. Rsrinivasan created a table in Athena but is only seeing the first record in a batch due to the missing delimiter. Aganivada added a backlog in the platform for making this change in CDK. Rsrinivasan asks if they can make the change in production or if Prashant can do it for data-related buckets. Rtaraniganty suggests manually enabling the flag for now and provides a link on how to configure dynamic partitioning for Kinesis in CDK. The discussion also mentions the possibility of applying the delimiter to all buckets instead of just data-related ones. The JIRA ticket for this issue is PLAT-2291.",11,"['Newline delimiter', 'Kinesis streams', 'S3', 'Athena', 'SQL filtering', 'grouping', 'dynamic partitioning', 'CDK']","['missing delimiter', 'backlog', 'JIRA ticket']",,['PLAT-2291'],UNKNOWN
|
|
2023-07-10T07:36:02.440219,2023-07-10T07:53:25.753949,aganivada,"{'aganivada', 'askumar'}",2,"askumar informs aganivada that the account-refresher has not been merged to the develop branch of job-executor yet. There is a pending task to add variables via cdk, which askumar is executing locally to avoid expiry. aganivada suggests closing the task and merging the changes, as they have updates to the project that may complicate merging later on. askumar agrees and thanks aganivada for catching this, stating that the changes have been merged and the pipeline has passed. No references to JIRA or other links are provided.",6,"['account-refresher merged to develop branch', 'task to add variables via cdk executed locally', 'changes merged and pipeline passed']",['updates to the project may complicate merging'],,[],UNKNOWN
|
|
2023-07-10T07:11:22.698019,2023-07-10T07:12:37.330429,sranjan,"{'askumar', 'pjha', 'sranjan'}",3,"Sranjan reports being unable to access AWS and asks for help. Pjha suggests connecting to VPN, and Askumar advises trying with VPN. Sranjan thanks Pjha and Askumar. No JIRA ticket or other links are mentioned.",4,['VPN'],['AWS'],,[],UNKNOWN
|
|
2023-07-06T19:50:50.047579,2023-07-07T03:10:32.615449,rsrinivasan,"{'askumar', 'rsrinivasan', 'aganivada'}",3,"The discussion thread is about an issue with a new service called ""askai"" that is pointing to the old RDS cluster instead of the new Aurora cluster. The issue was resolved by creating two environments and adding a migration tag for one of the services. The services use the same version from the pom file.",11,"['issue resolved', 'two environments created', 'migration tag added']","['issue with askai', 'pointing to old RDS cluster']",,['DAT-1062'],UNKNOWN
|
|
2023-07-06T23:51:52.693079,2023-07-07T00:08:52.182739,pjha,"{'aganivada', 'pjha'}",2,"The discussion thread is about modifying the TTL (time to live) for instances in a deployment. The default TTL is 6 hours, but it can be changed by adding ""multi-instance-ttl-in-hours"" in cdk.json. The cron job currently runs every hour, but it can be modified to check every 15 minutes or less if needed. The person suggests increasing the default TTL to 3 hours, especially when there are multiple services and deployments take 15-20 minutes. There was a mistake in setting the TTL for tenancy to 1 hour.",8,"['modifying TTL for instances', 'changing TTL in cdk.json', 'increasing default TTL to 3 hours', 'checking cron job every 15 minutes', 'setting TTL for tenancy to 1 hour']",[],,[],UNKNOWN
|
|
2023-07-06T14:20:14.314289,2023-07-06T23:42:07.222339,svummidi,"{'aganivada', 'svummidi', 'rsrinivasan'}",3,"The discussion thread is about an issue with logs displaying differently, some with ""message"" and some with ""message_obj.msg"". It is mentioned that this depends on the component logging the statement, with the former being spring default logs and the latter being custom logs. The issue is related to JSON payload in the logs, which is transformed into ""message_obj"" format by Logz.",3,"['JSON payload', 'Logz']","['issue with logs', 'spring default logs', 'custom logs', 'message', 'message_obj.msg']",NEUTRAL,[],UNKNOWN
|
|
2023-07-06T03:15:30.550119,2023-07-06T03:44:44.855809,ppant,{'ppant'},1,ppant faced a 401 unauthorized issue while setting up a CI/CD pipeline for vms-askai-service. They added the .ci-settings.xml file but the issue persisted. They later resolved the issue by fixing relative path issues. The discussion thread can be found at <https://axiamatic.slack.com/archives/C02CREJ9EJ2/p1688451831425289?thread_ts=1688367311.116169&cid=C02CREJ9EJ2>.,2,"['resolved issue', 'fixed relative path issues']","['401 unauthorized issue', 'CI/CD pipeline setup']",,[],UNKNOWN
|
|
2023-07-05T10:26:17.016289,2023-07-05T22:13:28.306259,hchintamreddy,"{'ppant', 'rtaraniganty', 'aganivada', 'hchintamreddy'}",4,"The discussion thread is about an exception encountered in the unit tests of Pulse Manager after updating the axm-commons version. The exception is related to a null pointer exception in the SsmMultiInstanceConfigClient class, specifically in the createSsmClient method. The cause of the exception is a null region parameter. The proposed solution is to add a check for the AWS_REGION environment variable and pass a default value if it is not present. The fix has been implemented in a patch and is awaiting review.",14,"['exception', 'unit tests', 'Pulse Manager', 'axm-commons', 'null pointer exception', 'SsmMultiInstanceConfigClient', 'createSsmClient', 'AWS_REGION', 'patch', 'review']",[],,"['COLL-2698', 'COLL-2698', 'COLL-2698', 'UTF-8', 'UTF-8']",UNKNOWN
|
|
2023-07-05T07:22:15.678079,2023-07-05T07:27:20.284079,aganivada,"{'aganivada', 'pjha'}",2,Aganivada asks Pjha to pull the latest develon of CDK to the multi-instance branch and resolve conflicts. Pjha agrees and says they will check and resolve the conflicts when they have the chance. Aganivada says there is no hurry and asks Pjha to let them know once they have looked into it.,7,"['Pulling latest develon of CDK', 'Resolving conflicts']",[],,[],UNKNOWN
|
|
2023-07-03T22:46:11.430299,2023-07-04T03:34:37.710679,pjha,"{'aganivada', 'askumar', 'pjha'}",3,The team is discussing the configuration of RDS Proxy for the test database. They are considering enabling it for the int database to check if they are getting the desired stats. They discuss the need to recreate RDS secrets and the possibility of managing two secrets. They also mention the differences in the database information between the existing secrets. No JIRA ticket or other links are mentioned.,9,"['configuration of RDS Proxy', 'enabling RDS Proxy for int database', 'recreating RDS secrets', 'managing two secrets']",['no JIRA ticket or other links mentioned'],NEUTRAL,[],UNKNOWN
|
|
2023-07-04T01:54:34.469649,2023-07-04T02:04:04.144789,askumar,"{'askumar', 'aganivada'}",2,The team has updated the maximum ACU for the INT Aurora cluster to 5 ACUs due to high CPU utilization. They plan to monitor it better once the proxy is configured.,3,"['maximum ACU update', 'monitoring']","['high CPU utilization', 'proxy configuration']",,[],UNKNOWN
|
|
2023-07-03T05:17:44.908239,2023-07-04T01:25:20.881849,aganivada,"{'aganivada', 'ppant'}",2,"The discussion thread is about adding additional invitation types and fixing issues with email templates. ppant made changes to the templates and resolved naming issues. aganivada tested the changes and encountered exceptions, which were fixed by ppant. They discussed missing parameters in the email template and made necessary updates. They also discussed the requirement of SSO connection and made changes accordingly. The changes were reviewed and approved by ppant.",43,"['Adding additional invitation types', 'Fixing issues with email templates', 'Resolving naming issues', 'Updating missing parameters in email template', 'Making changes for SSO connection', 'Reviewing and approving changes']",['Encountering exceptions during testing'],POSITIVE,['PLAT-2243'],RESOLVED_OR_CLOSED
|
|
2023-07-02T23:55:11.116169,2023-07-03T23:33:30.077599,nsrivastava,"{'aganivada', 'rtaraniganty', 'nsrivastava'}",3,The discussion thread is about the need for a Docker image for the gl pipeline of the teams-integrator node.js app. Aganivada suggests using custom Docker images and provides examples. Nsrivastava plans to update the base image with Node.js but Aganivada suggests creating a new image to avoid unnecessary packages. They also discuss issues with pulling the axm-parent and suggest making tweaks to the build process.,26,"['custom Docker images', 'updating base image with Node.js', 'creating a new image', 'tweaks to the build process']",['issues with pulling axm-parent'],NEUTRAL,"['COLL-2683', 'COLL-2683', 'COLL-2683']",UNKNOWN
|
|
2023-07-03T06:19:30.415719,2023-07-03T07:28:46.852119,aganivada,"{'aganivada', 'pjha'}",2,The discussion is about updating the container name for mult-instance in the code changes. Pjha agrees to make the necessary changes and shares the commit for review. Aganivada approves the changes and asks Pjha to post in the merge-request channel. Pjha mentions that there are no known risks and suggests merging the changes to develop by the end of the week. No specific JIRA ticket or other links are mentioned.,5,"['updating container name', 'code changes', 'commit for review', 'approving changes', 'merging changes']","['no known risks', 'no specific JIRA ticket or other links mentioned']",,[],UNKNOWN
|
|
2023-06-28T04:08:51.285219,2023-06-28T10:59:00.330809,ppant,"{'ppant', 'rtaraniganty', 'aganivada'}",3,"ppant mentions that they have made too many commits for multi-instance changes, causing Gitlab's runner to block tenancy. They suggest switching to a shared runner due to previous failures. They provide a link to their merge request branch and mention that it is passing now. They explain that the issue was caused by a dependency on core-data's 2052-SNAPSHOT version, which was deleted from the package registry. They rebuilt it and re-ran the pipeline. rtaraniganty questions if it was built recently and shares a log from the artifact reaper job showing the timestamp of the deleted version. They mention that snapshots older than 21 days are deleted. ppant realizes that their memory may be incorrect.",13,"['switching to shared runner', 'merge request passing', 'rebuilt dependency', 're-ran pipeline']","['too many commits', 'Gitlab runner blocking tenancy', 'deleted dependency version', 'incorrect memory']",,"['PLAT-2052', 'PLAT-2052']",UNKNOWN
|
|
2023-06-28T06:19:11.883969,2023-06-28T06:54:33.760079,askumar,"{'askumar', 'aganivada'}",2,The team is discussing whether to remove the RDS instances in the INT environment now that all the service schemas have been moved to the Aurora cluster. Aganivada suggests giving a few days for commons before deleting completely and asks if there are backups in S3 for other databases. Askumar agrees to keep the instances for another week and mentions that there are snapshots of the DB that can be restored and backups will be taken to S3. They also agree that only the latest backup of all RDS instances data is needed. No references to JIRA tickets or other links are mentioned in the conversation.,5,"['keep instances for another week', 'snapshots of DB', 'backups to S3']","['remove RDS instances', 'delete completely']",,[],UNKNOWN
|
|
2023-06-27T00:39:35.183979,2023-06-27T00:40:24.769859,aganivada,"{'aganivada', 'pjha'}",2,Aganivada asks Pjha to add Askumar to the stage and share credentials with Ashwani for DB migration. They also mention the need for a task to provision an Aurora instance in stage. Pjha agrees to do it. No other specific details or references are mentioned.,2,"['Add Askumar to stage', 'Share credentials with Ashwani', 'Provision Aurora instance in stage']",[],,[],UNKNOWN
|
|
2023-06-26T23:16:40.854389,2023-06-26T23:44:03.343369,pjha,"{'ppant', 'pjha', 'aganivada'}",3,The discussion thread is about the potential issue of SSM mappings still existing after a stack is deleted. It is suggested to delete the service-information from the SSM parameter instead of deleting the entire parameter. There is a mention of adding a TTL date in SSM parameters through CDK and using a lambda function for cleanup. No specific JIRA ticket or links are mentioned.,6,"['Deleting service-information from SSM parameter', 'Adding TTL date in SSM parameters through CDK', 'Using lambda function for cleanup']",['SSM mappings still existing after stack deletion'],NEUTRAL,[],UNKNOWN
|
|
2023-06-26T09:04:19.476239,2023-06-26T11:51:48.932359,rtaraniganty,"{'rtaraniganty', 'pjha'}",2,"The discussion thread is about the completion of tasks for the GL runner, including alarms, sizing up and down during releases. They also discuss the need for a Confluence page on scaling up and down, and decide to create one and link it in the runbook. The links to the relevant Confluence pages are provided.",8,"['completion of tasks for GL runner', 'alarms', 'sizing up and down during releases', 'creation of Confluence page on scaling up and down', 'linking Confluence page in runbook']",[],,[],UNKNOWN
|
|
2023-06-23T10:00:40.871109,2023-06-26T09:03:34.081809,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion is about creating a policy to restrict IAM user access if not connected to VPN. They plan to add the policy to the AxmPowerUserGroup in INT during IST hours to minimize impact. They also mention the need to test GitLab tasks and consider rollback instructions.,3,"['Creating policy to restrict IAM user access', 'Adding policy to AxmPowerUserGroup', 'Minimizing impact during IST hours']","['Testing GitLab tasks', 'Considering rollback instructions']",,[],UNKNOWN
|
|
2023-06-26T08:37:56.824139,2023-06-26T09:02:42.715909,ppant,"{'ppant', 'rtaraniganty'}",2,ppant suggests updating the configs in SSM for multi-instance to improve the structure of the backend code. rtaraniganty approves as long as there is a script to manage the updates automatically. The discussion confirms that the updates will be done via a script. No specific JIRA ticket or other links are mentioned.,3,"['updating configs in SSM for multi-instance', 'improving structure of backend code']",[],,[],UNKNOWN
|
|
2023-06-23T13:14:39.176689,2023-06-23T15:17:37.593839,rtaraniganty,"{'ppant', 'rtaraniganty'}",2,"The discussion is about a potential change in the network/security configuration that may have caused issues with connecting to RDS via sshuttle. The team added P81's security group to Aurora, allowing connections with just VPN. However, there seems to be a problem with the expected functionality.",5,"['potential change in network/security configuration', ""adding P81's security group to Aurora""]","['issues with connecting to RDS via sshuttle', 'problem with expected functionality']",,[],UNKNOWN
|
|
2023-06-22T04:54:48.524229,2023-06-23T04:53:25.167869,askumar,"{'askumar', 'rtaraniganty', 'ppant', 'aganivada'}",4,"The team is trying to migrate a schema from an RDS instance to Aurora RDS writer, but only the referenceId in the table is being migrated and not the referred blob. They discuss the ""lo_compat_privileges"" parameter and its implications. AWS support ticket is raised to enable the parameter. They also discuss the issue with migrating HTML blobs for the notification service and suggest using a brute force POST API to insert the templates. The discussion concludes with the successful migration of the notification templates using a script. No specific JIRA ticket or other links are mentioned.",20,"['successful migration', 'migration of notification templates']","['issue with migrating HTML blobs', 'not migrating referred blob', 'lo_compat_privileges parameter']",MIXED,[],UNKNOWN
|
|
2023-06-20T00:15:12.949629,2023-06-22T22:02:30.243169,ppant,"{'ppant', 'rtaraniganty'}",2,"The discussion thread is about reviewing a document on the structure of multi-instance config in SSM. One team member suggests adding the name and upload time of the user in the JSON. They also discuss adding an option to read and print the parameter. Additionally, they consider fetching all SSM parameters for multi-instance and creating a JSON with the parameters. The script is planned to be added to the cdk-artifacts repo.",10,"['Adding name and upload time of user in JSON', 'Adding option to read and print parameter', 'Fetching all SSM parameters for multi-instance', 'Creating JSON with parameters']",['None'],POSITIVE,[],ON_GOING
|
|
2023-06-21T00:57:10.646369,2023-06-22T17:00:33.815039,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion thread is about reviewing the deployment process for a lambda function using tags. Aganivada added some comments and requested a demo during SOS. Pjha agreed to review the comments and confirmed the demo. Rtaraniganty asked if feature branch versions can be tagged with 'SNAPSHOT' and suggested adding a pre-commit hook script. They also asked about updating the .gitlab-ci.yml file in all lambda repos and suggested moving apt-get installs into the base image.,6,"['reviewing deployment process', 'demo during SOS', 'reviewing comments', 'updating .gitlab-ci.yml file']","['feature branch versions', 'pre-commit hook script', 'moving apt-get installs']",,[],UNKNOWN
|
|
2023-06-19T04:19:56.532659,2023-06-21T06:37:47.799119,aganivada,"{'aganivada', 'rtaraniganty'}",2,"The discussion thread is about an issue with regex not working well with the text(analyzed) field in Logz. Two options were discussed: reverting the field type to keyword(string) or using text(analyzed) with a modified regex expression. The bug ID for the regex issue is 61838. The field was eventually updated to keyword in both the staging and production environments, and the regex is now working.",7,"['regex issue resolved', 'field updated to keyword']",['regex not working well with text field'],,[],UNKNOWN
|
|
2023-06-20T00:17:05.498079,2023-06-20T09:55:08.310219,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,"The discussion thread is about removing an inbound rule from the 'bastion-sg-int' security group. Access to the bastion host is now only allowed for p81 SG, and users need to connect to the Perimeter 81 VPN to login. The process of connecting to the VPN is described in this page: <https://pinstripe.atlassian.net/wiki/spaces/PRODUCT/pages/549585634/Connecting+to+Perimeter+81+VPN>.",7,"['Access to bastion host allowed only for p81 SG', 'Connecting to Perimeter 81 VPN']",['Removing inbound rule from bastion-sg-int security group'],NEUTRAL,[],UNKNOWN
|
|
2023-06-20T00:28:38.740619,2023-06-20T01:19:13.171209,sranjan,"{'aganivada', 'sranjan'}",2,Sranjan asks aganivada to bounce MB in stage and cc bganganna. Aganivada responds that it will be done in another 5-10 minutes. No specific details or references are mentioned in the discussion thread.,2,"['bouncing MB', 'cc bganganna']",[],NEUTRAL,[],UNKNOWN
|
|
2023-06-18T22:03:10.549739,2023-06-19T09:59:45.078669,mnirmal,"{'mnirmal', 'rtaraniganty', 'aganivada'}",3,"mnirmal encountered an error while trying to deploy the core-stack sns_events_publisher_stack.py collab-pulse-notification-events-sqs from release/0.9.12. aganivada suggested running the build-package.sh script for es-cluster-initial-setup and ip_authorizer, and then deploying on stage. mnirmal confirmed that the changes were pushed to the release branch. aganivada deployed the changes successfully. mnirmal thanked aganivada. rtaraniganty asked if the deployment dependency page was updated, and mnirmal apologized for forgetting to update it. aganivada asked if collab-pulse-notification-events-sqs was needed, and mnirmal said it wasn't sure and asked pkarthikeyan for confirmation.",23,"['successful deployment', 'changes pushed', 'deployment completed']","['error encountered', 'dependency not updated', 'uncertainty about requirement']",,[],UNKNOWN
|
|
2023-06-18T22:20:24.202269,2023-06-19T08:24:30.751559,aganivada,"{'aganivada', 'rtaraniganty'}",2,"The discussion thread is about an issue with the ID of an SSM parameter getting changed in a commit, causing problems when deploying old stacks. The suggested solution is to delete the SSM parameter, deploy the stack again, and then add the SSM parameter with the correct ID. It is mentioned that service stacks do not need to be redeployed. The change in the ID was not driven by a specific need but was a learning experience for future reviews. No JIRA ticket or other links are mentioned.",9,"['Suggested solution', 'Learning experience']","['Issue with SSM parameter ID', 'Problems when deploying old stacks']",NEUTRAL,[],RESOLVED_OR_CLOSED
|
|
2023-06-15T18:44:51.330729,2023-06-15T22:06:55.841289,aganivada,"{'aganivada', 'pjha'}",2,The discussion is about automatically switching the pipeline to a shared runner if a job is stuck for a certain amount of time. They plan to discuss this further next week. There is documentation on how to revert changes so builds can run back on a shared runner. The documentation link is provided.,5,"['automatically switching pipeline to shared runner', 'documentation on reverting changes']",[],NEUTRAL,[],UNKNOWN
|
|
2023-06-13T23:31:44.538569,2023-06-14T21:21:14.930579,pkarthikeyan,"{'ppant', 'rtaraniganty', 'pkarthikeyan', 'hchintamreddy'}",4,The team is discussing a JDBC connection error in the token-manager. They are seeing warnings in the Spring health endpoint and similar behavior in Lightstep and score-provider. They suspect that the connection pool was maxed out and suggest increasing the max limit of the connection pool size. They also mention that there may be other queries taking longer to execute or erroring out. They consider enabling debug logging for hikari and suspect that the issue may be a transient network issue or a hiccup in RDS. There is no mention of any JIRA ticket or other links.,12,"['JDBC connection error', 'increasing max limit of connection pool size', 'enabling debug logging for hikari', 'transient network issue', 'hiccup in RDS']","['warnings in Spring health endpoint', 'similar behavior in Lightstep and score-provider', 'other queries taking longer to execute or erroring out']",NEUTRAL,[],UNKNOWN
|
|
2023-06-14T16:29:52.370739,2023-06-14T19:54:15.125509,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,rtaraniganty is asking if anyone requested a change in how Logz handles their logs because regex is not working on Stage and Prod accounts but works on INT. aganivada mentions a mapping issue related to mdc.tenantId but believes it is harmless. No JIRA ticket or other links are mentioned.,2,"['regex', 'mapping issue']","['JIRA ticket', 'link']",,[],UNKNOWN
|
|
2023-06-13T22:36:27.555169,2023-06-14T08:33:39.178879,rtaraniganty,"{'askumar', 'svummidi', 'rvaidya', 'rtaraniganty', 'hchintamreddy'}",5,"The team discussed using Snowflake for storing customer metrics, with query times averaging 1-2 seconds for 1.1K records. They also considered using Druid but noted its immutability drawback. Victoria db was used for value metrics in SHN. The team discussed the need for sub-second response times and the possibility of using both Snowflake and Druid for different purposes. They also mentioned the option of dumping data into Snowflake and using a pipeline to generate synthesized data stored in Druid for faster UI performance.",23,"['Snowflake', 'query times', '1-2 seconds', '1.1K records', 'Victoria db', 'sub-second response times', 'pipeline', 'synthesized data', 'faster UI performance']","['Druid', 'immutability drawback']",,[],UNKNOWN
|
|
2023-06-12T00:51:54.545279,2023-06-14T07:44:31.272749,askumar,"{'askumar', 'rtaraniganty', 'pjha'}",3,"The discussion is about high CPU utilization in Aurora clusters in the INT environment. They are considering increasing the max vCPU or using multiple clusters due to the high number of connections. They discuss the current vCPU configuration, RDS sizes, and suggest increasing the min and max ACU. They also mention the possibility of using a proxy to reduce the DB connection requirement.",22,"['increasing max vCPU', 'using multiple clusters', 'increasing min and max ACU', 'using a proxy']","['high CPU utilization', 'high number of connections', 'current vCPU configuration', 'RDS sizes']",NEUTRAL,[],ON_GOING
|
|
2023-06-12T09:14:36.112839,2023-06-14T07:33:49.334849,snangia,"{'pjha', 'askumar', 'svummidi', 'rsrinivasan', 'snangia', 'rtaraniganty'}",6,"The discussion thread is about a user-action service that is stuck in the ""update_rollback_in_progress"" state. The team suggests various solutions, such as updating the desired count to 0, canceling the deployment, and checking for exceptions related to parsing notification events. They also discuss empty scores in Druid and the need to handle expected cases to prevent ""java.lang.IllegalStateException"" errors. No specific JIRA ticket or other links are mentioned.",44,"['Various solutions suggested', 'Handling expected cases', 'Preventing errors']","['Service stuck in update_rollback_in_progress state', 'Empty scores in Druid']",NEUTRAL,['COLL-2545'],ON_GOING
|
|
2023-06-12T22:18:15.302029,2023-06-13T09:44:21.170239,hchintamreddy,"{'askumar', 'rtaraniganty', 'hchintamreddy'}",3,"There are indexing failures for production logs, specifically from lambdas. Prabhu raised a merge request to address the issue.",4,"['indexing failures', 'production logs', 'merge request']",['lambdas'],,[],UNKNOWN
|
|
2023-06-08T15:46:45.265519,2023-06-08T21:14:47.771399,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"rtaraniganty mentions that if they hadn't taken a day off and closed their previous sprint tasks before the retro, their team would have achieved the highest per capita in the last 15 weeks with 30 points. aganivada acknowledges this achievement and mentions that the previous highest was 160+ less than a month ago, setting a new goal for the team.",2,"['achievement', 'highest per capita', 'new goal']",[],,[],UNKNOWN
|
|
2023-06-08T11:34:15.904479,2023-06-08T21:05:09.149369,rsrinivasan,"{'aganivada', 'rtaraniganty', 'rsrinivasan', 'gshenoy'}",4,"The discussion thread is about an issue with the integration account in Logz. The fields under ""mdc"" are getting dropped and not indexed. The issue is related to the field ""mdc.tenantId"" being mapped as a long but sent with a null value. The team is working on creating a rule to accept only long values for this field. There is also a mention of a bug related to null check in the common lib for mdc. A JIRA ticket has been created for this bug: <https://pinstripe.atlassian.net/browse/PLAT-2173>.",17,[],"['integration account issue', 'fields getting dropped', 'mdc.tenantId mapping issue', 'bug in common lib for mdc']",,['PLAT-2173'],ON_GOING
|
|
2023-06-08T09:07:48.613329,2023-06-08T09:40:32.031969,aganivada,"{'aganivada', 'rtaraniganty'}",2,The discussion is about leveraging point-in-time recovery for DynamoDB backup. They plan to add a line to CDK and deploy all DynamoDB instances. The backups are taken daily and provide 35 days of backup. The monthly cost for backups is estimated to be around $6. A task will be added to test table recovery. Reference: <https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html?icmpid=docs_dynamodb_help_panel_hp_pitr>,4,"['leveraging point-in-time recovery', 'adding line to CDK', 'deploying all DynamoDB instances', 'daily backups', '35 days of backup', 'monthly cost of $6', 'testing table recovery']",[],,[],UNKNOWN
|
|
2023-06-07T07:58:54.127609,2023-06-07T21:58:21.737899,aganivada,"{'aganivada', 'askumar', 'rtaraniganty', 'gshenoy'}",4,The discussion thread involves aganivada encountering an S3 access denied error while deploying a service/core stack to int. askumar helps by deploying core data and admin-gw. They encounter issues related to liquibase changes and stale personas in INT. gshenoy resolves the issues. aganivada and askumar also discuss intermittent deployment issues with CDK and suggest using pyenv for isolation.,42,"['helpful deployment', 'issue resolution', 'discussion on CDK']","['S3 access denied error', 'liquibase changes issue', 'stale personas in INT', 'intermittent deployment issues']",,"['PLAT-2037', 'DISC-3094']",UNKNOWN
|
|
2023-05-31T03:02:30.914489,2023-06-06T03:29:00.266179,ppant,"{'ppant', 'rtaraniganty', 'aganivada'}",3,ppant has updated the document for backend changes for multi instances and is asking for a review. rtaraniganty suggests having a review meeting with the team to discuss the changes. They also mention the rewiring of clients and the need for clarity on widespread changes. ppant confirms that only a single client is being created in most services. A review meeting is planned for early next week.,15,"['document update', 'review meeting', 'single client']",['widespread changes'],,[],UNKNOWN
|
|
2023-06-04T23:39:12.321359,2023-06-05T10:21:09.497289,rsrinivasan,"{'aganivada', 'rsrinivasan', 'pjha'}",3,"The discussion thread is about resolving a ""not enough space"" error on the Axiamatic GitLab runner. The team identifies that the issue is caused by a lack of space on the Docker client. They check the available space and find that 21% is used with 93G available. They discuss implementing an alert when capacity reaches 60% and plan to clean up unused images and volumes to free up space. The issue is resolved, and the user is able to generate a build and deploy. No specific JIRA ticket or other links are mentioned.",12,"['resolved issue', 'build and deploy']","['not enough space', 'lack of space', 'error', 'Axiamatic GitLab runner']",,[],UNKNOWN
|
|
2023-06-05T04:47:41.110669,2023-06-05T08:45:49.596049,snangia,"{'aganivada', 'snangia', 'pjha', 'rtaraniganty'}",4,The discussion thread revolves around a GitLab pipeline failure due to an authentication issue with accessing a parent POM. The team tries to troubleshoot the issue by clearing the runner cache and checking the GitLab status. They also raise a support ticket with GitLab but face difficulties in submitting it. The team discusses the possibility of an upgrade to the parent POM causing the issue and compares the successful builds of other projects. They eventually manage to submit a support ticket and await a response.,30,"['Troubleshooting', 'Clearing runner cache', 'Checking GitLab status', 'Comparing successful builds', 'Submitting support ticket']","['Authentication issue', 'Difficulty in submitting support ticket', 'Possible upgrade causing the issue']",NEUTRAL,['COLL-2520'],ON_GOING
|
|
2023-06-02T05:22:47.882089,2023-06-02T10:50:31.384969,ppant,"{'ppant', 'rtaraniganty'}",2,"The discussion thread is about a version mismatch issue with the CDK (Cloud Development Kit) v2. The error message ""This CDK CLI is not compatible with the CDK library used by your application"" is encountered during deployment. The suggested solution is to fix the CDK version at 2.8.0 in the common script. It is also mentioned that the issue occurs when different versions of npx are used. The full output of the synth that failed is provided. It is suggested to upgrade the CLI to the latest version, but it is unclear how to do so. The discussion also mentions that the issue is specific to the core stack and that deploying app services works fine. It is noted that installing CDK v2 globally and removing aliases resolves the issue. No references to JIRA tickets or other links are provided.",14,"['Suggested solution: fix CDK version at 2.8.0 in common script', 'Issue specific to core stack', 'Deploying app services works fine', 'Installing CDK v2 globally and removing aliases resolves the issue']","['Version mismatch issue with CDK v2', ""Error message: 'This CDK CLI is not compatible with the CDK library used by your application'"", 'Issue occurs when different versions of npx are used', 'Unclear how to upgrade CLI to the latest version']",MIXED,[],ON_GOING
|
|
2023-06-02T01:17:01.105649,2023-06-02T03:35:47.136769,askumar,"{'askumar', 'aganivada'}",2,The discussion thread is about adding the @Transactional annotation to Delegate methods. Some tests are failing because the transaction is not committed in case of exceptions. The suggestion is to add an interceptor to close the transaction in failure cases. The conversation can be found at: <https://axiamatic.slack.com/archives/C028U328HMG/p1685554068875239?thread_ts=1685552661.038959&cid=C028U328HMG>,3,"['Adding @Transactional annotation', 'Adding interceptor to close transaction']","['Tests failing', 'Transaction not committed in case of exceptions']",POSITIVE,[],ON_GOING
|
|
2023-06-01T21:43:46.535339,2023-06-01T22:05:28.275509,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,The discussion thread is about a code modification that was checked in. The team is discussing allowing SELECT to work and will be looking at the code in the GitLab repository at <https://gitlab.com/axiamatic-main/3rdparty-preliquibase>. No specific details about the code modification or the reason for allowing SELECT are mentioned.,2,"['code modification', 'SELECT']",[],,[],UNKNOWN
|
|
2023-05-30T04:10:29.544959,2023-06-01T21:21:04.477889,aganivada,"{'aganivada', 'sranjan'}",2,The discussion thread is about an error in the jira-task-container that occurs when querying for non-existing tenants. The issue is caused by entries for non-existing tenants in the webhook_config table. A JIRA ticket (DISC-3071) has been created to address this issue. There is also mention of tenant coordination and disabling logging in the int environment.,6,"['JIRA ticket created', 'Addressing the issue']","['Error in jira-task-container', 'Non-existing tenants', 'Entries in webhook_config table', 'Tenant coordination', 'Disabling logging']",,['DISC-3071'],UNKNOWN
|
|
2023-05-31T23:03:37.062969,2023-06-01T20:16:59.821809,rsrinivasan,"{'aganivada', 'rtaraniganty', 'rsrinivasan'}",3,"The discussion thread revolves around performance issues caused by an alert in the Axiamatic account's cluster. The alert has been disabled temporarily, and suggestions have been made to optimize the search query and suppress error cases. The logs in the INT environment are filling up rapidly, and there have been instances of running out of storage capacity. The logging level has been updated, but some instances still need to be checked. A link to the logz.io platform is provided for further investigation.",11,"['Temporary disabling of alert', 'Optimizing search query', 'Suppressing error cases', 'Updating logging level']","['Performance issues', 'Logs filling up rapidly', 'Running out of storage capacity', 'Instances needing checking']",NEGATIVE,[],UNKNOWN
|
|
2023-05-31T20:38:09.881599,2023-05-31T23:13:23.682969,aganivada,"{'aganivada', 'ppant'}",2,ppant and pjha are being congratulated by aganivada. ppant asks aganivada when they will come to Bangalore to give them a party. aganivada responds that they will come as soon as they get a chance. No references to JIRA ticket or other links are mentioned.,3,['congratulations'],[],,[],UNKNOWN
|
|
2023-05-31T07:58:51.831239,2023-05-31T17:50:34.092369,aganivada,"{'aganivada', 'rtaraniganty'}",2,"aganivada asks the team to review a document on the platform epics. rtaraniganty suggests using Swanly instead. aganivada agrees to move the document to Swanly for tracking, but finds Confluence easier for planning. Swanly is helpful for tracking execution. No specific details or links are mentioned.",3,"['Swanly', 'tracking execution']","['Confluence', 'planning']",,[],UNKNOWN
|
|
2023-05-29T20:49:00.326999,2023-05-31T06:23:51.122639,aganivada,"{'aganivada', 'askumar'}",2,The discussion thread is about configuring Snowflake with STS (Security Token Service) for data integration with both INT and PROD S3 environments. Askumar confirms that the configuration works in INT and asks if it should be configured for prod. Aganivada agrees and asks to test it with INT. Askumar confirms that the prod account setup is complete and data from both INT and PROD S3 environments will be available in Snowflake.,7,"['Snowflake configuration with STS', 'Data integration with S3', 'INT environment', 'PROD environment']",[],,[],UNKNOWN
|
|
2023-05-30T03:13:11.957109,2023-05-30T08:51:04.391719,ppant,"{'ppant', 'rtaraniganty', 'rsrinivasan', 'aganivada'}",4,"The team is discussing an issue with the Notification-service's tests not being compatible with the latest versions of axm-commons. They are getting an unsatisfied dependency exception after updating axm-commons in the pom. They have tried adding a mock s2sWebClient and comparing the application-test.yml with other services, but the issue persists. The build works fine, but only the tests are failing. They have resolved the issue by adding some configurations and a mock bean. A merge request has been opened for this.",14,"['issue resolution', 'merge request']","['unsatisfied dependency exception', 'test failure']",,[],UNKNOWN
|
|
2023-05-29T05:59:34.355399,2023-05-30T08:50:52.056859,pjha,"{'aganivada', 'askumar', 'pjha', 'rtaraniganty'}",4,"The team discussed upgrading the RDS-Aurora-Postgres engine version to 15.2. They reviewed two strategies, with AWS recommending the second one. They also discussed the before-upgrade checklist and the need for a dry run. Two approaches were considered for the upgrade process. The team tested the pre-check commands on a clone created with a snapshot and confirmed that everything was working fine. They decided to use approach-1 for integration and approach-2 for stage and prod. The RDS instance was successfully upgraded, and the core-data service was deployed pointing to the upgraded Postgres RDS. The team confirmed that the upgrade was completed and merged the Aurora branch to develop.",25,"['Upgrading RDS-Aurora-Postgres engine version', 'Reviewing upgrade strategies', 'Testing pre-check commands', 'Successful upgrade of RDS instance', 'Deployment of core-data service', 'Completion of upgrade', 'Merging Aurora branch to develop']",['None'],POSITIVE,[],UNKNOWN
|
|
2023-05-29T23:49:43.901229,2023-05-30T02:00:50.815289,nsrivastava,"{'aganivada', 'nsrivastava'}",2,"The team was facing an issue with uploading the Slack-Integrator snapshot dependency. The job mentioned building the artifact, but it was not present in the package registry. The SC MR was failing due to the dependency not being found. After investigating, it was discovered that the issue was resolved by syncing the dev branch with the main branch.",6,"['issue resolved', 'syncing branches']","['uploading dependency', 'missing artifact', 'SC MR failing']",,"['COLL-2498', 'COLL-2498']",RESOLVED_OR_CLOSED
|
|
2023-05-29T21:13:15.607239,2023-05-29T22:54:53.342369,rtaraniganty,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion is about adding default permissions to ECS tasks to access SSM parameters. The team is considering adding a prefix to the SSM parameters to track the ones added only for admin-gw. They also discuss the benefits of letting services directly read the parameters they need. There may be cases where explicit permissions were added for certain keys. No specific JIRA ticket or other links are mentioned.,9,"['Adding default permissions to ECS tasks', 'Adding prefix to SSM parameters', 'Letting services directly read parameters']",['No specific JIRA ticket or other links mentioned'],NEUTRAL,[],UNKNOWN
|
|
2023-05-17T03:17:03.949609,2023-05-28T22:45:10.684489,askumar,"{'askumar', 'rtaraniganty', 'aganivada'}",3,The discussion is about the migration plan for the service database. They discuss merging the Liquibase tables and estimate that the migration will take at least 2 releases. They also consider using pgdump to update/insert missing records and suggest prepopulating the Liquibase table to avoid each service copying its own data.,12,"['migration plan', 'merging Liquibase tables', 'using pgdump', 'prepopulating Liquibase table']",['none'],POSITIVE,[],ON_GOING
|
|
2023-05-26T05:31:04.759009,2023-05-26T10:05:56.606319,nsrivastava,"{'aganivada', 'pjha', 'nsrivastava'}",3,The discussion thread is about a job in SC that was abruptly terminated with an error message. The team is investigating the issue and suspect it may be a configuration problem. They are also monitoring CPU usage and planning to set alerts for resource shortages. There is a mention of a failed test and a webhook configuration change for SC.,12,"['Investigating issue', 'Monitoring CPU usage', 'Setting alerts for resource shortages']","['Job termination with error message', 'Configuration problem', 'Failed test', 'Webhook configuration change']",NEGATIVE,[],UNKNOWN
|
|
2023-05-24T09:10:58.529099,2023-05-25T23:30:33.235899,rtaraniganty,"{'mnirmal', 'araman', 'anair', 'rtaraniganty', 'mli'}",5,"The discussion thread is about changing the CTA (Call to Action) on the Slack platform. The team wants to change ""Complete Pulse"" to ""Start Pulse"" and ""Next"" to ""Submit"" on the FINAL Pulse page. The decision was made based on the introduction of the ability to complete a half-finished Pulse. The thread references a previous discussion during the development phase. No JIRA ticket or other links are mentioned.",7,"['CTA change', 'Start Pulse', 'Submit']","['Complete Pulse', 'Next']",POSITIVE,[],ON_GOING
|
|
2023-05-25T09:04:16.536229,2023-05-25T09:13:04.516609,aganivada,"{'aganivada', 'pjha'}",2,"The discussion is about finding all the stacks deployed via multi-env and adding a tag for all multi-instance deployments in AWS. It is mentioned that the Slack message doesn't specify the deployment version, but tags can be added to resources created through multi-instance deployment. No specific details or references to JIRA or other links are provided.",4,"['finding stacks deployed via multi-env', 'adding tags for multi-instance deployments in AWS', 'tags can be added to resources created through multi-instance deployment']","[""Slack message doesn't specify deployment version"", 'no specific details or references provided']",NEUTRAL,[],UNKNOWN
|
|
2023-05-24T22:42:49.283339,2023-05-24T23:00:41.923049,vtiwari,"{'ppant', 'vtiwari', 'aganivada'}",3,"The discussion thread is about vtiwari encountering an issue with accessing tenant and other APIs due to the workspace having no available licenses. ppant suggests reopening the browser, but it doesn't work. aganivada adds more licenses and suggests trying again. vtiwari confirms that it works after aganivada's intervention. No references to JIRA ticket or other links are mentioned.",10,['Issue resolved'],"['Access issue', 'No available licenses']",,[],UNKNOWN
|
|
2023-05-24T09:11:17.070379,2023-05-24T10:50:00.107489,rtaraniganty,"{'araman', 'rtaraniganty', 'hchintamreddy'}",3,"The discussion thread is about the possibility of adding a back button in a Slack bot. The issue arose due to dynamic navigation caused by follow-up questions. The original design included a back button, but it was removed due to complexity. The user expresses concern about the lack of a back button and acknowledges the challenges involved. No specific JIRA ticket or other links are mentioned.",8,[],['lack of back button'],NEUTRAL,[],UNKNOWN
|
|
2023-05-24T09:13:52.532149,2023-05-24T09:31:49.257739,bganganna,"{'mnirmal', 'bganganna'}",2,"The discussion thread is about a missed improvement in the pulse card. Bganganna mentions that the back button for the Slack survey was missed, but it may be present in Teams. Mnirmal clarifies that ""Complete Pulse"" was part of the spec, and earlier it was ""Start Pulse.""",4,"['back button for Slack survey', 'Complete Pulse']","['missed improvement', 'Start Pulse']",,[],UNKNOWN
|
|
2023-05-24T04:13:48.611679,2023-05-24T06:54:42.318159,hchintamreddy,"{'aganivada', 'sjain', 'hchintamreddy'}",3,There was an issue with a stuck deployment in the INT environment for Pulse Manager. The error message indicated a problem with pulling the container image. hchintamreddy asked sjain if they had pulled the latest develop branch for CDK deployment. hchintamreddy then restarted the deployment and it was successful. The issue was resolved.,11,"['stuck deployment', 'successful resolution']",['problem with pulling container image'],,[],UNKNOWN
|
|
2023-05-22T22:05:17.645079,2023-05-24T00:48:02.720559,rsrinivasan,"{'sjain', 'rsrinivasan', 'mnirmal', 'snangia', 'rtaraniganty', 'hchintamreddy'}",6,"The discussion thread revolves around an issue where a user's response to a pulse survey did not get recorded. It is suspected that the pulse expired before the response was submitted. The team discusses potential solutions, such as removing the check for pulse expiration in the pulse manager system and handling it in the survey coordinator system instead. A JIRA ticket is proposed to address this issue. There is also a mention of an error in parsing an action ID. The issue seems to affect all users and has been ongoing since 5/21. A fix for the NumberFormatException has been deployed, and the issue with Seshan's submission is attributed to a race condition.",39,"['Potential solutions discussed', 'JIRA ticket proposed', 'Fix for NumberFormatException deployed']","['User response not recorded', 'Pulse expired before response submitted', 'Error in parsing action ID', 'Issue affecting all users', 'Ongoing since 5/21', ""Race condition causing Seshan's submission issue""]",NEUTRAL,[],ON_GOING
|
|
2023-05-21T09:06:37.884949,2023-05-23T08:52:40.430879,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"The discussion thread is about changes made to the latest-images script to sort the output by date and print multiple entries if needed. The script is used to verify builds and identify release builds. The admin-gw was updated to name builds with ""SNAPSHOT"" for non-main branches.",3,"['Sorting output by date', 'Printing multiple entries', 'Verifying builds', 'Identifying release builds', 'Updating admin-gw']",['None'],POSITIVE,[],UNKNOWN
|
|
2023-05-22T21:02:16.276599,2023-05-23T08:07:31.473709,aganivada,"{'aganivada', 'ppant', 'bganganna', 'mnirmal'}",4,"The discussion thread is about an issue with the email template ""collab-web-survey-v1"". The team suspects that the issue is not related to the VPN changes. They discuss testing and deployment of templates in different environments and suggest checking the database for template updates. They also mention a commit with new placeholder variables. Finally, they plan to deploy a new version and assign a JIRA ticket to mnirmal.",18,"['email template issue', 'testing and deployment', 'checking database for updates', 'new version deployment']",['VPN changes'],NEUTRAL,"['PLAT-2067', 'COLL-2479']",ON_GOING
|
|
2023-05-22T22:01:24.842979,2023-05-22T22:02:39.471729,pjha,"{'aganivada', 'pjha'}",2,pjha requested aganivada to review the multi-instance-deployment phase-1 changes from the infra side. The changes were enabled for experiment-service and tenancy-service. aganivada asked pjha to post the reviews in the merge-requests channel. The link to the changes is <https://gitlab.com/axiamatic-main/axm-deployment/base-infra/-/merge_requests/423/diffs>.,2,"['multi-instance-deployment', 'infra side', 'experiment-service', 'tenancy-service']",[],,[],UNKNOWN
|
|
2023-05-22T04:44:27.194579,2023-05-22T05:40:53.302399,rsrinivasan,"{'aganivada', 'ppant', 'rsrinivasan', 'mnirmal'}",4,"rsrinivasan reported a 403 forbidden error for the notification service in the integration environment. aganivada suggested trying from VPN. rsrinivasan asked mnirmal to try from VPN, and ppant confirmed it worked for them. mnirmal also confirmed it worked.",5,['VPN'],"['403 forbidden error', 'notification service']",,[],UNKNOWN
|
|
2023-05-22T04:30:00.970569,2023-05-22T05:01:55.704879,aganivada,"{'aganivada', 'askumar', 'psomasamudram563', 'gshenoy'}",4,"The team discusses an issue with the ""createProductOmnibus"" method being flagged as read-only, causing errors. They suspect that the transaction manager is considering the entire transaction as read-only because the first transaction is a read. They mention a JIRA ticket (PLAT-2066) and consider forcing the ""readonly"" flag to false if the library cannot fix the issue. The discussion concludes with confirmation that the issue is resolved.",17,"['createProductOmnibus method', 'transaction manager', 'JIRA ticket PLAT-2066', 'issue resolved']","['read-only flag', 'errors']",,['PLAT-2066'],UNKNOWN
|
|
2023-05-22T02:45:56.014699,2023-05-22T03:51:21.764999,mnirmal,"{'mnirmal', 'aganivada'}",2,aganivada is creating a snapshot of the stage DB for mnirmal to debug a PMS issue. mnirmal is okay with the delay. aganivada asks mnirmal to try some files from a specific link and will remove the restored instance in stage once confirmed by collab.,7,"['creating snapshot', 'debugging PMS issue', 'mnirmal okay with delay', 'trying files from link']",['removing restored instance'],,[],UNKNOWN
|
|
2023-05-22T02:02:23.559989,2023-05-22T02:44:16.935749,sranjan,"{'aganivada', 'rsrinivasan', 'sranjan'}",3,"The team is discussing an issue where they are getting a lot of log messages saying ""Failed to parse given rule"" in the Jira container. They suspect that the issue may be related to an outdated version of the platform libs common (0.0.10) and suggest updating it to the latest version. They also mention that this error may be harmless unless rbac is being used in the Jira service. A tracker ticket has been created to address the issue.",11,['Updating platform libs common to latest version'],"['Failed to parse given rule', 'Outdated version of platform libs common', 'Error may be harmless', 'RBAC in Jira service', 'Tracker ticket created']",,[],UNKNOWN
|
|
2023-05-20T01:11:56.406549,2023-05-20T02:01:49.058939,aganivada,"{'aganivada', 'askumar'}",2,"askumar informs aganivada that they have stopped and are deleting unused clusters. askumar also mentions that there is one database, ""vector-db-testing,"" being used by rsrinivasan for testing. No JIRA ticket or other links are mentioned.",3,"['stopped and deleting unused clusters', 'vector-db-testing being used for testing']",[],,[],UNKNOWN
|
|
2023-05-18T00:15:32.359469,2023-05-18T01:30:57.301169,aganivada,"{'aganivada', 'pjha', 'bganganna'}",3,"The team noticed that authentication redirects were not working for the GL-runner in the production environment, but were working fine in other environments. They discovered that this was due to bot-protection enabled in prod, causing Auth0 to think the calls from GL-runner were coming from a bot. They whitelisted the IP on Auth0 and confirmed that it was working. A sanity test was triggered on prod.",11,"['Authentication redirects fixed', 'Whitelisting IP on Auth0', 'Sanity test triggered on prod']","['Authentication redirects not working in prod', 'Bot-protection causing issues']",POSITIVE,[],RESOLVED_OR_CLOSED
|
|
2023-05-17T10:27:36.651589,2023-05-17T22:09:54.636269,rtaraniganty,"{'aganivada', 'rtaraniganty', 'askumar', 'pjha'}",4,"The team plans to make upgrades in the next few weeks, including upgrading Opensearch ES from 1.2 to 1.3 and then to 2.x. They also want to migrate from RDS to Aurora and create an Aurora instance with the same version as in production. They will then trial the latest version before attempting it in stage and production. They also need shell scripts for ES re-indexing. The Aurora version in int is confirmed to be the same as in production. No JIRA ticket or other links are mentioned.",4,"['upgrades', 'Opensearch ES', 'RDS to Aurora migration', 'Aurora instance creation', 'ES re-indexing']",[],,[],UNKNOWN
|
|
2023-04-11T23:15:24.499599,2023-05-17T20:34:07.541339,ppant,"{'rvaidya', 'aganivada', 'ppant', 'rtaraniganty', 'anair'}",5,The discussion thread is about controlling invitation emails via feature flags. They plan to introduce feature flags or a parameter in the API to use custom templates for sending invitation emails. They discuss different cases where invitations are sent and make suggestions for improving the wording and content of the templates. They also mention that the platform team is working on a change to stop Auth0 from sending invitation emails and instead use their notification service. They provide a sample API request and create a JIRA ticket for the task.,24,"['introducing feature flags', 'using custom templates for invitation emails', 'improving wording and content of templates', 'platform team working on change to stop Auth0 from sending invitation emails', 'sample API request', 'creating JIRA ticket']",[],,['DISC-2997'],ON_GOING
|
|
2023-05-16T03:13:42.734789,2023-05-17T03:57:27.971719,aganivada,"{'pmangalapuri', 'aganivada', 'araman', 'bganganna', 'sranjan'}",5,"The discussion thread is about deploying the vault-access service with CDK changes to fix an authentication issue. They discuss verifying report generation after deployment and whitelisting oauth-related endpoints for web surveys and Jira web hooks. They also mention including regression tests for reporting, web-app survey, and Jira-webhook in the next sprint. There is a mention of a failing Jira test and a discussion about the access to vault for different endpoints. No specific JIRA ticket or links are mentioned.",18,"['deploying vault-access service', 'CDK changes', 'verifying report generation', 'whitelisting oauth-related endpoints', 'regression tests', 'web-app survey', 'Jira-webhook']","['authentication issue', 'failing Jira test', 'access to vault for different endpoints']",NEUTRAL,[],UNKNOWN
|
|
2023-05-16T10:12:51.549539,2023-05-16T10:37:45.095079,aganivada,"{'aganivada', 'askumar'}",2,The discussion thread is about migrating data from one Snowflake instance to another. Askumar mentions that they don't need to migrate data as they already have one month's data in S3. Aganivada suggests using AWS S3 to copy data into their table. Aganivada then asks if they can export and import config/scripts in Snowflake when provisioning a new account.,3,"['migrating data', 'using AWS S3', 'exporting/importing config/scripts']",[],,[],UNKNOWN
|
|
2023-05-16T06:28:08.403699,2023-05-16T06:58:46.432079,aganivada,"{'aganivada', 'ppant'}",2,"There was a build failure in the develop branch after merging HF changes in tenancy. The failure was due to some random tests failing, but passing locally. Retriggering the pipeline resolved the issue, suggesting it may be related to parallel execution of tests. The specific test that failed in the morning was `LinkVendorCustomerTest.testGetCustomersWithoutBeingOrgAdmin`. Annotating this test with `same_thread` prevented further failures. It was concluded that the test fails when run in multiple threads.",9,"['Retriggering the pipeline resolved the issue', 'Annotating the test with `same_thread` prevented further failures']","['Build failure in the develop branch', 'Random tests failing', 'Test failed in the morning', 'Test fails when run in multiple threads']",NEGATIVE,[],RESOLVED_OR_CLOSED
|
|
2023-05-16T05:54:29.302749,2023-05-16T06:29:33.501779,aganivada,"{'aganivada', 'askumar'}",2,"The discussion is about the progress of the internal database migration. Askumar is making a change in CDK to use the same secret ID instead of creating a new parameter in secret manager. The password change is being handled by pjha. Askumar is also working on the migration plan document. The migration for Core will be done before the branch cut, and a plan for Core in the stage will also be created. No specific JIRA ticket or other links are mentioned.",6,"['progress of internal database migration', 'change in CDK', 'migration plan document']",['password change being handled by pjha'],,[],UNKNOWN
|
|
2023-05-16T02:22:27.276629,2023-05-16T02:30:22.983459,ppant,"{'ppant', 'rsrinivasan'}",2,"The discussion is about the failure of the pipeline for the apps-workflow-lambda due to an existing wheel with the same package name. They consider deleting the existing wheel and discuss adding a deletion trigger to the pipeline. They also discuss removing the stage altogether since the lambda package is not imported anywhere. They mention that for lambdas, they typically don't publish to PyPI unless a certain condition is met. They discuss a variable that determines if the branch is protected and mention that it is set to 1 for apps lambda. They suggest setting it explicitly to zero. No JIRA ticket or other links are mentioned.",11,"['deleting existing wheel', 'adding deletion trigger to pipeline', 'setting branch protection to zero']","['failure of pipeline', 'existing wheel with same package name', 'removing stage', 'lambda package not imported', 'not publishing to PyPI', 'branch protection set to 1']",NEGATIVE,[],ON_GOING
|
|
2023-05-15T23:04:03.677469,2023-05-16T01:35:07.209189,aganivada,"{'aganivada', 'askumar', 'pjha'}",3,"In the discussion thread, aganivada asks askumar to review the changes related to Aurora that were merged into the develop branch. askumar confirms that all the changes are present. aganivada informs pjha that once the three stacks are updated, they can merge cdkv2 to develop. pjha confirms that they are working on the last stack. pjha also mentions that aganivada merged their changes to the feature/PLAT-792 branch.",6,"['review changes', 'changes present', 'merge cdkv2', 'working on last stack', 'merged changes']",[],,['PLAT-792'],UNKNOWN
|
|
2023-05-15T23:29:46.384089,2023-05-15T23:55:35.212519,anair,"{'aganivada', 'anair'}",2,"Anair and Aganivada are discussing the preparation for 1-2 Okta integrations. Aganivada mentions that the documentation work for Okta has already been done and shares two articles added by rsrinivasan: ""Testing SSO in INT"" and ""SAML Enterprise Connection.""",3,"['Okta integration', 'documentation work']",[],,[],UNKNOWN
|
|
2023-05-15T22:34:56.814089,2023-05-15T22:54:50.950119,aganivada,{'aganivada'},1,The discussion thread is about resolving an issue with the report-generator lambda. Aganivada apologizes for not knowing that the report generation private DNS changes were not merged to develop yet. They deployed the report-generator from develop for testing CDKv2. No specific details or references to JIRA or other links are mentioned.,2,[],[],NEUTRAL,[],ON_GOING
|
|
2023-05-15T22:36:22.904919,2023-05-15T22:37:50.359689,ppant,"{'ppant', 'aganivada'}",2,ppant is redeploying the lambda from CDK V2 to fix an issue. aganivada mentions that it should already be CDKv2.,2,"['redeploying the lambda', 'fixing an issue']",['CDKv2'],,[],UNKNOWN
|
|
2023-05-15T04:03:44.957249,2023-05-15T09:38:40.797209,aganivada,"{'aganivada', 'rtaraniganty', 'pjha'}",3,"The team discussed deploying lambda's to int with CDKv2, with most deployments working successfully. There was a minor import issue with coordination building blocks. An issue was found while deploying trigger eventbridge changes, but it was being fixed by PJha. They planned to merge into develop and deploy version 9.11 to stage using v2 code.",7,"[""deploying lambda's"", 'CDKv2', 'successful deployments', 'fixing trigger eventbridge changes', 'merging into develop', 'deploying version 9.11 to stage', 'v2 code']","['minor import issue', 'issue with coordination building blocks']",POSITIVE,[],ON_GOING
|
|
2023-05-09T00:43:55.853069,2023-05-15T02:56:07.209469,nsrivastava,"{'aganivada', 'rtaraniganty', 'nsrivastava', 'hchintamreddy'}",4,"The discussion thread is about the broken links in the Jira integration in GitLab. The issue is that the Jira ID in the merge request description leads to a 404 page. They discuss updating the MR template and the default Web URL in GitLab. They open a case with GitLab and eventually find a solution. The Jira link now works, but it is not retroactive. They also discuss the importance of having a Jira ID in the MR title. The thread ends with a mention of specific merge requests where the Jira integration is working correctly. No specific JIRA ticket or other links are mentioned.",20,"['Updating MR template', 'Updating default Web URL', 'Finding a solution', 'Jira link now works', 'Importance of Jira ID in MR title', 'Jira integration working correctly']","['Broken links in Jira integration', 'Jira ID leads to 404 page', 'Jira link not retroactive']",POSITIVE,['COLL-1430'],RESOLVED_OR_CLOSED
|
|
2023-05-12T03:48:34.387719,2023-05-12T12:58:21.101659,mnirmal,"{'mnirmal', 'rtaraniganty', 'pjha', 'aganivada'}",4,mnirmal asked for the deployment dependencies page for version 0.9.11. aganivada said they will verify. pjha was asked to check if the page exists and add one if it doesn't. pjha confirmed the page exists and shared the link. rtaraniganty thanked pjha.,5,"['deployment dependencies page', 'version 0.9.11']",[],,[],UNKNOWN
|
|
2023-05-10T22:51:48.556359,2023-05-11T03:32:33.550679,gshenoy,"{'aganivada', 'ppant', 'pmangalapuri', 'gshenoy'}",4,"The team is discussing an issue with the tenancy API, which is returning a 403 error. They suspect that the issue may be related to not using a VPN. They also mention that the API is failing when generating reports from Lambda via Puppeteer. They are investigating the token being passed to the dashboard app and suspect an issue with connecting to the vault service.",14,"['discussion of tenancy API issue', 'investigating token for dashboard app']","['403 error with tenancy API', 'API failing when generating reports', 'issue with connecting to vault service']",NEGATIVE,[],UNKNOWN
|
|
2023-05-10T13:09:51.715059,2023-05-10T20:29:30.021509,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"The discussion is about allowing people to connect to RDS instances in an environment after connecting to the VPN. Currently, it is not working. It is suggested to add P81 SG to RDS access as part of VPN CDK changes. The link to the security group is provided.",2,"['connecting to RDS instances', 'VPN CDK changes']","['not working', 'security group']",,[],UNKNOWN
|
|
2023-05-09T11:36:13.837949,2023-05-10T11:49:34.757189,hchintamreddy,"{'aganivada', 'svummidi', 'rtaraniganty', 'hchintamreddy'}",4,"The team is discussing adding a default header to the com.axm.platform.commons.config.WebClientConfig#s2sWebClient to identify the service origin. They agree to prefix the header with ""InternalService-"" and later suggest shortening it to ""axm-"".",6,"['adding default header', 'identify service origin', 'prefix header with InternalService-', 'shorten header to axm-']",[],,[],UNKNOWN
|
|
2023-05-09T11:53:11.433229,2023-05-09T22:41:14.028279,pjha,"{'aganivada', 'pjha'}",2,"The discussion thread is about configuring a Group runner for Axiamatic Main. The steps include getting the registration token, registering the runner on an EC2 instance, enabling untagged jobs, disabling the shared runner, and creating a webhook. The user ""rtaraniganty"" mentions not having permission for steps 1 and 3, but ""aganivada"" offers to help after lunch. No JIRA ticket or other links are mentioned.",3,"['Configuring Group runner', 'Registering runner on EC2 instance', 'Enabling untagged jobs', 'Creating webhook', 'Help from aganivada']",['No permission for steps 1 and 3'],NEUTRAL,[],UNKNOWN
|
|
2023-05-09T22:35:58.568249,2023-05-09T22:37:10.969749,aganivada,"{'aganivada', 'askumar', 'rsrinivasan'}",3,Anil is suffering from a stye and plans to reduce screen-time. He informs the team and expects delayed responses. Raghav and Ashok both advise him to take care and avoid long stretches. No JIRA ticket or other links are mentioned.,3,"['taking care', 'advice']","['suffering from stye', 'reduced screen-time', 'delayed responses']",,[],UNKNOWN
|
|
2023-05-09T16:01:43.692929,2023-05-09T22:30:37.122199,rtaraniganty,"{'aganivada', 'rtaraniganty', 'pjha'}",3,"The discussion thread is about an issue with deploying services using CDKv2. The error message states that the authorizer name must be unique. The team discusses possible reasons for the error, such as changes in CDKv2 and the metadata requirements for authorizers. They make changes to the code and successfully deploy the services. They also discuss the need to deploy all services and core stacks before merging to develop. No specific JIRA ticket or links are mentioned.",60,"['successful deployment', 'code changes', 'core stack deployment']","['error message', 'CDKv2 issues', 'metadata requirements']",,[],RESOLVED_OR_CLOSED
|
|
2023-05-05T10:51:41.999949,2023-05-09T09:23:15.286099,rtaraniganty,"{'askumar', 'rtaraniganty', 'aganivada'}",3,The discussion thread is about switching off unused RDS/Aurora instances in the INT environment to save costs. They also discuss the naming pattern of the Aurora clusters and decide to follow the production naming convention. They mention a test cluster that will be closed soon. They plan to stop unused instances and delete them within the week. They also mention checking with Nayan about the replication postgres instance.,11,"['switching off unused RDS/Aurora instances', 'saving costs', 'following production naming convention', 'stopping unused instances', 'deleting instances within the week']","['test cluster closing soon', 'checking with Nayan about replication postgres instance']",NEUTRAL,[],UNKNOWN
|
|
2023-05-08T17:11:48.496209,2023-05-09T09:04:02.565019,rtaraniganty,"{'ppant', 'rtaraniganty'}",2,"The discussion thread is about an error related to a missing file in the platform_libs_epoch package. The error occurs when trying to access a URL from a service that depends on platform_libs_epoch. They discuss the location of the missing file, potential tweaks needed in another file, and the usage of axm_http. They also discuss the possibility of using a Python dict instead of a JSON file and making the code work from any lambda. The coordination invoker lambda is deployed with the changes and seems to be working fine. A temporary merge request is provided for reference.",17,"['location of missing file', 'coordination invoker lambda working fine']","['error related to missing file', 'potential tweaks needed in another file', 'usage of axm_http', 'using Python dict instead of JSON file', 'making code work from any lambda']",NEUTRAL,[],UNKNOWN
|
|
2023-05-09T08:09:53.173979,2023-05-09T08:15:29.457549,aganivada,"{'aganivada', 'pjha'}",2,"Aganivada informs Pjha that they are deleting tenancy multi-instances deployed in int for now and can revisit it during testing. Aganivada asks Pjha if they want to keep *exp-stack-int-plat-1* for validation, to which Pjha replies to reduce the desired instances to 0.",3,"['deleting tenancy multi-instances', 'revisit during testing', 'keep exp-stack-int-plat-1 for validation']",['reduce desired instances to 0'],,[],UNKNOWN
|
|
2023-05-08T23:39:46.558849,2023-05-09T08:07:14.386089,ppant,"{'ppant', 'aganivada'}",2,"The discussion thread is about a compatibility issue caused by the new version of Python's requests library. The version of boto3 being used is incompatible with urllib3, and the requests library needs to be downgraded to version 2.28.2. The specific dependencies and versions are provided in the thread. The conversation is requested to be posted in the engg channel.",2,"['compatibility issue', ""Python's requests library"", 'downgrade to version 2.28.2']","['incompatible with urllib3', 'version of boto3']",,[],ON_GOING
|
|
2023-05-01T23:03:10.160799,2023-05-08T23:38:59.570349,askumar,"{'askumar', 'rtaraniganty', 'rsrinivasan', 'aganivada'}",4,"The team encountered an issue while migrating data via AWS Data Migration service. They discussed using pg_dump for schema and constraints migration. They also considered manually adding constraints or using the database engine's native tools. Multiple snapshots cannot be migrated to one instance. The team is planning to go ahead with pg_dump, but there are challenges with copying BLOBS in the commons database. Reference: <https://support.console.aws.amazon.com/support/home?region=us-west-2#/case/?displayId=12663141051&language=en>",20,"['pg_dump', 'schema migration', 'constraints migration', 'native tools']","['data migration issue', 'multiple snapshots migration', 'copying BLOBS']",,[],UNKNOWN
|
|
2023-05-08T00:51:38.230219,2023-05-08T00:58:52.321769,sjain,"{'ppant', 'sjain', 'aganivada'}",3,"The discussion thread is about a build failure in the sentiment-collector project. Sjain is experiencing an error while publishing a Docker image, specifically an issue with the --role-arn argument. Ppant suggests marking the branch as protected to resolve the issue. Aganivada confirms that only certain branches have permission to publish and marks the branch as protected. Sjain realizes that the pipeline has changed and now only has two builds. Sjain thanks Aganivada for the assistance.",6,"['build failure', 'protected branch', 'assistance']","['error', 'Docker image', '--role-arn argument', 'pipeline change']",,[],UNKNOWN
|
|
2023-05-05T15:47:18.929839,2023-05-05T20:32:23.310109,anair,"{'anair', 'rsrinivasan'}",2,EA is interested in SSO with Okta. Rsrinivasan confirms that they have prepared for Okta integration. More details can be found in the JIRA ticket <https://pinstripe.atlassian.net/wiki/spaces/PRODUCT/pages/401572225/Okta+Integration>.,2,"['SSO with Okta', 'Okta integration']",[],,[],UNKNOWN
|
|
2023-05-04T22:16:17.157669,2023-05-05T00:25:01.872059,ppant,"{'ppant', 'rtaraniganty', 'aganivada'}",3,"The team has made changes to the openApi generated ApiClient to support reading endpoint configurations for backend support in multiple instance deployment. They are currently using application.yml for the proof of concept (PoC) but plan to move it to SSM. The configurations include basePath mappings for different tenant IDs and services. The request will be routed based on the tenant ID, and if a service name or tenant ID is not present, it will go to the default endpoint. The team also discussed validating the flow with a reactive app and clarified that the port value cannot go beyond 65535. The changes made for the PoC were just for testing purposes. The team has tested the flow with the onboarding app by explicitly setting the tenant IDs in the thread context and it seems to work fine.",7,"['changes to ApiClient', 'support for multiple instance deployment', 'reading endpoint configurations', 'using application.yml for PoC', 'moving to SSM', 'basePath mappings for different tenant IDs and services', 'routing based on tenant ID', 'validating flow with reactive app', 'port value limitation', 'testing with onboarding app', 'working fine with explicit tenant IDs']",['changes made for PoC'],POSITIVE,[],UNKNOWN
|
|
2023-05-03T13:56:23.857809,2023-05-04T21:12:33.222189,rtaraniganty,"{'aganivada', 'rtaraniganty', 'mnirmal'}",3,"The team has finished the release of version 0.9.10 and created a hotfix (HF) branch for future deployments. Mohith committed to the wrong branch, so he was asked to move his code to the HF branch. Once that is done, the release branch will be deleted. The team also published tags for version 0.9.10 in the cdk-artifacts project as a backup.",9,"['Finished release of version 0.9.10', 'Created hotfix branch for future deployments', 'Published tags for version 0.9.10 in cdk-artifacts project']","['Mohith committed to the wrong branch', 'Code needs to be moved to the HF branch', 'Release branch needs to be deleted']",NEUTRAL,[],UNKNOWN
|
|
2023-05-03T12:40:21.777179,2023-05-04T04:55:49.855949,rtaraniganty,"{'rtaraniganty', 'rsrinivasan'}",2,The discussion thread mentions that the current platform sprint is the 100th one. The team members express their excitement about this milestone. No other specific details or references are provided.,2,"['100th platform sprint', 'excitement']",[],,[],UNKNOWN
|
|
2023-05-04T02:22:59.672009,2023-05-04T04:26:18.978129,ppant,"{'ppant', 'rsrinivasan', 'aganivada'}",3,"The team is discussing an issue with OpenApi's ApiClient not picking up a bean from plat-commons. They have created a Spring component called AxmApiClient to customize the API Client and route requests based on the tenant ID. The problem is that AxmApiClient is coming as null in ApiClient. They tried using @Autowired for injection but it resulted in null, so they switched to constructor injection and it worked. The discussion can be found in the following links: tenancy and plat-libs-commons.",8,"['Spring component', 'Constructor injection']","[""OpenApi's ApiClient"", 'AxmApiClient', '@Autowired']",,[],UNKNOWN
|
|
2023-05-04T03:55:49.854329,2023-05-04T04:24:31.695419,aganivada,"{'aganivada', 'askumar'}",2,aganivada alerted the team about a spike in logging. askumar found a warning log in production related to a throttled GetRecords request. aganivada suspected that the stream may be overloaded and will investigate. askumar mentioned that some services have debug level logs in INT. aganivada realized it was a false alarm and will add an alert for the kinesis throttling issue.,8,"['alerted the team', 'found a warning log', 'investigate', 'debug level logs', 'add an alert']","['spike in logging', 'throttled GetRecords request', 'stream overloaded', 'false alarm', 'kinesis throttling issue']",,[],UNKNOWN
|
|
2023-04-26T04:19:05.086169,2023-05-03T06:23:44.795749,aganivada,"{'aganivada', 'rtaraniganty'}",2,There is an issue with the private DNS resolution in perimeter 81 for the integration and stage environments. The perimeter 81 team suggested making changes to the route53 resolver or having separate networks in perimeter 81. They attempted to share the route53 resolver but it didn't work. They are considering setting up VPC peering between integration and stage. The cost of a new gateway for stage is $50 per month. They are currently leaning towards the peering approach and may consider adding a gateway later. They also shared a how-to article on DNS configuration with perimeter 81 private DNS.,9,"['suggested changes to route53 resolver', 'considering VPC peering', 'how-to article on DNS configuration']","['issue with private DNS resolution', 'attempted shared route53 resolver', 'cost of new gateway']",NEUTRAL,[],ON_GOING
|
|
2023-05-02T22:06:33.068739,2023-05-03T02:55:19.435209,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,Today is araman's 1-year anniversary at Axiamatic. rtaraniganty congratulates araman and mentions @plat and @systest. aganivada also congratulates araman.,2,"['anniversary', 'congratulations']",[],,[],UNKNOWN
|
|
2023-05-02T09:22:24.602179,2023-05-03T00:01:20.026789,aganivada,"{'aganivada', 'askumar'}",2,The discussion thread is about the planning sheet for version 0.9.11. The team is targeting to close the tasks marked in bold in sprint 3. Askumar and pjha are requested to update tasks related to the database. Askumar has updated tasks related to exploring pg_dump approach for data replication and using CDK to populate cluster name and variables for all services.,3,"['planning sheet', 'closing tasks', 'updating tasks', 'exploring pg_dump approach', 'using CDK', 'populating cluster name', 'populating variables']",['none'],POSITIVE,[],UNKNOWN
|
|
2023-05-02T09:37:21.298179,2023-05-02T22:32:26.340579,pjha,"{'rtaraniganty', 'pjha'}",2,The discussion thread is about the issue faced by pjha in creating an RDS Aurora Serverless_v2 instance using CDK_v2. They are unable to create read instances using CDK and have referred to a GitHub issue (https://github.com/aws/aws-cdk/issues/20197) for more information.,5,[],"['issue faced', 'unable to create read instances', 'CDK issue']",,[],UNKNOWN
|
|
2023-04-20T02:30:20.298699,2023-05-01T22:12:25.258309,ppant,"{'ppant', 'svummidi', 'rsrinivasan', 'rtaraniganty'}",4,"The team is discussing the origin and customization of the ""ApiClient.mustache"" file. It is mentioned that the file is generated from the OpenAPI tools project and can be customized by modifying the base template. The file will reside in the core-libs-data-commons and its dependency will be added to the projects' specification.xml. The discussion also mentions a JIRA ticket: <https://pinstripe.atlassian.net/l/cp/xAmCHwxT>.",7,"['discussion of origin and customization of ApiClient.mustache file', 'file generated from OpenAPI tools project', 'file can be customized by modifying base template', 'file will reside in core-libs-data-commons', ""dependency added to projects' specification.xml""]",['no negative topics mentioned'],NEUTRAL,[],UNKNOWN
|
|
2023-04-26T20:31:11.384239,2023-04-26T20:47:43.800449,rsrinivasan,"{'aganivada', 'svummidi', 'rsrinivasan'}",3,"Svummidi suggests deploying version 0.0.9.2 of the estimation service to stage, including a fix for the time line view. Aganivada agrees and confirms that they will deploy this version. No JIRA ticket or other links are mentioned.",3,"['deploy version 0.0.9.2', 'fix for time line view']",[],,[],UNKNOWN
|
|
2023-04-26T17:41:11.572599,2023-04-26T20:47:08.249839,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,The discussion is about the cost of using GitLab's shared runners and the possibility of using a personal runner instead. They need to move 6000 minutes of workload to justify the cost of their own runner. They plan to disable the shared runner after completing the 0.9.10 validation and attempt a proof of concept for turning on the GL-runner on-demand. No specific JIRA ticket or other links are mentioned.,2,"['personal runner', 'GL-runner on-demand']",['cost of shared runners'],NEUTRAL,[],UNKNOWN
|
|
2023-04-26T00:52:07.270939,2023-04-26T20:34:55.243259,bganganna,"{'svummidi', 'bganganna'}",2,"The discussion thread is about documenting the steps for reprocessing open text comments in production to populate the date. Svummidi has a draft that will be updated and published. Bganganna asks if there is a release recipe document to follow, and Svummidi explains the usual pattern of covering with a feature flag and updating tenant-specific comments. The activity is planned as a post-release activity. Reference: <https://pinstripe.atlassian.net/l/cp/uiDGXSrS>",5,"['documenting steps', 'reprocessing open text comments', 'updating and publishing draft', 'usual pattern of covering with a feature flag', 'updating tenant-specific comments', 'post-release activity']",['lack of release recipe document'],NEUTRAL,[],UNKNOWN
|
|
2023-04-25T05:16:24.011519,2023-04-26T11:07:36.567849,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion is about reviewing the document on querying CloudFront logs from an S3 bucket in Athena. Aganivada suggests creating Athena tables in all three environments and linking them to the bucket. Pjha mentions that the Int and Stage environments are already done and will create in production once changes are deployed. Rtaraniganty asks if the provisioning was done via CDK and points out a spelling issue in the DB name that needs to be fixed.,4,"['reviewing document', 'creating Athena tables', 'linking tables to bucket']",['spelling issue in DB name'],,[],UNKNOWN
|
|
2023-04-25T23:24:27.147919,2023-04-26T00:02:13.773329,aganivada,"{'aganivada', 'pmangalapuri'}",2,Aganivada updated the deployment dependency template to include i18nexus migration for future prod deployments. Pmangalapuri thanked Aganivada.,2,"['deployment dependency template', 'i18nexus migration', 'prod deployments']",[],,[],UNKNOWN
|
|
2023-04-24T22:25:18.581139,2023-04-25T00:06:03.245179,pjha,"{'aganivada', 'pjha'}",2,The discussion is about merging a change and deploying the tenancy. Pjha suggests deleting and deploying the tenancy due to a change in the service-id. Aganivada asks if they can try deploying the tenancy instead of destroying it. Pjha explains that the change in the service-id requires deletion. They also discuss creating a merge request for 'issue/shortning_service_id' to 'release/0.9.10' and agree to merge it to develop and main. No JIRA ticket or other links are mentioned.,9,"['merging change', 'deploying tenancy', 'creating merge request', 'merging to develop and main']","['deleting tenancy', 'change in service-id']",,[],UNKNOWN
|
|
2023-04-24T04:36:26.585829,2023-04-24T21:28:01.498779,aganivada,"{'aganivada', 'rtaraniganty'}",2,The discussion was about migrating the current RDS instances to Aurora Serverless v2 in integration. They considered two options: migrating all instances to Aurora or migrating only core and discovery. They discussed the cost difference and the possibility of using a proxy. They decided to use Aurora for all instances in both integration and stage environments. No specific JIRA ticket or other links were mentioned.,6,"['migrating to Aurora Serverless v2', 'using Aurora for all instances', 'using Aurora in integration and stage environments']","['cost difference', 'using a proxy']",POSITIVE,[],RESOLVED_OR_CLOSED
|
|
2023-04-24T08:32:48.511449,2023-04-24T20:53:40.456489,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion thread is about deploying the slack-integrator-service with route53 mapping to a load balancer DNS. There is an error related to the length of the InstanceId being more than 64 characters. The team suggests abbreviating the instanceid and shortening the service_id. They plan to submit a merge request to release/0.9.10 and track the service_id change separately.,29,"['deploying slack-integrator-service', 'route53 mapping', 'load balancer DNS', 'abbreviating InstanceId', 'shortening service_id', 'submitting merge request', 'tracking service_id change']",['error related to InstanceId length'],POSITIVE,[],UNKNOWN
|
|
2023-04-18T21:08:54.429929,2023-04-24T19:35:37.164139,aganivada,"{'aganivada', 'anair', 'rvaidya'}",3,"The discussion is about renaming user roles in accordance with PLAT-1876. The proposed changes are to rename Product Admin and Account Admin as ""Local Admin."" There is a suggestion to differentiate Product Admin from Account Admin, but it is unclear if this will be implemented. A migration script will be run to update existing admins and invitations.",3,"['renaming user roles', 'Local Admin', 'migration script']",['unclear implementation'],,['PLAT-1876'],UNKNOWN
|
|
2023-04-12T11:45:32.393469,2023-04-24T10:16:31.951749,akalyta,"{'akalyta', 'svummidi', 'psomasamudram563'}",3,"The discussion thread is about parsing G2 products data. Akalyta suggests making changes to the parsed files, such as uploading them in .csv format, naming the files in lowercase with dashes, and using G2 field names. Psomasamudram563 uploads CSV files to the rawdata folder, and svummidi mentions the possibility of automating the creation of product instance IDs.",13,"['changes to parsed files', 'uploading files in .csv format', 'naming files in lowercase with dashes', 'using G2 field names', 'automating creation of product instance IDs']",[],POSITIVE,[],UNKNOWN
|
|
2023-04-17T21:00:29.403909,2023-04-24T07:17:12.935869,aganivada,"{'aganivada', 'svummidi', 'akalyta'}",3,"The team is discussing increasing their quota for openAI. Aganivada submits a request to increase the quota to $200, with a hard limit of $150 to be safe. Svummidi thanks Aganivada for adding credentials to 1Password.",9,"['increasing quota', 'adding credentials to 1Password']",[],POSITIVE,[],UNKNOWN
|
|
2023-04-23T23:05:18.065599,2023-04-23T23:27:43.490469,akalyta,"{'akalyta', 'aganivada'}",2,Akalyta asks Aganivada to raise the hard limit for OpenAI from $139 to $180 to avoid interruptions. Aganivada agrees and updates the limit. They also request to raise the account limit to $250 for even higher usage if necessary. No JIRA ticket or other links are mentioned.,4,"['raise hard limit to $180', 'avoid interruptions', 'raise account limit to $250']",[],,[],UNKNOWN
|
|
2023-04-23T20:58:05.484719,2023-04-23T21:21:16.959919,aganivada,"{'aganivada', 'bganganna'}",2,"During the regression cycle, aganivada asks bganganna if they can run the tests identified for permissions validation during 0.9.9-hf. They mention that they made some changes to RBAC to enable reporting on the vendor side. Bganganna asks if they need to test from the customer side as well, but aganivada suggests covering both scenarios if there is time, as the collaborators flow is important in the context of the RBAC change on either side. No references to JIRA tickets or other links are mentioned.",3,"['RBAC changes', 'vendor reporting', 'collaborators flow']",[],,[],UNKNOWN
|
|
2023-04-19T21:23:25.549509,2023-04-19T21:23:51.163559,rsrinivasan,"{'aganivada', 'rsrinivasan'}",2,rsrinivasan informs aganivada that his son is unwell and he needs to take him to the hospital. He mentions that he will connect in the evening. aganivada responds by telling rsrinivasan to take care. No JIRA ticket or other links are mentioned.,2,[],[],NEUTRAL,[],ON_GOING
|
|
2023-04-19T08:18:42.888679,2023-04-19T09:25:45.302549,askumar,{'askumar'},1,"The discussion thread is about testing data migration for the core-stack in INT. The user, askumar, notifies the team that responses for API calls might be delayed during the testing. Later, askumar updates that the testing is done. No other specific details or references are mentioned.",2,[],[],NEUTRAL,[],RESOLVED_OR_CLOSED
|
|
2023-04-19T05:47:01.968619,2023-04-19T06:42:59.350359,askumar,"{'askumar', 'rsrinivasan'}",2,"The discussion thread is about the initial schema design for storing event information in Snowflake. The main table is tightly coupled with pulse-related events, and there is support for JSON in Snowflake. The alternate base table has been added to Snowflake and the documentation has been updated. No specific details or references to JIRA tickets or other links are mentioned.",4,"['Initial schema design', 'Support for JSON in Snowflake', 'Alternate base table added', 'Documentation updated']",['Tightly coupled main table'],NEUTRAL,[],ON_GOING
|
|
2023-04-03T03:15:47.597929,2023-04-18T02:46:32.137459,rsrinivasan,"{'aganivada', 'rsrinivasan'}",2,"The discussion thread is about modifying the API client moustache in the openapi-generator project. Rsrinivasan shared a sample for the modification, and aganivada mentioned ppant in the conversation. The details can be found at <https://github.com/OpenAPITools/openapi-generator/pull/6036/files#diff-61b6ebf1535b93a154d615707eb8f1139bdce63b4d989ca998608d42f3d49ae4>.",2,"['API client modification', 'OpenAPI Generator project']",[],,[],UNKNOWN
|
|
2023-04-17T23:34:29.540539,2023-04-17T23:51:58.361669,nsrivastava,"{'aganivada', 'nsrivastava'}",2,The discussion thread is about a missing `docker` error in a pipeline. It is mentioned that the error is due to GL runner changes not being merged to the develop branch. The pipeline is redirected to a regular shared runner and it is mentioned that the GL-runner changes will be merged once all test-related issues are resolved. The job is successful after the changes.,6,"['docker error', 'pipeline redirection', 'successful job']","['GL runner changes not merged', 'test-related issues']",,[],UNKNOWN
|
|
2023-04-13T18:25:34.634889,2023-04-13T23:14:36.658099,ppant,"{'ppant', 'hchintamreddy', 'aganivada'}",3,"During the discussion, it was discovered that the `sqs-lambda-listener` parameter from SSM is being used in all app stacks due to the `apply_sqs_lambda_defaults_from_context` method in the `BaseAppStack`. It was also mentioned that only the `message-broker` service depends on the `message-broker-sqs-lambda` parameter. Further investigation is needed to determine if any other services rely on this parameter.",6,"['sqs-lambda-listener', 'SSM', 'BaseAppStack', 'apply_sqs_lambda_defaults_from_context', 'message-broker', 'message-broker-sqs-lambda']","['investigation', 'other services']",NEUTRAL,[],UNKNOWN
|
|
2023-04-12T17:41:50.959149,2023-04-12T22:51:50.119929,rtaraniganty,"{'svummidi', 'aganivada', 'rsrinivasan', 'ppant', 'rtaraniganty', 'akasim'}",6,"The team is discussing options for building product metrics dashboards using Retool. They consider building an admin app middleware service in reactive Java, a Python admin service, a set of lambdas, or a non-reactive Java service. They discuss the pros and cons of each option and consider factors such as stack consistency, performance, ease of development, and data access. They also mention the possibility of using GraphQL and connecting to Salesforce. The team leans towards option #2 (Python) or #4 (non-reactive Java) due to their lighter weight compared to Java. They also discuss the use of Retool for connecting to data sources and the need for some middleware to handle complex data retrieval.",15,"['Retool', 'Python', 'non-reactive Java', 'lightweight']","['reactive Java', 'lambdas', 'complex data retrieval']",,[],UNKNOWN
|
|
2023-04-12T08:51:44.421059,2023-04-12T22:09:53.007579,rvaidya,"{'rvaidya', 'rsrinivasan', 'aganivada', 'rtaraniganty', 'ppant'}",5,"The team discussed an error in the vendorapp in the INT environment related to AWS Kinesis permissions. They found that the ECS IAM role had the necessary permissions, but the Kinesis stream name did not start with ""int-"". They also discussed the configuration files and made changes to resolve the issue. The problem was resolved when the *-int.yaml files were removed from the dev config.",20,"['error resolution', 'configuration changes']","['AWS Kinesis permissions', 'ECS IAM role', 'Kinesis stream name']",,[],UNKNOWN
|
|
2023-04-06T09:14:29.930769,2023-04-12T21:23:37.190539,rsrinivasan,"{'aganivada', 'rtaraniganty', 'rsrinivasan', 'gshenoy'}",4,"The discussion thread involves rsrinivasan, aganivada, rtaraniganty, and gshenoy. They discuss projects they have worked on and the need to fix the build process. They mention specific projects like vms-estimation-service and platform-services-notification. They also mention issues with code coverage badges and console output.",6,"['projects worked on', 'vms-estimation-service', 'platform-services-notification']","['fix build process', 'code coverage badges', 'console output']",,[],UNKNOWN
|
|
2023-04-12T09:38:59.108249,2023-04-12T21:21:06.825409,askumar,"{'askumar', 'aganivada'}",2,"The discussion thread is about deciding on the approach for data enrichment of snowflake data, specifically creating a map of TenantId to Name and UserId to Name. Two approaches are suggested: 1) Lambda enriching the event by making a call to the backend, and 2) Snowflake having a table with key value maps, either pushed by a different Lambda or by taking a dump from the database. The question is raised if the same Lambda can be used for pushing tenant and user creation events.",3,"['Data enrichment', 'Lambda enriching event', 'Backend call', 'Snowflake table with key value maps', 'Pushing tenant and user creation events']",['No negative topics'],NEUTRAL,[],UNKNOWN
|
|
2023-04-12T16:19:51.089739,2023-04-12T21:20:13.795709,rtaraniganty,"{'aganivada', 'rtaraniganty', 'askumar'}",3,The team plans to write a script to generate various events and feed them into Snowflake. They will then connect it with Retool to build the required charts. They also discuss using Grafana to publish events and mention using Snowflake's UI to insert data. No specific JIRA ticket or links are mentioned.,4,"['script to generate events', 'connecting with Retool', 'building charts', ""using Snowflake's UI to insert data""]",['no specific JIRA ticket or links mentioned'],NEUTRAL,[],UNKNOWN
|
|
2023-04-11T20:03:25.858639,2023-04-12T10:45:34.606609,rtaraniganty,"{'askumar', 'rtaraniganty', 'aganivada'}",3,"The team is discussing options for building product metrics dashboards. They are considering using admin APIs to fetch data, pushing metrics to Snowflake, and using Retool for basic views. They are also discussing the number of tables to define in Snowflake and the possibility of using a ""union"" schema. They mention the need for joins in some cases and the idea of leaving user and tenant data as ids in Snowflake tables. No specific JIRA ticket or link is mentioned.",15,"['Options for building product metrics dashboards', 'Using admin APIs to fetch data', 'Pushing metrics to Snowflake', 'Using Retool for basic views', 'Defining tables in Snowflake', ""Using a 'union' schema"", 'Joining tables in Snowflake', 'Leaving user and tenant data as ids in Snowflake tables']",[],,[],UNKNOWN
|
|
2023-04-12T08:58:26.697039,2023-04-12T10:07:15.128419,aganivada,"{'aganivada', 'ppant'}",2,"The discussion thread is about a transactional issue faced by ppant with tenancy's tenant rollback due to a duplicate name. Aganivada suggests splitting to a helper class and using annotations on the helper to fix the issue. However, ppant mentions running into a refactoring problem with a delegate service. Aganivada suggests asking askumar for further assistance.",5,"['splitting to a helper class', 'using annotations']","['duplicate name', 'refactoring problem', 'delegate service']",NEUTRAL,[],UNKNOWN
|
|
2023-04-05T04:45:20.610419,2023-04-12T08:38:37.411319,araman,"{'aganivada', 'araman', 'anair', 'rtaraniganty'}",4,"The discussion thread is about resolving issues related to the audit log in the production environment. They discuss cleaning up old entries, resolving a failed test, and releasing lambda functions. They also mention the need for versioning and including branch names in package names. The issue of empty section records and the presence of a system user are also mentioned. The JIRA ticket mentioned is PLAT-1887.",18,"['cleaning up old entries', 'resolving a failed test', 'releasing lambda functions', 'versioning', 'including branch names in package names']","['empty section records', 'presence of a system user']",NEUTRAL,"['PLAT-1887', 'PLAT-1887']",UNKNOWN
|
|
2023-04-11T23:29:21.862829,2023-04-11T23:34:51.262459,araman,"{'aganivada', 'araman'}",2,Araman informs Aganivada that he will not be able to attend the sprint retro. The sprint will be closed and new tasks will be added to the backlog. The focus for the next 2 days will be on 0.9.9 HF for systest. They will pick up 0.9.10 items for test planning in the next sprint.,2,"['sprint retro', 'new tasks', '0.9.9 HF for systest', '0.9.10 items', 'test planning']",['not able to attend'],,[],UNKNOWN
|
|
2023-04-11T12:42:16.026399,2023-04-11T22:36:20.008569,aganivada,"{'aganivada', 'anair', 'rsrinivasan'}",3,"The discussion is about exploring the option of using Auth0's auto membership configuration for automatic membership in a group. Users will be added to the organization when they log in, but they may see an error page until assigned a role by the orgadmin. It is suggested to assign a default role to users based on configuration. Anair suggests assigning everyone as org admin for now, which can be easily done from Auth0. Mathew.Archuleta@Sands.com is assigned the orgadmin role, and it is mentioned that deleting invitations should not cause any issues since his role is already orgadmin. No references to JIRA ticket or other links are provided.",8,"[""Exploring option of using Auth0's auto membership configuration"", 'Users added to organization when they log in', 'Assigning default role to users based on configuration', 'Assigning everyone as org admin for now', 'Assigning orgadmin role to Mathew.Archuleta@Sands.com', 'Deleting invitations should not cause any issues']",['Users may see an error page until assigned a role by orgadmin'],NEUTRAL,[],ON_GOING
|
|
2023-04-11T02:47:45.460379,2023-04-11T20:33:57.409389,aganivada,"{'aganivada', 'ppant'}",2,The discussion thread is about a potential small fix needed for a JIRA ticket (PLAT-1878) regarding case sensitivity in the `/publisher/all/{tenantId}` API. The suggestion is to add `equalsIgnoreCase` check as part of refactoring and convert the domain to lowercase before passing it to the core. There is also a mention of using RSQL ignorecase or the like operator. No conversion to lowercase is currently done when storing. Reference: <https://pinstripe.atlassian.net/browse/PLAT-1878>,7,"['potential small fix', 'JIRA ticket PLAT-1878', 'case sensitivity', 'refactoring', 'equalsIgnoreCase check', 'convert domain to lowercase', 'RSQL ignorecase', 'like operator']",['no conversion to lowercase when storing'],NEUTRAL,['PLAT-1878'],UNKNOWN
|
|
2023-04-11T10:26:56.534809,2023-04-11T10:28:14.164499,aganivada,{'aganivada'},1,The discussion is about updating and deploying lambdas to the integration environment. The suggestion is to request individual teams for sanity checks. No specific details or references are provided.,2,"['Updating and deploying lambdas', 'Requesting individual teams for sanity checks']",[],,[],UNKNOWN
|
|
2023-04-11T10:19:06.774449,2023-04-11T10:22:16.463319,aganivada,"{'aganivada', 'mnirmal'}",2,aganivada asked mnirmal to share the collab ticket for pulse metrics. mnirmal provided the link <https://pinstripe.atlassian.net/browse/COLL-2197>. aganivada thanked mnirmal and cc'ed rtaraniganty to add pulse metrics to the ticket.,3,"['collab ticket', 'pulse metrics']",[],,['COLL-2197'],UNKNOWN
|
|
2023-04-10T21:19:45.522409,2023-04-11T09:43:49.177639,aganivada,"{'aganivada', 'rsrinivasan'}",2,The discussion thread is about enabling Single Sign-On (SSO) as the default for Haleon. Aganivada asks rsrinivasan to turn on SSO and reminds him to enable it for lvsands as well. Aganivada also adds the discussion to the tracking steps. A link to the Slack conversation is provided.,5,"['Single Sign-On (SSO)', 'enable SSO', 'tracking steps']",[],,[],UNKNOWN
|
|
2023-04-09T23:34:21.234639,2023-04-10T00:06:49.182019,ppant,"{'ppant', 'aganivada'}",2,ppant created a document in January for refactoring Tenancy. They will use it to track all refactoring tasks and notes. aganivada will refactor usersapiservicedelegate and VendorApiServiceDelegate.,2,"['refactoring Tenancy', 'tracking refactoring tasks', 'notes']","['usersapiservicedelegate', 'VendorApiServiceDelegate']",,[],UNKNOWN
|
|
2023-04-06T19:51:54.112049,2023-04-06T22:33:27.765819,rtaraniganty,"{'svummidi', 'rtaraniganty', 'anair', 'aganivada'}",4,The discussion thread is about onboarding everyone to Drata. rtaraniganty sent an email inviting svummidi and aganivada to install the Drata agent and complete the first round of assessment. svummidi suggests creating an Apple ID with a company email account for FileVault. The process took around 15-20 minutes for aganivada and 10 minutes for anair. anair mentions completing all steps except the background check.,12,"['onboarding', 'Drata agent installation', 'assessment completion']",['background check'],,[],UNKNOWN
|
|
2023-04-06T01:40:23.709189,2023-04-06T07:29:05.395059,askumar,"{'askumar', 'rsrinivasan'}",2,The discussion thread is about integrating and testing Aurora. Askumar provides a reference document for Aurora integration and testing and invites others to add comments or questions. Rsrinivasan shares a link with his questions comparing their own approach with a library. He also shares a link on how to use the library.,3,"['Aurora integration', 'Aurora testing']",[],,[],UNKNOWN
|
|
2023-04-06T03:39:59.194859,2023-04-06T05:11:32.565209,askumar,"{'askumar', 'aganivada'}",2,"The discussion thread is about a demo for AWS Aurora Read Write DB. Askumar shares a video link for the demo and Aganivada thanks him. Askumar agrees to provide a voiceover for the demo, including details about write operations on read-only methods, application.yml changes, and local config with only one type of instance. No JIRA ticket or other links are mentioned.",3,"['AWS Aurora Read Write DB', 'video link', 'voiceover', 'write operations on read-only methods', 'application.yml changes', 'local config with one type of instance']",[],,[],UNKNOWN
|
|
2023-04-05T21:31:59.784839,2023-04-06T05:10:45.560209,aganivada,{'aganivada'},1,"aganivada scheduled a sync-up between ppant and rsrinivasan to run the SSO migration script in production. They plan to cover the setup and migration today or split it between today and Monday. The goal is to replicate the tenant similar to lvsands, including roles and permissions. ppant updated the code to skip non-existing users and is waiting for rsrinivasan to be available to continue.",2,"['scheduled sync-up', 'SSO migration script', 'cover setup and migration', 'replicate tenant', 'include roles and permissions', 'updated code to skip non-existing users']",['waiting for rsrinivasan to be available'],POSITIVE,[],ON_GOING
|
|
2023-04-05T17:14:43.605709,2023-04-05T21:28:02.689089,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"rtaraniganty mentions that whenever they log in to LD, they receive a notice to upgrade their SDK as it is reaching EOL. They plan to do this in the next couple of sprints due to non-trivial changes. aganivada acknowledges this and adds a JIRA ticket <https://pinstripe.atlassian.net/browse/PLAT-1908> for the upgrade.",2,[],[],NEUTRAL,['PLAT-1908'],UNKNOWN
|
|
2023-03-30T23:32:53.213369,2023-04-05T04:33:36.005759,pjha,"{'aganivada', 'pjha'}",2,"The discussion thread is about a deployment issue with a tenancy and Route53 target as an ALB endpoint. The error ""service already exists"" is encountered, and the team considers options like modifying the service name or using a different AWS account. Ultimately, it is decided to destroy and deploy the service again, which resolves the issue. No specific JIRA ticket or links are mentioned.",16,"['deployment issue', 'ALB endpoint', 'destroy and deploy']","['service already exists', 'modifying service name', 'using different AWS account']",,[],UNKNOWN
|
|
2023-04-04T18:06:07.358329,2023-04-04T21:19:02.244039,rtaraniganty,"{'aganivada', 'rtaraniganty', 'ppant'}",3,"The team is discussing an issue with log4j XML not being reloaded from cloud config, requiring them to bounce the service. They plan to fix this by integrating all collab services with cloud config and creating JIRA tickets for the same. Only message broker, sentiment collector, and slack integrator currently have cloud-config-bus.",5,"['integrating collab services with cloud config', 'creating JIRA tickets']","['issue with log4j XML not being reloaded', 'requiring service bounce']",NEUTRAL,[],UNKNOWN
|
|
2023-04-04T10:48:27.496229,2023-04-04T11:13:17.123929,aganivada,"{'aganivada', 'bganganna'}",2,"Aganivada asks Bganganna if they can deploy tenancy HF on stage to verify the invitation issue. Bganganna agrees. Aganivada thanks Bhavana and plans to deploy the fix to stage tomorrow, run tests, and provide an update. No specific details or references are mentioned.",3,"['deployment', 'tenancy HF', 'verification', 'invitation issue', 'fix', 'tests', 'update']",[],,[],UNKNOWN
|
|
2023-04-04T06:35:25.207649,2023-04-04T07:34:34.588889,rsrinivasan,"{'aganivada', 'rsrinivasan', 'bganganna'}",3,"rsrinivasan enabled the soft delete feature flag for tenants 8677, 12944, and 14037. They verified that EA loading and the test tenant were working fine. However, there was a 404 error on the pulse manager, which was not related to the feature flag on scoring. The error was due to no pulses found for a specific product instance. bganganna asked if rsrinivasan had excluded any instances when enabling the flag. They also mentioned that they were seeing some errors from the pulse manager and were checking with mnirmal and snangia. rsrinivasan mentioned that for tenant 8677, they had excluded pulse instances 6394, 8669, and 8668.",7,"['soft delete feature flag enabled', 'EA loading and test tenant working fine']","['404 error on pulse manager', 'no pulses found for specific product instance', 'excluded pulse instances']",NEUTRAL,[],UNKNOWN
|
|
2023-04-03T21:08:25.085279,2023-04-04T07:29:28.482589,aganivada,"{'aganivada', 'ppant'}",2,Aganivada plans to spend 2-3 days in the next sprint on refactoring tenancy due to the code and formatting becoming unmanageable. Ppant offers to help as they have finished lambda coding and are available for the task. Aganivada thanks Ppant for the offer.,3,['refactoring tenancy'],['code and formatting becoming unmanageable'],POSITIVE,[],UNKNOWN
|
|
2023-04-03T10:17:14.836589,2023-04-04T03:13:34.932379,aganivada,"{'aganivada', 'rsrinivasan', 'rvaidya', 'bganganna'}",4,"The discussion thread is about a bug that was uncovered in the flow where a vendor invites a customer. It is discovered that when empty permissions are sent, the usermetadata is set as an empty array instead of not sending it at all. This is considered a regression after changes were made for invite with permissions during the collaborators flow. A request is made to raise an Auth0 ticket for the lack of audit log when user metadata is updated via invitation for an existing user.",14,"['Bug uncovered in vendor invitation flow', 'Request to raise Auth0 ticket for lack of audit log']","['Regression after changes for invite with permissions', 'Usermetadata set as empty array instead of not sending it']",NEGATIVE,[],UNKNOWN
|
|
2023-04-02T20:53:07.220499,2023-04-03T21:12:30.367229,aganivada,"{'aganivada', 'rtaraniganty', 'rsrinivasan'}",3,The discussion thread is about the Haleon SSO setup and the use of SignatureMethod and DigestMethod in the SAML response. There is a concern about the algorithm chosen for calculating the digest and a mismatch in the certificate thumbprint. It is suggested to validate the configuration with the customer. The error log in Auth0 indicates an invalid thumbprint. Reference: [Auth0 Error Log](https://manage.auth0.com/dashboard/us/dev-x9m-rker/logs/90020230331102354424074000000000000001223372038775325410?page=1),5,"['Haleon SSO setup', 'use of SignatureMethod', 'use of DigestMethod']","['algorithm chosen for calculating the digest', 'mismatch in certificate thumbprint']",NEGATIVE,[],UNKNOWN
|
|
2023-04-03T09:09:33.801539,2023-04-03T16:30:39.145419,aganivada,"{'aganivada', 'anair'}",2,The team had a call with Pavan (Haleon) and resolved the issue with the invitation flow. They requested Anair to trigger the invitation flow for three users from Pavan's team. Pavan also suggested syncing updated usernames in Teammates and displaying email in the collaborators page. Anair acknowledged both requests. No JIRA ticket or other links were mentioned.,3,"['resolved issue with invitation flow', 'triggered invitation flow for three users', 'acknowledged requests']",[],POSITIVE,[],UNKNOWN
|
|
2023-03-28T11:44:46.585659,2023-04-03T08:21:02.554599,rtaraniganty,"{'rtaraniganty', 'pjha'}",2,"The discussion is about setting up a process to build and deploy Docker images using ECR in INT. Two approaches are discussed: creating an ECR repo and pushing the image before deployment, or providing the Dockerfile path to the CDK code. The first approach is favored, and there is a script to clean up old images. No specific JIRA ticket or links are mentioned.",8,"['Setting up process to build and deploy Docker images using ECR in INT', 'Creating an ECR repo and pushing the image before deployment', 'Script to clean up old images']",['Providing Dockerfile path to CDK code'],POSITIVE,[],ON_GOING
|
|
2023-03-28T20:12:25.503019,2023-04-02T23:18:22.362409,rtaraniganty,"{'pmangalapuri', 'gshenoy', 'rsrinivasan', 'aganivada', 'rtaraniganty'}",5,"The team discusses changes made to the production ES cluster, specifically the reduction in node count from 7 to 4. They consider turning off the *oses-plat-evtmgmt-production* cluster to save costs and discuss archiving events in S3 instead of using Elasticsearch. They plan to set up expiration policies for the archived events and consider using CDK for this implementation. A JIRA ticket, DISC-2728, is created to remove the dependency on the *oses-plat-evtmgmt-production* cluster.",25,"['reduction in node count', 'turning off *oses-plat-evtmgmt-production* cluster', 'archiving events in S3', 'setting up expiration policies for archived events', 'using CDK for implementation']",['dependency on *oses-plat-evtmgmt-production* cluster'],POSITIVE,"['DISC-2728', 'DISC-2728']",UNKNOWN
|
|
2023-03-31T11:17:59.473949,2023-04-01T02:36:31.609259,rsrinivasan,"{'aganivada', 'rsrinivasan'}",2,rsrinivasan requested the ability for users to be automatically assigned a group/role in Auth0 and be able to login and view the dashboard without the orgadmin adding them as a collaborator in the UI. aganivada acknowledged the request and mentioned that it doesn't seem straightforward from Auth0's perspective. They agreed to sync up next week and add a platform ticket. [Link to the discussion thread](https://community.auth0.com/t/sync-active-directory-roles-with-auth0-roles/77166),2,"['automatic group/role assignment', 'login and view dashboard']",['not straightforward'],,[],UNKNOWN
|
|
2023-03-30T22:53:49.986749,2023-03-31T10:09:33.053529,ppant,"{'ppant', 'rtaraniganty', 'aganivada'}",3,The team discussed an issue with vulnerability checks failing for the `py==1.11.0` package in Python 3.8 used in Gitlab pipelines. They considered updating the Python version to 3.10.7 but realized that AWS Lambda only supports versions 3.7 to 3.9. They decided to update the versions of various packages that work with the security checks.,15,"['vulnerability checks', 'updating package versions']","['vulnerability checks failing', 'AWS Lambda only supports Python 3.7 to 3.9']",,[],UNKNOWN
|
|
2023-03-30T17:01:00.347599,2023-03-30T17:32:37.465879,rtaraniganty,"{'svummidi', 'rtaraniganty', 'anair'}",3,"There is an exception on the ScoreProvider side for the EA Tenant. The issue is related to EA data re-indexing, causing problems in accessing the UI page. The team is discussing the issue with the Druid support team.",6,"['exception on ScoreProvider side', 'discussing issue with Druid support team']",['EA data re-indexing causing problems in accessing UI page'],,[],UNKNOWN
|
|
2023-03-29T10:49:16.981489,2023-03-29T21:09:25.940159,pjha,"{'aganivada', 'pjha'}",2,"pjha asked aganivada to review a pull request (PR) for replacing the ECS IP with an ALB endpoint in Route53. aganivada suggested testing it with a service in the int environment before merging, to which pjha agreed. No specific details or links were mentioned.",3,"['pull request review', 'replacing ECS IP with ALB endpoint', 'testing in int environment']",[],,[],UNKNOWN
|
|
2023-03-28T15:14:25.863659,2023-03-29T21:08:17.152839,svummidi,"{'avenkataraman', 'svummidi', 'rsrinivasan', 'rtaraniganty', 'anair'}",5,"The discussion thread revolves around the concern of including topics generated from questions in the retro tenant. The team discusses the possibility of excluding these topics to pick popular ones. They also consider the cost of making separate calls to OpenAI for sentiment and topic analysis. The prompt is modified to exclude topics from questions, and the topics are regenerated successfully. The team is satisfied with the results. The prompt used for GPT3.5 can be found at <https://gitlab.com/axiamatic-main/axiamatic-cfg/stage-configs/-/blob/main/config/ingestion/application.yml>. The JIRA ticket related to this issue is tracked at <https://pinstripe.atlassian.net/browse/DAT-939>.",19,"['Excluding topics from questions in retro tenant', 'Regenerating topics successfully', 'Satisfaction with the results']",['Considering the cost of separate calls to OpenAI'],POSITIVE,['DAT-939'],RESOLVED_OR_CLOSED
|
|
2023-03-28T22:48:07.069559,2023-03-28T23:18:51.059979,ppant,"{'ppant', 'aganivada'}",2,ppant asks if `terminal-core-stack` has been removed from base-infra's core. aganivada suggests copying it locally to test and mentions that the file will be automatically added to the develop branch when the release/0.9.9 branch is closed. ppant asks if they should commit it to the develop branch along with changes for sqs lambda.,4,"['terminal-core-stack', ""base-infra's core"", 'copying it locally', 'test', 'release/0.9.9 branch', 'commit', 'develop branch', 'sqs lambda']",[],,[],UNKNOWN
|
|
2023-03-28T08:54:02.813839,2023-03-28T21:21:47.274449,aganivada,"{'aganivada', 'rtaraniganty'}",2,"The discussion thread is about reviewing a VPN overview and planning document. The reviewer provides feedback on the existing and updated architecture, suggesting improvements such as labeling icons and indicating authentication tokens. A question is raised about the security implications of Eventbridge API calls accessing a service. The document will be updated accordingly.",3,"['existing architecture', 'updated architecture', 'labeling icons', 'indicating authentication tokens']",['security implications of Eventbridge API calls'],POSITIVE,[],UNKNOWN
|
|
2023-03-26T20:01:21.225479,2023-03-28T00:53:08.814399,rtaraniganty,"{'rvaidya', 'pkarthikeyan', 'mnirmal', 'araman', 'rtaraniganty', 'mli'}",6,"The discussion thread is about adding a person to a team after sending out a pulse and including them in the pulse. Suggestions are made to edit the config, use a different persona, or use the new API. The issue with the AXM Stage Slack Bot not loading is also mentioned. A link to the logz.io dashboard is provided for further investigation.",14,"['adding a person to a team', 'sending out a pulse', 'including them in the pulse', 'edit the config', 'use a different persona', 'use the new API']",['AXM Stage Slack Bot not loading'],,[],UNKNOWN
|
|
2023-03-26T23:47:51.105509,2023-03-27T22:05:18.379799,pkarthikeyan,"{'askumar', 'svummidi', 'pkarthikeyan', 'aganivada', 'ppant', 'rtaraniganty'}",6,"There were issues with connecting to Perimeter 81 and RDS while using VPN. However, the issues seem to have been resolved and the connection is now working for most users. There was a Perimeter 81 outage yesterday, which may have caused the connectivity problems. There were also some intermittent test failures, which were attributed to changes in the VPN branch that haven't been merged yet.",10,"['connection resolved', 'working for most users']","['issues with connecting to Perimeter 81', 'issues with RDS', 'Perimeter 81 outage', 'intermittent test failures']",,[],UNKNOWN
|
|
2023-03-27T17:48:20.610319,2023-03-27T20:28:03.533539,ppant,"{'ppant', 'aganivada'}",2,ppant fixed an issue but forgot to merge the MR. They merged it now. aganivada asked how often a log is printed and if a HF version should be released for all services using the latest observability. ppant clarified that the log is only printed when the service is started/bounced. aganivada suggested posting an FYI message in the engineering channel to avoid confusion.,4,"['issue fixed', 'merged MR', 'clarification on log printing']",['forgot to merge MR'],POSITIVE,[],UNKNOWN
|
|
2023-03-23T04:28:18.093899,2023-03-25T09:02:13.653789,aganivada,"{'aganivada', 'rtaraniganty', 'bganganna'}",3,"The discussion thread is about a test suite taking more than an hour in the stage, causing job timeouts. The issue is identified as the deletion of product and publishers in the tear down, which takes time due to a large number of records. It is suggested to clean up the records manually at a time with less traffic. A cleanup job is triggered in the stage, and a Git commit link is shared for updating the develop branch. A suggestion is made to optimize the Get Admin S2S Token keyword to reduce the time taken for operations. A merge request is created, and a backup of the core prod is taken before triggering the cleanup. The cleanup is done in batches, and the count of records is reduced.",23,"['Cleanup job triggered', 'Optimizing Get Admin S2S Token keyword', 'Merge request created', 'Cleanup done in batches', 'Count of records reduced']","['Test suite taking more than an hour', 'Job timeouts', 'Deletion of product and publishers taking time', 'Large number of records causing delay', 'Manual cleanup suggested', 'Cleanup triggered in stage', 'Backup of core prod taken']",MIXED,[],RESOLVED_OR_CLOSED
|
|
2023-02-25T10:02:56.055279,2023-03-24T19:48:11.318389,araman,"{'rvaidya', 'aganivada', 'araman', 'akasim', 'bganganna', 'rtaraniganty'}",6,The discussion thread revolves around an issue where users are facing a 401 error while navigating to the Actions page on stage in a tenant. The issue seems to be related to deleted tenants and stale user actions. The team is investigating the issue and planning to fix it in version 0.9.9.,29,[],"['401 error', 'deleted tenants', 'stale user actions']",NEUTRAL,[],ON_GOING
|
|
2023-03-24T08:24:09.439519,2023-03-24T10:44:31.051399,ppant,"{'ppant', 'rtaraniganty'}",2,ppant created a how-to document for common issues with Poetry and shared it with the team. rtaraniganty thanked ppant for the document. No other specific details or links were mentioned in the discussion thread.,2,"['how-to document', 'Poetry']",[],,[],UNKNOWN
|
|
2023-03-19T23:03:24.788369,2023-03-23T23:12:15.153689,rvaidya,"{'svummidi', 'rvaidya', 'snangia', 'rsrinivasan', 'aganivada', 'ppant'}",6,The discussion thread is about the excessive logging in the INT environment. It is discovered that trace logs are enabled for tenant 19190 and it is suggested to disable them. The ingestion service and sentiment collector are identified as the main sources of excessive logs. It is mentioned that there is a known bug with Log4j2 where log level changes via cloud config may not reflect without service restart. It is requested to revert the log level to info for the sentiment collector.,20,"['excessive logging', 'disable trace logs', 'identify sources of excessive logs', 'revert log level to info']",['known bug with Log4j2'],,[],UNKNOWN
|
|
2023-03-23T07:08:38.710029,2023-03-23T12:15:52.520679,aganivada,"{'aganivada', 'rtaraniganty', 'rvaidya', 'pkarthikeyan'}",4,The team is discussing how to use the name resolution API for the tenant table. They refer to an enum for the resolution target type and clarify that a colon is not required. They provide a sample payload for the query and discuss the format of the key. They confirm that the intent is to use the Java classes generated by OpenAPI and clarify that the name resolver API can be used from apps.,19,"['Using name resolution API for tenant table', 'Referring to enum for resolution target type', 'Providing sample payload for query', 'Discussing format of key', 'Using Java classes generated by OpenAPI', 'Name resolver API can be used from apps']",[],POSITIVE,[],UNKNOWN
|
|
2023-03-21T11:10:20.190789,2023-03-23T06:49:04.622969,rtaraniganty,"{'gshenoy', 'pkarthikeyan', 'aganivada', 'rtaraniganty', 'ppant', 'sranjan'}",6,"The discussion thread includes various topics such as refactoring plat-libs-epoch, logging for tenant 19190, researching load balancer, transaction manager override attempt, setting up load balancers for AWS cloud services, and exploring auto-deploying docker images to ECR. A tracker ticket was created for the changes, and there was a suggestion to cache publisher names locally. The JIRA ticket for integrating all services used by lambda is PLAT-1839.",10,"['refactoring plat-libs-epoch', 'researching load balancer', 'setting up load balancers for AWS cloud services', 'exploring auto-deploying docker images to ECR', 'suggestion to cache publisher names locally']","['logging for tenant 19190', 'transaction manager override attempt']",NEUTRAL,"['PLAT-1840', 'PLAT-1839', 'PLAT-1839', 'PLAT-1840']",UNKNOWN
|
|
2023-03-21T05:15:16.716529,2023-03-23T01:19:11.287689,pjha,"{'aganivada', 'pjha'}",2,"pjha shared a confluence design doc for ""Deploying multiple instances of same service"" and aganivada asked if it can be posted in the design-review channel. pjha agreed. No specific details about the content of the design doc were mentioned.",3,['Deploying multiple instances of same service'],[],,[],UNKNOWN
|
|
2023-03-21T05:04:45.396849,2023-03-21T11:07:21.706529,ppant,"{'ppant', 'rtaraniganty'}",2,ppant asked about an issue with the `AxmFilter` where TRACE logs were being included when the filter was set to DEBUG level. They noticed that the `filter()` method used `level.isLessSpecificThan()` instead of `level.isMoreSpecificThan()`. rtaraniganty confirmed that it should be fixed. No specific JIRA ticket or links were mentioned in the discussion.,2,['AxmFilter issue'],['TRACE logs included'],,[],UNKNOWN
|
|
2023-03-21T08:26:46.904519,2023-03-21T09:15:13.868229,pjha,"{'rtaraniganty', 'pjha'}",2,The discussion thread is about finding documentation for auto-deploying a Docker image to the ECR. They plan to take it to a logical conclusion to determine the structure of the lambda and the necessary permissions. The documentation can be found at <https://pinstripe.atlassian.net/wiki/spaces/PRODUCT/pages/551157789/AutoDeploying+Docker+image+to+the+ECR>.,2,"['Finding documentation', 'Auto-deploying Docker image', 'ECR', 'Lambda structure', 'Necessary permissions']",[],,[],UNKNOWN
|
|
2023-03-21T00:26:54.060059,2023-03-21T09:14:12.192259,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion thread is about the use of IP addresses instead of load balancers in Route53 for backend-service calls. They are considering using load balancers for multi-instance deployment and routing based on HTTP headers. They discuss the discrepancy between requests made to the load balancer and requests received by the tenancy. They plan to test using load balancers manually before updating CDK. They also discuss using Cloud Map and refer to the CDK v1 reference for private DNS namespace examples. No specific JIRA ticket or other links are mentioned.,14,"['use of IP addresses', 'load balancers', 'multi-instance deployment', 'routing based on HTTP headers', 'testing load balancers manually', 'using Cloud Map', 'CDK v1 reference for private DNS namespace examples']",['discrepancy between requests made to load balancer and requests received by tenancy'],NEUTRAL,[],UNKNOWN
|
|
2023-03-20T07:18:58.985919,2023-03-20T23:04:05.498869,aganivada,"{'aganivada', 'askumar'}",2,The discussion thread is about trying to override the transaction manager in the Spring framework. Askumar mentions that he hasn't found a working approach yet and aganivada asks if they have tried it in the QC environment.,4,[],[],NEUTRAL,[],ON_GOING
|
|
2023-03-19T22:26:20.990969,2023-03-20T17:49:19.268689,ppant,"{'ppant', 'rtaraniganty', 'sranjan', 'gshenoy'}",4,"The team discussed the use of the ""data-brokering-libs-jira"" library in Jira Lambda integration with VPC. They considered using the ""platform-libs-epoch"" library instead but decided against it due to its specificity. They discussed renaming ""plat-libs-common"" to ""plat-lambda-commons"" or creating a new library for shared interfaces/methods. They agreed to rename ""plat-libs-epoch"" to ""plat-libs-lambda"" and use it in all lambdas. There was a suggestion to rename it to ""plat-libs-py-common"" to indicate its usability in non-lambda cases as well.",7,"['use of data-brokering-libs-jira library', 'renaming plat-libs-common to plat-lambda-commons', 'renaming plat-libs-epoch to plat-libs-lambda', 'use of plat-libs-lambda in all lambdas', 'renaming plat-libs-lambda to plat-libs-py-common']",['use of platform-libs-epoch library'],POSITIVE,[],UNKNOWN
|
|
2023-03-16T14:24:53.104389,2023-03-20T09:05:10.203339,rtaraniganty,"{'svummidi', 'rtaraniganty', 'bganganna'}",3,The discussion thread is about identifying the test that is creating entities in the production database and not deleting them afterwards. The team suspects that the lack of cleanup after tests is causing this issue. They have updated the test code to track down the tenants left behind and plan to fix the issue soon.,9,"['test code update', 'tracking tenants', 'fixing the issue']","['lack of cleanup', 'creating entities in production database']",,[],UNKNOWN
|
|
2023-03-20T07:18:17.804749,2023-03-20T07:23:08.802149,aganivada,"{'aganivada', 'pjha'}",2,"pjha was asked about their progress on load-balancer research. They replied that they haven't started yet because they were dealing with other issues related to bringing up multiple instances. Now that those issues are fixed, they will begin looking into the load-balancer. No specific details or references were mentioned.",2,['load-balancer research'],"['other issues', 'bringing up multiple instances']",,[],UNKNOWN
|
|
2023-03-17T09:31:38.108989,2023-03-19T23:04:06.962849,ppant,"{'ppant', 'rtaraniganty', 'askumar', 'aganivada'}",4,"The team discusses the requirement of updating lambda code to make API calls through a private domain instead of using API gateway. The platform team will update common libraries and shared lambdas, while individual teams will update their own lambdas. The Apps Workflow Lambda will also be included in the updates. The discussion can be found at <https://pinstripe.atlassian.net/wiki/spaces/~63240b3b051efc698568571a/pages/550175562/Lambda+update+tracking>.",11,"['Updating lambda code', 'Private domain for API calls', 'Updating common libraries', 'Updating shared lambdas', 'Updating individual lambdas', 'Updating Apps Workflow Lambda']",['Using API gateway'],NEUTRAL,[],UNKNOWN
|
|
2023-03-17T08:02:52.682699,2023-03-17T08:31:01.283089,ppant,"{'ppant', 'askumar', 'rtaraniganty'}",3,"The team discusses an issue with API calls to non-existing endpoints in the tenant deletion lambda. The calls throw 404 and 401 errors, causing the step functions to fail. They decide to add a check in the lambda and consider removing the ingestion service from the list. No JIRA ticket or other links are mentioned.",6,"['Adding check in lambda', 'Removing ingestion service from list']","['API calls to non-existing endpoints', '404 and 401 errors', 'Step functions failure']",NEGATIVE,[],ON_GOING
|
|
2023-03-16T14:29:07.216069,2023-03-16T20:42:16.892079,rtaraniganty,"{'pmangalapuri', 'rtaraniganty', 'aganivada'}",3,"The discussion is about whether to prioritize the automatic deployment of builds to the integration environment (PLAT-1589) or the ability to deploy multiple instances of a service during development. They also discuss the need for apps to communicate with multiple backend instances using a header, and consider using ALB to route requests based on the header. They plan to test this approach manually before trying it with CDK route. No specific JIRA ticket or links are mentioned.",6,"['Automatic deployment of builds to integration environment', 'Ability to deploy multiple instances of a service during development', 'Using ALB to route requests based on header']",['No specific JIRA ticket or links mentioned'],NEUTRAL,['PLAT-1589'],UNKNOWN
|
|
2023-03-15T00:28:14.433639,2023-03-15T00:50:16.185109,rtaraniganty,"{'rtaraniganty', 'sbhosale'}",2,"The discussion thread is about an error encountered during the initialization of the context. The error is related to a changeset in the core. The changeset's checksum has changed, causing a validation failure. The solution discussed is to drop the persona table and remove the changelog or add a different changeset to modify the table. The issue is resolved by updating the persona table to match the changeset in develop.",7,"['error resolution', 'context initialization']","['validation failure', 'changeset error']",,"['DISC-2609', 'DISC-2609']",UNKNOWN
|
|
2023-03-14T12:18:59.394609,2023-03-14T12:53:58.085939,mnirmal,"{'mnirmal', 'rtaraniganty'}",2,The discussion thread revolves around an issue with the 0.0.14 version of com.axm.commons. The error message shows a NullPointerException and InvocationTargetException. The issue occurs when running the service locally. The test runs fine despite the errors. A suggested fix involves updating the log4j2.xml file and adding a null check in the code.,11,"['Test runs fine', 'Suggested fix']","['Issue with version 0.0.14', 'NullPointerException', 'InvocationTargetException', 'Error when running locally']",NEUTRAL,[],ON_GOING
|
|
2023-03-14T00:04:22.829639,2023-03-14T02:13:06.844349,ppant,"{'ppant', 'rsrinivasan', 'aganivada'}",3,The discussion thread is about the options for lambda integrations with backend services in VPC. Option 2 is considered better due to the changes and extra cost involved in routing requests through private API Gateway. Microservices interact through a private domain in the format of <service-name>.services.<env>.exp-pinstripe.local.,8,"['Option 2', 'Private domain']","['Extra cost', 'Routing requests through private API Gateway']",,[],UNKNOWN
|
|
2023-03-09T22:14:20.996399,2023-03-09T23:20:14.279699,aganivada,"{'aganivada', 'rvaidya', 'rsrinivasan'}",3,The team analyzed the response time of the getorgs API call and found that it is significantly slower in production due to the lack of user roles in the response. They discussed potential solutions such as introducing caching or storing user/orgs and roles locally. They also mentioned the possibility of maintaining role and orgid metadata on user permissions. The team will reach out to auth0 for a solution. No specific JIRA ticket or links were mentioned.,7,"['Analyzing response time of getorgs API call', 'Identifying the cause of slow response time', 'Discussing potential solutions', 'Reaching out to auth0 for a solution']","['Lack of user roles in the getorgs API response', 'Slow response time in production']",NEGATIVE,[],ON_GOING
|
|
2023-03-09T10:49:19.239149,2023-03-09T21:18:48.759719,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,The discussion thread is about a problem with the release/0.9.8 branch not being closed properly and the manifest files being out of sync. The team discusses the issue and decides to manually delete the remote branch and create a HF CDK branch for future deployments. No specific JIRA ticket or links are mentioned.,14,"['problem resolved', 'manual deletion of remote branch', 'HF CDK branch created']","['release/0.9.8 branch not closed properly', 'manifest files out of sync']",,[],RESOLVED_OR_CLOSED
|
|
2023-03-07T19:40:33.928209,2023-03-09T12:49:26.085139,rtaraniganty,"{'aganivada', 'rtaraniganty', 'svummidi', 'rsrinivasan'}",4,"The discussion thread revolves around an issue with GitLab Maven. The user encountered an access forbidden error when fetching a new library on GitLab, despite it working fine locally. They tried various solutions, including clearing the cache and creating a new project, but the issue persisted. Other users suggested updating the token and checking the authorization model. Eventually, it was discovered that GitLab had released a new feature that required listing all projects allowed to access the artifacts, causing the problem. The security implications of this feature were discussed, and the support team was contacted for further clarification.",60,['GitLab Maven'],"['access forbidden error', 'issue persisted', 'security implications']",,"['PLAT-1620', 'PLAT-1620', 'PLAT-1620']",RESOLVED_OR_CLOSED
|
|
2023-03-07T21:40:53.890079,2023-03-08T20:16:40.588309,ppant,"{'ppant', 'rtaraniganty', 'rsrinivasan', 'aganivada'}",4,"The team is discussing tools for BI with visualization and SQL execution on selected databases and tables. Suggestions include Apache Superset, Metabase, Imply Druid, and Microsoft PowerBI. They also discuss an event-driven approach for data tracking and suggest splitting data between static content and streaming event data for better visualization and querying. The current model has limitations with scraping Prometheus and mapping IDs to names.",6,"['BI tools', 'visualization', 'SQL execution', 'Apache Superset', 'Metabase', 'Imply Druid', 'Microsoft PowerBI', 'event-driven approach', 'data tracking', 'static content', 'streaming event data', 'better visualization', 'querying']","['limitations', 'scraping Prometheus', 'mapping IDs to names']",NEUTRAL,[],ON_GOING
|
|
2023-03-06T15:35:52.152829,2023-03-08T11:03:08.923279,rtaraniganty,"{'rtaraniganty', 'rvaidya', 'hchintamreddy'}",3,"The discussion thread is about an error in IntelliJ when referring to a model class. The error started after a spring dependency update. The participants suggest that if the compilation goes fine, there is no need to worry about the error. One participant suggests defining the model class in requestBodies and referring to it. No specific details or links are mentioned.",6,"['Compilation success', 'Defining model class in requestBodies']","['Error in IntelliJ', 'Error after spring dependency update']",NEUTRAL,[],UNKNOWN
|
|
2023-02-26T21:21:36.106199,2023-03-08T08:09:18.704979,snangia,"{'pjha', 'askumar', 'aganivada', 'snangia', 'rtaraniganty'}",5,The discussion thread is about updating permission policies for the Gitlab-Agent-Role in CDK. It is mentioned that there is currently no way to do this automatically and it needs to be done manually from the console. The team plans to convert this to CDK and add a task for it. They also discuss adding S3 read-write permissions for a specific bucket in the INT environment and mention the need for it in non-INT environments as well. The team agrees to make the necessary changes and updates the trust policy for staging. They also mention the absence of the bucket in production and resolve the issue by adding S3 access permissions for both stage and prod.,38,"['Updating permission policies for Gitlab-Agent-Role in CDK', 'Converting to CDK and adding a task', 'Adding S3 read-write permissions for a specific bucket in INT environment', 'Making necessary changes and updating trust policy for staging', 'Adding S3 access permissions for stage and prod']","['No way to update permission policies automatically', 'Need for S3 read-write permissions in non-INT environments', 'Absence of the bucket in production']",POSITIVE,[],RESOLVED_OR_CLOSED
|
|
2023-03-03T05:07:24.306539,2023-03-07T11:47:56.344119,rsrinivasan,"{'akalyta', 'svummidi', 'rsrinivasan'}",3,"The discussion thread revolves around reviewing topics generated from the last pass data. The prompt for topic extraction has been modified to include sentiment analysis, keyword extraction, emotion matching, and product aspect identification. The team discusses the results and the use of GPT-3.5 for the proof of concept. The conversation also mentions an interesting article comparing GPT-3.5 and Davinci models. The link to the enriched last pass data and enriched retro comments data is provided. No references to JIRA tickets or other links are mentioned.",8,"['topic extraction', 'sentiment analysis', 'keyword extraction', 'emotion matching', 'product aspect identification', 'use of GPT-3.5', 'proof of concept', 'interesting article', 'enriched last pass data', 'enriched retro comments data']",[],,[],UNKNOWN
|
|
2023-02-24T04:08:53.173869,2023-03-07T05:24:44.979809,rsrinivasan,"{'aganivada', 'rsrinivasan'}",2,"rsrinivasan shared a link to a feature flag named ""global.user-permissions-compact-model/targeting"" on LaunchDarkly. aganivada thanked rsrinivasan for sharing the link.",4,"['feature flag', 'LaunchDarkly', 'link sharing']",[],,[],UNKNOWN
|
|
2023-03-03T03:12:39.789749,2023-03-06T22:37:30.131839,pjha,"{'rtaraniganty', 'pjha'}",2,"The discussion thread is about modifying lambda functions that communicate with various services. The main lambda function mentioned is ""platform-lambda-coord-invoker/lambda_function.py"" which uses ""app_config.get_api_domain_url()"" to make service calls. Replacing this with service-specific URLs can cover most services. Other lambda functions mentioned are ""platform-lambda-triggerpulse"" and ""platform-lambda-useraction"" which also use ""app_config"" and ""API_GW_URL"".",4,"['modifying lambda functions', 'communicate with various services', 'replacing app_config.get_api_domain_url() with service-specific URLs', 'platform-lambda-coord-invoker/lambda_function.py', 'platform-lambda-triggerpulse', 'platform-lambda-useraction']",[],,[],UNKNOWN
|
|
2023-03-02T21:59:30.289689,2023-03-02T22:04:16.386179,pjha,"{'aganivada', 'rtaraniganty', 'pjha'}",3,The discussion thread involves pjha explaining their successful use of lambda functions within a VPC and sharing a link to the lambda function. They also agree to update one existing lambda function and move it into the VPC. No specific details or references to JIRA tickets are mentioned.,6,"['successful use of lambda functions within a VPC', 'sharing a link to the lambda function', 'updating existing lambda function', 'moving lambda function into VPC']",[],,[],UNKNOWN
|
|
2023-02-28T14:29:28.389459,2023-03-02T22:03:29.875339,rtaraniganty,"{'aganivada', 'rtaraniganty', 'ppant'}",3,"The team is discussing the need for a tool to remember when debug logs are turned on in cloud config. They also discuss the issue of log4j not loading on the fly and the impact it had on their quota. They explore the possibility of using LS as a temporary tool and analyze the log config for different services. They discover that services fully integrated with cloud config can pull log config changes without restart, while others require a restart. They also discuss the possibility of using tenant-level logging and find a bug in log4j2 related to config refreshing. They plan to test changing the log level to debug and explore if it provides helpful information. References: <https://app.logz.io/#/goto/9c0aadbd9cabd4d62e14726fb580cfec?switchToAccountId=389045>, <https://axiamatic.slack.com/archives/C02BXE5HS00/p1677765624739079>, <https://pinstripe.atlassian.net/wiki/spaces/~63240b3b051efc698568571a/pages/493518911/Tenant+Level+Logging+Control>, <https://issues.apache.org/jira/browse/LOG4J2-3192?focusedCommentId=17494377&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17494377>",22,"['Need for a tool to remember debug log status in cloud config', 'Exploring LS as a temporary tool', 'Analyzing log config for different services', 'Services fully integrated with cloud config can pull log config changes without restart', 'Testing changing log level to debug']","['Log4j not loading on the fly', 'Impact of log4j not loading on quota', 'Some services require restart for log config changes', 'Bug in log4j2 related to config refreshing']",MIXED,[],ON_GOING
|
|
2023-02-28T22:22:32.301219,2023-03-02T20:16:20.145439,svummidi,"{'aganivada', 'svummidi', 'anair', 'bganganna'}",4,"The discussion is about an issue where a user with an existing account is unable to accept an invitation to a different tenant. The suggestion is to redirect the user to the login page instead of the registration page. There is a JIRA ticket for this issue (PLAT-1452). Auth0's limitation is mentioned, and a workaround is suggested to directly add the user without sending an invitation. The Product Owner or Org Admin can add authorized users without approval.",12,"['Redirect user to login page', 'Workaround to add user without invitation', 'Product Owner or Org Admin can add authorized users']","['User unable to accept invitation', ""Auth0's limitation""]",MIXED,['PLAT-1452'],ON_GOING
|
|
2023-03-02T09:18:17.926499,2023-03-02T19:37:23.148239,sjain,"{'rtaraniganty', 'sjain'}",2,"Sanket reported an NPE issue in the INT environment while updating pvt during an integration test. He provided reference logs for further investigation. Ravi offered to deploy the current develop version of core, and after checking, Sanket confirmed that it now works. No JIRA ticket or other links were mentioned.",5,"['NPE issue', 'integration test', 'reference logs', 'deploy current develop version', 'works']",['no JIRA ticket or other links mentioned'],,[],UNKNOWN
|
|
2023-03-02T06:51:40.036509,2023-03-02T18:36:30.989379,rvaidya,"{'aganivada', 'ppant', 'rvaidya'}",3,The team discusses an issue with inviting a collaborator on the same domain mapped to the tenant. The error message indicates that the domain of some emails is not valid. They identify that the issue lies in the specificTenantOnly parameter and the tenantId used to query the publisher on the domain. They decide to make specificTenantOnly false and deploy the fix to the stage version before pushing it to int. The fix is successfully deployed.,11,"['issue with inviting collaborator', 'error message', 'specificTenantOnly parameter', 'tenantId', 'fix deployed successfully']",[],,[],UNKNOWN
|
|
2023-03-01T06:45:12.380929,2023-03-02T08:59:23.911449,rsrinivasan,"{'aganivada', 'rtaraniganty', 'svummidi', 'rsrinivasan'}",4,"The discussion thread revolves around feedback on the quality of topics generated from open text comments for AWS Comprehend, OpenAI's Curie, and OpenAI's Davinci. The team discusses observations such as empty topics in AWS, Curie extracting entire strings, and the release of OpenAI's gpt-3.5-turbo. They also mention the need for question context and tracking token count for comparison. The script and repository links are provided for review. No JIRA ticket or other links are mentioned.",12,"['Observations on topic quality', 'Release of gpt-3.5-turbo']","['Empty topics in AWS', 'Curie extracting entire strings']",NEUTRAL,[],ON_GOING
|
|
2023-03-02T02:55:40.935489,2023-03-02T08:55:08.255229,amishra,"{'aganivada', 'amishra', 'gshenoy'}",3,"The discussion thread is about an error message ""Could not find products by name"" that occurred in the INT environment. It was determined that the error was due to stale data in the integration database. The issue was resolved by cleaning up the wrong values in the database.",11,"['Error resolution', 'Database cleanup']","['Error message', 'Stale data']",,[],UNKNOWN
|
|
2023-03-01T04:02:54.740919,2023-03-02T03:40:14.120689,ppant,"{'ppant', 'rsrinivasan', 'aganivada'}",3,"The team is discussing an issue with the JPA query specification in the core data's `vendor-customer-mapping/all/customers/paged` endpoint. When distinct=true and sort filters are applied together, it results in an SQL error. One possible solution is to use the visibility library to build raw queries. The issue is not currently blocking apps, but it may cause a 500 error if someone uses the affected API. The team also discusses restricting the sort filter options to avoid this issue.",16,"['Possible solution using visibility library', 'Issue not currently blocking apps']","['SQL error when distinct=true and sort filters are applied together', 'May cause a 500 error if someone uses the affected API', 'Discussing restricting sort filter options']",NEUTRAL,[],ON_GOING
|
|
2023-03-01T12:23:12.166039,2023-03-01T19:37:01.383799,svummidi,"{'aganivada', 'svummidi'}",2,The discussion is about whether it is possible to access the tenant selection page without logging out and logging back in. Aganivada is unsure but suggests that it may be possible with some UI effort as the flow/route is coded into the UI logic. No specific details or references are mentioned.,2,[],[],NEUTRAL,[],ON_GOING
|
|
2023-02-25T11:03:04.805629,2023-02-28T09:36:56.985229,rtaraniganty,"{'araman', 'rtaraniganty', 'bganganna'}",3,The discussion thread is about a number of bugs opened in February that don't have the Testing Complexity field populated. bganganna agrees to update the tickets created before adding this field and suggests making it mandatory. rtaraniganty agrees as long as there's a default value. araman agrees to make the field mandatory. No JIRA ticket or other links are mentioned.,7,"['Updating tickets without Testing Complexity field', 'Making Testing Complexity field mandatory']",[],,[],UNKNOWN
|
|
2023-02-27T19:55:36.414679,2023-02-28T07:56:21.837419,aganivada,"{'aganivada', 'snangia', 'pjha', 'rtaraniganty'}",4,"The discussion thread is about the value of the ${env_role_arn} variable in the run-robot-cicd.sh script of system tests. It is mentioned that the value is stored in the AGENT_ROLE_ARN_INT gitlab variable. However, it is noted that the role arn:aws:iam::433798924509:role/Gitlab-Agent-Role only works from the system test repo and not any other repo. There is a suggestion to check if any additional environment variable is being passed to the system-test job. The conversation also references the GitLab documentation on configuring a conditional role with OIDC claims.",12,"['value of ${env_role_arn} variable', 'AGENT_ROLE_ARN_INT gitlab variable', 'checking additional environment variables', 'GitLab documentation on configuring a conditional role with OIDC claims']",['role arn:aws:iam::433798924509:role/Gitlab-Agent-Role only works from system test repo'],NEUTRAL,[],UNKNOWN
|
|
2023-02-28T03:01:51.906139,2023-02-28T03:26:54.144969,aganivada,"{'aganivada', 'snangia'}",2,The discussion is about automating the publishing of a bot to an S3 bucket. They are considering pushing images/bot icons from GitLab to S3 as a zipped file. It is mentioned that they are yet to check if S3 will be used for Slack as well. No specific details or references to JIRA tickets or other links are provided.,4,"['automating publishing of bot', 'pushing images/bot icons from GitLab to S3', 'using S3 for Slack']",[],,[],UNKNOWN
|
|
2023-02-28T00:36:10.171269,2023-02-28T02:59:17.149719,aganivada,{'aganivada'},1,"aganivada informed the team that they had to step out for personal work and would be away for the next 2 hours. Later, aganivada returned and mentioned being back now. No specific details or references to JIRA tickets or other links were provided.",2,[],[],NEUTRAL,[],RESOLVED_OR_CLOSED
|
|
2023-02-27T19:34:10.894129,2023-02-27T22:04:11.662459,rsrinivasan,"{'aganivada', 'rsrinivasan'}",2,"rsrinivasan gained access to Clarity, an internal monitoring tool for Imply, for stage and int clusters. They plan to create alerts using webhooks to send to Slack channels. They are unsure if Opsgenie supports webhooks and want to verify by temporarily adding themselves as admins. No references to a JIRA ticket or other links were mentioned.",5,"['rsrinivasan gained access to Clarity', 'creating alerts using webhooks', 'sending alerts to Slack channels']","['uncertainty about Opsgenie supporting webhooks', 'temporary addition as admins']",NEUTRAL,[],UNKNOWN
|
|
2023-02-14T23:27:42.081179,2023-02-25T05:12:00.922979,araman,{'araman'},1,"The discussion thread includes a mention of different levels of difficulty for tasks: Trivial, Medium, Hard, Rare, On-Call, and Automation. There is also a mention of someone named bganganna, but no further details are provided. No JIRA ticket or other links are mentioned.",2,"['levels of difficulty for tasks', 'Automation']",['bganganna'],,[],UNKNOWN
|
|
2023-02-22T21:39:26.792109,2023-02-22T22:51:19.408599,rvaidya,"{'rvaidya', 'rsrinivasan'}",2,"The discussion is about whether the notification service supports attachments. Rsrinivasan confirms that it does, mentioning both inline attachments (base64 encoded data) and attachments from an S3 bucket. He provides a link to system test cases for this functionality.",2,"['notification service supports attachments', 'inline attachments', 'attachments from S3 bucket']",[],,[],UNKNOWN
|
|
2023-02-21T02:19:26.439079,2023-02-22T02:40:23.923289,ppant,"{'ppant', 'aganivada'}",2,The discussion thread is about finding a solution for using different email templates for re-invitation for SSO migration. The options discussed are using a different template type for re-invitation or updating the same template and using Auth0's common variables to categorize the email. They also discuss using user metadata or app metadata to store the invite type and managing the data when the user accepts the re-invite. They mention the possibility of disabling the email notification from Auth0 and generating the invitation link manually. They also suggest checking the Auth0 community for better solutions. No specific JIRA ticket or other links are mentioned.,5,"['Using different email templates for re-invitation', ""Updating the same template and using Auth0's common variables"", 'Using user metadata or app metadata to store invite type', 'Managing data when user accepts re-invite', 'Disabling email notification from Auth0', 'Generating invitation link manually', 'Checking Auth0 community for better solutions']",[],,[],UNKNOWN
|
|
2023-02-21T07:27:03.662999,2023-02-21T21:10:09.017419,pjha,"{'aganivada', 'pjha'}",2,pjha asked aganivada to review the GitLab Runner Integration page on the wiki. aganivada added some comments and asked pjha to check. pjha replied that they have responded to the questions. No specific details or links were mentioned.,3,['GitLab Runner Integration page'],[],,[],UNKNOWN
|
|
2023-02-19T23:50:26.013889,2023-02-20T20:46:53.954669,rvaidya,"{'avenkataraman', 'rvaidya', 'apatole', 'aganivada', 'rtaraniganty', 'mli'}",6,The discussion thread is about whether to split the customer table into two tables for connected and invited customers. The team is considering this for pagination purposes and to improve the user experience. They are discussing the possibility of using tabs instead of sorting and filtering to display the different categories. A design proposal has been shared for review. [Link to design proposal](https://www.figma.com/file/nviGvKraWGkHaJeb4ckXoI?node-id=7918:231907#374342318),11,"['splitting customer table', 'improving user experience', 'using tabs']",['sorting and filtering'],POSITIVE,[],UNKNOWN
|
|
2023-02-17T09:09:30.772179,2023-02-20T03:16:35.359889,rtaraniganty,"{'araman', 'rtaraniganty'}",2,The discussion thread is about targeting Monday noon for a deployment. Araman suggests deploying version 0.9.7 rel1 once the root cause analysis (RCA) for the discussed issue is known. The issue is further discussed in a Slack conversation linked here: https://axiamatic.slack.com/archives/C02NJB4RCBC/p1676878559483649.,2,"['deployment', 'version 0.9.7 rel1']","['root cause analysis', 'issue']",,[],UNKNOWN
|
|
2023-02-20T01:23:54.950599,2023-02-20T01:43:33.882889,askumar,"{'askumar', 'ppant', 'aganivada'}",3,"The discussion thread is about askumar asking for a review of an approach to update/fetch the stage of epoch execution. ppant is unable to open the link, so askumar adds access for him. aganivada suggests sharing the link in the design channel and tagging tls for review. askumar agrees and adds some comments.",7,"['review of approach', 'adding access']",['unable to open link'],,[],UNKNOWN
|
|
2023-02-17T08:41:15.360069,2023-02-17T08:44:49.336819,araman,"{'aganivada', 'araman'}",2,"Araman asks if there will be any fixes pushed today, mentioning that he has raised questions and is waiting for replies on some changes. Aganivada says he is not aware of any fixes, but the EA bulk upload has already been deployed. They decide to wait for confirmation from Product.",3,[],[],NEUTRAL,[],ON_GOING
|
|
2023-02-17T05:40:11.273499,2023-02-17T06:55:35.808789,nsrivastava,"{'aganivada', 'rtaraniganty', 'nsrivastava'}",3,"The discussion thread is about a Docker task in the SC main branch that failed with an ""InvalidIdentityToken"" error. The team suspects it could be intermittent and suggests retrying. One team member speculates that GitLab may have changed their certificate. Another team member jokes about it being a Friday afternoon in the EU.",5,"['intermittent failure', 'retrying']","['InvalidIdentityToken', 'GitLab certificate change', 'Friday afternoon']",,[],UNKNOWN
|
|
2023-02-16T21:42:29.393719,2023-02-16T21:45:25.524849,aganivada,"{'aganivada', 'ppant'}",2,ppant added a JIRA ticket (PLAT-1706) for customizing email templates during re-invite for the next sprint. They discussed passing a query parameter like `reinvite=true` and selecting the re-invite template. They also mentioned the possibility of suppressing it from auth0 if necessary.,3,"['customizing email templates', 're-invite', 'query parameter', 're-invite template']",['suppressing from auth0'],POSITIVE,['PLAT-1706'],UNKNOWN
|
|
2023-02-16T08:35:28.500489,2023-02-16T10:23:28.482779,rtaraniganty,"{'rtaraniganty', 'rsrinivasan'}",2,"The discussion thread is about searching for a specific name or part of a name using an API. An API link is provided for visibility v2 search on tenancy. The user asks about searching on multiple regex and the response mentions using the ""pin"" operator which takes an array of patterns. The user also mentions implementing a script for searching purposes.",8,"['API search', 'Regex search', 'Pin operator', 'Script implementation']",[],,[],UNKNOWN
|
|
2023-02-16T08:34:57.122469,2023-02-16T09:12:37.708189,rtaraniganty,"{'aganivada', 'rtaraniganty', 'rvaidya'}",3,The discussion thread is about finding the fastest way to obtain a tenant ID based on a name. It is suggested to use the API endpoint <https://api.integration.axiamatic.cloud/tenancy/swagger-ui/index.html?configUrl=/tenancy/v3/api-docs/swagger-config#/tenants/getAllTenants> with an ilike rsql query filter. The link <https://gitlab.com/axiamatic-main/axm-defaults/-/merge_requests/9> is also mentioned.,5,"['fastest way to obtain tenant ID', 'API endpoint', 'ilike rsql query filter']",['none'],,[],UNKNOWN
|
|
2023-02-14T22:28:24.806239,2023-02-15T00:09:30.559009,aganivada,"{'aganivada', 'askumar', 'psomasamudram563'}",3,The discussion thread is about building a metrics dashboard and mapping IDs to names. They are using Grafana and DronaHQ to handle this issue. They discuss exporting mappings to a CSV file and mention that DronaHQ can export CSVs for any backend API. They also mention integrating with the production environment soon. No specific JIRA ticket or other links are mentioned.,9,"['building a metrics dashboard', 'mapping IDs to names', 'using Grafana', 'using DronaHQ', 'exporting mappings to a CSV file', 'DronaHQ can export CSVs for any backend API', 'integrating with the production environment']",[],,[],UNKNOWN
|
|
2023-02-14T23:09:31.982239,2023-02-14T23:26:05.834519,aganivada,"{'aganivada', 'ppant'}",2,ppant suggests using a status page tracking solution from Better Uptime. Aganivada asks to hold off on researching until they confirm if it meets their requirements. No specific details or references are mentioned.,3,['status page tracking solution from Better Uptime'],[],NEUTRAL,[],UNKNOWN
|
|
2023-02-14T01:00:31.962859,2023-02-14T02:14:56.430969,mnirmal,"{'mnirmal', 'aganivada', 'hchintamreddy'}",3,"The discussion thread involves mnirmal requesting hchintamreddy to review and execute queries to delete user instances and responses in PROD. hchintamreddy approves the queries, and aganivada confirms that the queries have been executed successfully. The first query updates 2 records, while the second query does not update any records. No references to JIRA ticket or other links are mentioned.",5,"['requesting review and execution of queries', 'approval of queries', 'successful execution of queries']","['no updates in second query', 'no references to JIRA ticket or other links']",,[],UNKNOWN
|
|
2023-02-13T23:40:39.718969,2023-02-13T23:48:22.063079,rsrinivasan,"{'ppant', 'rsrinivasan'}",2,"The discussion thread is about a terminal called Warp.dev, which is being recommended as a better alternative to iTerm. One user tried using it and found it to be good, but mentioned difficulty in integrating tmux with it. No JIRA ticket or other links are mentioned.",3,"['Warp.dev', 'better alternative', 'good']",['difficulty in integrating tmux'],,[],UNKNOWN
|
|
2023-02-10T03:45:28.861739,2023-02-13T19:59:27.140789,rvaidya,"{'askumar', 'svummidi', 'rvaidya', 'rsrinivasan', 'aganivada', 'ppant'}",6,"The team discussed a weird issue with an app call in the STAGE environment. The issue occurred when the app called multiple downstream APIs with different users and tenants. It was found that the context was not getting cleared properly, leading to permission issues. The team identified the root cause and proposed a fix using the afterCompletion() method instead of postHandle(). They also discussed enabling debug logging for a specific tenant and planned to deploy a hotfix. The team also addressed concerns about using stale user context from previous requests. Reference: PLAT-1682, <https://gitlab.com/axiamatic-main/core-services-data/-/tree/hotfix/0.0.12.3>",30,"['Identified root cause', 'Proposed fix using afterCompletion() method', 'Addressed concerns about using stale user context', 'Planned to deploy hotfix']","['Weird issue with app call in STAGE environment', 'Context not getting cleared properly', 'Permission issues', 'Enabling debug logging for specific tenant']",MIXED,['PLAT-1682'],RESOLVED_OR_CLOSED
|
|
2023-02-09T21:22:37.919879,2023-02-13T09:23:30.310499,rtaraniganty,"{'aganivada', 'rtaraniganty', 'askumar'}",3,"The discussion thread is about finding a way to map individual IDs in Grafana and periodically updating the mapping in their store for transformations. They received a response from Grafana stating that this kind of mapping needs to happen on a datasource level and asked for details on how they scrape their metrics. They discussed the mappings needed, including tenantid to tenant name and user id to email/user name. They considered using a name cache in Redis and consulting it to translate IDs to names before publishing metrics. They also explored options available from Grafana/Prometheus to automatically link the data. There were references to community posts discussing device ID lookup and using SQL data to label time series.",14,"['Finding a way to map individual IDs in Grafana', 'Periodically updating the mapping in the store for transformations', 'Exploring options available from Grafana/Prometheus to automatically link the data']","['Mapping needs to happen on a datasource level', 'Scraping metrics details requested by Grafana', 'Considering using a name cache in Redis for ID translation', 'Consulting Redis cache to translate IDs to names before publishing metrics', 'References to community posts discussing device ID lookup', 'Using SQL data to label time series']",MIXED,[],UNKNOWN
|
|
2023-02-10T13:30:50.127899,2023-02-13T07:05:29.246579,akalyta,"{'akalyta', 'svummidi', 'aganivada'}",3,The discussion thread is about adding a secret key to CDK and ensuring it is passed to the application on int. Akalyta is trying to add the OpenAI secret API key to the application but is facing issues. Anil suggests checking the setup-basics.sh script and adding the necessary functions. Akalyta also mentions adding the key to the estimation-service/cdk.json file. Svummidi confirms that setup-functions.sh is already executed in INT and suggests making changes to the estimation service scripts. Akalyta plans to test the changes and submit an MR.,9,"['adding secret key', 'passing key to application', 'checking setup-basics.sh script', 'adding key to cdk.json file', 'making changes to estimation service scripts', 'testing changes', 'submitting MR']",['facing issues'],,[],UNKNOWN
|
|
2023-02-12T20:51:59.813159,2023-02-13T01:25:27.425789,aganivada,"{'aganivada', 'ppant', 'rsrinivasan', 'rvaidya'}",4,The discussion thread is about an issue with sending notifications via email. The error message indicates an invalid recipient address. The team is trying to determine the cause of the issue and whether email validation is enabled during user creation. They also discuss the possibility of updating the user's email directly from the backend. It is mentioned that the tenant is a webapp tenant. A UI ticket for email validation is planned.,12,"['determining cause of issue', ""updating user's email from backend"", 'planned UI ticket for email validation']","['issue with sending notifications via email', 'invalid recipient address', 'email validation during user creation']",NEUTRAL,[],ON_GOING
|
|
2023-02-06T01:49:05.028849,2023-02-07T03:37:04.304049,aganivada,"{'aganivada', 'anair', 'rsrinivasan', 'bganganna'}",4,"The discussion thread is about a major issue where customers have MFA enabled but vendors do not. The team made a change in the auth0 rules to skip MFA check for vendor users with the ""obfuscated:read"" role. This change is currently blocking Splunk from accessing EA's product details page. The fix has been verified in the int/stage environment and a JIRA ticket (PLAT-1656) has been created for this issue. There is also a question about whether similar changes should be made to allow access to system_user without MFA.",18,"['MFA enabled for customers', 'Change in auth0 rules', 'Fix verified in int/stage environment']","['Vendors without MFA', ""Blocking Splunk from accessing EA's product details page"", 'Question about system_user without MFA']",,"['PLAT-1656', 'PLAT-1656', 'PLAT-1656']",UNKNOWN
|
|
2023-01-31T07:25:13.484429,2023-02-02T07:22:46.754499,rvaidya,"{'aganivada', 'askumar', 'rvaidya'}",3,"The discussion thread revolves around two issues. The first issue is about the core throwing a 500 error instead of a 403 error when a ProductAdmin logs in without any permission in the permission set. The second issue is related to the PVT table and the absence of the PID/Product Admin preauthorize check. The team discusses possible solutions and creates JIRA tickets for further investigation and resolution. The JIRA tickets mentioned are DISC-2321, PLAT-1648, and PLAT-1650.",19,"['Core throwing 500 error', 'Possible solutions', 'JIRA tickets']","['Core throwing 403 error', 'PVT table issue', 'Absence of PID/Product Admin preauthorize check']",,"['DISC-2321', 'DISC-2321', 'PLAT-1650', 'PLAT-1650']",UNKNOWN
|
|
2023-01-31T20:09:01.007139,2023-02-01T04:32:56.443719,aganivada,"{'aganivada', 'askumar', 'rvaidya'}",3,The discussion thread is about bugs found in version 0.9.7. PLAT-1642 is related to permissions not being verified properly for the updateProductInstance API. PLAT-1641 is closed after discussion. PLAT-1640 requires updating an error message. PLAT-1638 needs more information. PLAT-1636 and 1637 require UI and backend changes. The fix for PLAT-1642 involves changing the condition from AND to OR.,7,"['PLAT-1641', 'PLAT-1640', 'PLAT-1636', 'PLAT-1637']","['PLAT-1642', 'PLAT-1638']",,"['PLAT-1642', 'PLAT-1641', 'PLAT-1640', 'PLAT-1638', 'PLAT-1638', 'PLAT-1636', 'PLAT-1641', 'PLAT-1642', 'PLAT-1642']",RESOLVED_OR_CLOSED
|
|
2023-01-31T18:38:08.480769,2023-01-31T20:15:43.941189,araman,"{'aganivada', 'araman'}",2,"The discussion is about onboarding an existing vendor through an invitation. Aganivada asks if the onboarding flow was triggered, and mentions that permissions were updated correctly in another flow. Araman suggests discussing further over a call. No specific details or references are provided.",4,"['onboarding flow', 'permissions update']",[],,[],UNKNOWN
|
|
2023-01-30T22:29:05.464339,2023-01-31T06:05:19.695039,rtaraniganty,"{'rtaraniganty', 'akasim'}",2,"The discussion thread is about missing logs in the logz.io UI. It is mentioned that the logs are missing in both stage and prod environments. It is discovered that the stage environment had a 7-day retention period, which caused the logs to be missing. The retention period is fixed to 14 days for stage and int environments and 30 days for prod. No JIRA ticket or other links are mentioned.",16,['fixed retention period'],"['missing logs', 'no JIRA ticket']",,[],RESOLVED_OR_CLOSED
|
|
2023-01-30T01:15:32.783079,2023-01-30T03:07:35.687589,aganivada,"{'aganivada', 'bganganna'}",2,The discussion is about a JIRA ticket (PLAT-1636) and whether the issue mentioned in the ticket was covered in Figma. The team wants to know if they can fix the issue and update dev-rca accordingly. There is also a discussion about the behavior of removing a product by a product admin and whether it should be deleted from the tenant or just removed from the ProductAdmin role. It is mentioned that the expected behavior is for the product admin to have all permissions as the orgadmin on the specific product. No specific details about the issue or the JIRA ticket are provided.,4,"['JIRA ticket (PLAT-1636)', 'Fixing the issue', 'Updating dev-rca', 'Product admin permissions']","['Behavior of removing a product', 'Deleting from the tenant', 'Removing from ProductAdmin role']",NEUTRAL,['PLAT-1636'],UNKNOWN
|
|
2023-01-26T14:20:53.249369,2023-01-30T00:51:18.775899,anair,"{'aganivada', 'anair'}",2,"The discussion thread is about measuring metrics in the monitoring piece and the feasibility of using start and end dates. Sample queries and actions related to actions and messaging are discussed. The need to add more attributes to support the metrics is mentioned. The conversation involves anair, aganivada, mnirmal, and hchintamreddy. No specific JIRA ticket or other links are mentioned.",8,"['Measuring metrics in the monitoring piece', 'Feasibility of using start and end dates', 'Sample queries and actions related to actions and messaging', 'Involvement of anair, aganivada, mnirmal, and hchintamreddy']","['No specific JIRA ticket or other links mentioned', 'Need to add more attributes to support the metrics']",NEUTRAL,[],UNKNOWN
|
|
2023-01-09T22:45:51.941449,2023-01-24T23:09:51.760769,rvaidya,"{'gshenoy', 'svummidi', 'rvaidya', 'rsrinivasan', 'aganivada', 'rtaraniganty', 'anair'}",7,The discussion thread focuses on the implementation of an audit log system. They discuss the challenges of ID resolution and the possibility of using backend services to provide names for objects. They emphasize the importance of capturing user actions in the audit log and discuss the possibility of adding a user name field. The thread ends with additional questions and considerations for the audit log implementation. No specific details or references to JIRA tickets or other links are mentioned in the context.,75,"['Implementation of audit log system', 'Capturing user actions in the audit log', 'Using backend services for ID resolution', 'Adding a user name field']",['Challenges of ID resolution'],NEUTRAL,['PLAT-1301'],ON_GOING
|
|
2023-01-16T04:38:02.157089,2023-01-24T03:14:22.695709,ppant,"{'ppant', 'rtaraniganty', 'psomasamudram563', 'aganivada'}",4,"The discussion thread is about implementing pagination for the ""/api/v1/vendor/{tenantId}/customers"" API. The team discusses the challenges of syncing page number and size with the second call and suggests filtering invitations on a given tenant to update records with organization info. They also mention splitting the UI into two components and adding an API to core-data to narrow the search. A new API has been deployed to int for testing. No specific details or references to JIRA tickets or other links are mentioned.",8,"['Implementing pagination for /api/v1/vendor/{tenantId}/customers', 'Syncing page number and size with the second call', 'Filtering invitations on a given tenant to update records with organization info', 'Splitting the UI into two components', 'Adding an API to core-data to narrow the search', 'New API deployed to int for testing']",[],,[],UNKNOWN
|
|
2023-01-17T09:04:53.086339,2023-01-17T20:20:51.321179,aganivada,"{'aganivada', 'askumar'}",2,The discussion thread is about a change in the int platform-libs-commons repository that was not verified in Int. The change caused an exception related to the put operation not being supported on readonlyhttpheaders. The team is discussing the issue and reviewing the webclientconfig change made to address it.,5,"['change in int platform-libs-commons repository', 'reviewing webclientconfig change']","['not verified in Int', 'exception related to put operation not supported on readonlyhttpheaders']",,[],UNKNOWN
|
|
2023-01-16T08:57:08.254499,2023-01-16T14:34:21.148199,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,"The discussion is about adding an API in CoreData to reduce round trips. However, it is mentioned that the call cannot be moved to core as it requires information about the organization from tenancy. Instead, the suggestion is to update the tenancy call to return open invitations and split the UI into two components: open invitations and active customers. The idea of using a tabbed view for invited and connected customers is also mentioned. No specific JIRA ticket or links are referenced.",3,"['Adding API in CoreData to reduce round trips', 'Updating tenancy call to return open invitations', 'Splitting UI into two components: open invitations and active customers', 'Using a tabbed view for invited and connected customers']",['Call cannot be moved to core as it requires information about the organization from tenancy'],NEUTRAL,[],UNKNOWN
|
|
2023-01-11T15:06:51.493089,2023-01-12T20:19:55.566259,rtaraniganty,"{'aganivada', 'rtaraniganty', 'askumar', 'ppant'}",4,"The team is discussing the status of the Job executor service and whether it is running as expected. They are unsure if the jobs it is supposed to run are being tracked. Ashwani is suggested to look into it, and a link to the project is provided.",7,[],"['Job executor service not running as expected', 'Jobs not being tracked']",,[],UNKNOWN
|
|
2023-01-12T03:41:51.639469,2023-01-12T10:19:45.549719,askumar,"{'askumar', 'rtaraniganty', 'aganivada'}",3,"The discussion thread revolves around a script being executed in PROD for the tenancy endpoint, causing the API gateway to deny requests due to a malicious URL. It is revealed that the issue was triggered by a tenant clean-up and was caused by a script with incorrect values. The IP address responsible for the issue is traced back to Beam Telecom Pvt Ltd in India. The issue has been fixed, and the team discusses the importance of investigating suspicious activities. No references to JIRA tickets or other links are mentioned.",13,"['issue fixed', 'importance of investigating suspicious activities']","['script executed in PROD', 'API gateway denying requests', 'malicious URL', 'issue triggered by tenant clean-up', 'script with incorrect values', 'IP address traced back to Beam Telecom Pvt Ltd']",,[],UNKNOWN
|
|
2023-01-10T13:28:07.015369,2023-01-10T13:55:49.822239,rtaraniganty,"{'svummidi', 'rtaraniganty'}",2,The discussion is about the possibility of summarizing all responses for a given open-text question in future releases. They are currently working on trying G2 comments summarization and testing it for scale. They also want to confirm their ability to run the model in-house. No specific JIRA ticket or links are mentioned.,3,"['Possibility of summarizing all responses', 'Working on G2 comments summarization', 'Testing for scale', 'Ability to run the model in-house']",[],,[],UNKNOWN
|
|
2023-01-10T03:02:09.785699,2023-01-10T05:55:09.828369,araman,"{'sfarooqh', 'askumar', 'rsrinivasan', 'araman', 'bganganna'}",5,"The discussion thread revolves around a rule parsing error in a test tenant in the production environment. The error is related to the latest update in prod for reports, but it is not clear if it is caused by a lambda timeout issue. A trace_id and a JIRA ticket (DISC-2137) have been shared for further investigation. There is also a mention of manual editing of user metadata and the creation of permissions in reporting.",15,"['rule parsing error', 'latest update in prod for reports', 'manual editing of user metadata', 'creation of permissions in reporting']",['lambda timeout issue'],NEUTRAL,"['DISC-2137', 'DISC-2137', 'DISC-2137']",ON_GOING
|
|
2023-01-08T21:18:10.412819,2023-01-08T21:21:24.342989,aganivada,"{'aganivada', 'sparashar'}",2,"Aganivada assigned JIRA ticket PLAT-1560 to ppant, but marked it for the next sprint due to time constraints. However, if ppant has the bandwidth, they are free to pick it up. Sparashar mentioned that the Apps service would be using the API. cc: rvaidya. [JIRA ticket PLAT-1560](https://pinstripe.atlassian.net/browse/PLAT-1560)",2,"['JIRA ticket assignment', 'ppant', 'pick up task']",['time constraints'],NEUTRAL,['PLAT-1560'],UNKNOWN
|
|
2023-01-05T20:15:06.456839,2023-01-05T20:17:49.261199,slackbot,"{'aganivada', 'slackbot'}",2,"The discussion thread is about the impact of a change on SSO accounts already set up in int and stage. The user mentions that the email from Auth0 does not mention any issues with SAML integration, so they believe the integration should not break due to the change.",2,"['impact of change on SSO accounts', 'no issues with SAML integration']",['integration breaking due to change'],,[],UNKNOWN
|
|
2023-01-04T10:20:01.708739,2023-01-05T20:08:28.312869,rtaraniganty,"{'ppant', 'rtaraniganty', 'psomasamudram563', 'aganivada'}",4,"The discussion thread is about connecting to a VPN from GitLab programmatically. They discuss using OpenVPN and the need for VPN access for system test jobs. They also explore alternative ways of securing access to APIs, such as using temporary credentials from AWS STS. The Perimeter 81 VPN service is mentioned, along with its features and pricing. They also discuss building an authorizer for monitoring purposes. No specific JIRA ticket or other links are mentioned.",15,"['connecting to VPN programmatically', 'using OpenVPN', 'VPN access for system test jobs', 'alternative ways of securing access to APIs', 'temporary credentials from AWS STS', 'Perimeter 81 VPN service', 'Perimeter 81 features', 'Perimeter 81 pricing', 'building an authorizer for monitoring purposes']",[],,[],UNKNOWN
|
|
2023-01-05T00:30:16.886919,2023-01-05T00:53:59.345729,akasim,"{'sfarooqh', 'pkarthikeyan', 'aganivada', 'akasim', 'sranjan'}",5,"The team noticed that after merging the hotfix branch to the develop and main branches, the pipeline build did not automatically trigger for both branches. They speculated that this may be due to a warning about remote branch deletion. It was later discovered that GitLab was experiencing an outage, which may have caused the issue. The team confirmed that there were no other irrecoverable issues and were able to manually trigger the pipeline.",13,['successful manual pipeline trigger'],"['pipeline build not automatically triggered', 'warning about remote branch deletion', 'GitLab outage']",,[],UNKNOWN
|
|
2022-03-09T16:51:14.414469,2023-01-04T20:56:14.180639,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,The discussion thread is about updating the authorizer in the API Gateway to allow calls from an associated VPN. They also discuss excluding health calls from GitLab and using a pass-through authorizer for non-apps. They mention the possibility of using an IP range for GitLab calls and reference an AWS resource policy for API Gateway access. There is also mention of an ip-authorizer lambda function. No specific JIRA ticket or other links are mentioned.,11,"['Updating authorizer in API Gateway', 'Allowing calls from associated VPN', 'Using pass-through authorizer for non-apps', 'AWS resource policy for API Gateway access', 'IP range for GitLab calls', 'ip-authorizer lambda function']",['Excluding health calls from GitLab'],NEUTRAL,[],UNKNOWN
|
|
2023-01-03T22:20:32.401649,2023-01-03T22:40:15.535679,pmangalapuri,"{'pmangalapuri', 'aganivada'}",2,"The discussion is about restricting the override of a Docker image for a release version. The team forgot to update to the next development version after rebasing from the main branch. However, it is noted that the develop branch always has ""-develop"" suffixed, so there is no issue with overriding the release version. The manual update of the version for the UI project is mentioned as the reason for running into this situation.",4,"['no issue with overriding release version', 'develop branch always has -develop suffixed']","['team forgot to update to next development version', 'manual update of version for UI project']",NEUTRAL,[],UNKNOWN
|
|
2023-01-02T12:18:22.300859,2023-01-02T22:20:16.321799,rtaraniganty,"{'aganivada', 'rtaraniganty'}",2,rtaraniganty added an epic to track flags that could be retired. They noticed that there are 3 platform flags with targeting set to off but are returning false. aganivada explained that the security-settings and SSO related flags are on the back-burner and will be cleaned up in this sprint.,2,"['epic to track flags that could be retired', 'cleaning up flags in this sprint']","['platform flags with targeting set to off but returning false', 'security-settings and SSO related flags on back-burner']",,['HOUS-28'],UNKNOWN
|
|
|
