Secoda Community

Screenshot 2023-09-25 at 9.59.54 AM.png

Screenshot 2023-09-25 at 9.59.07 AM.png

Hi Manasa! The creation query can be found at the `&lt;/&gt;` button in the top right of the tables. Learn more at this link: <https://docs.secoda.co/features/queries/documenting-queries#creation-queries>
I believe what you're looking at in the second photo is the query history.

image.png

Hello <@U053D21TN6A> yes i checked it there as well and still the query it shows is incomplete.

Hey <@U02N4NXTTJR> any idea what might be going on here?

I'll look into it, from the first glance it looks like a delete query is mistakenly being picked up as the creation query

<@U02N4NXTTJR> I see this for couple of other tables as well. Is this something that can be fixed at once for all of them, or it needs to be addressed individually for every table?

We can probably fix it for all of them at the same time

Thank you! Please keep me posted here for any updates.

Hi <@U02N4NXTTJR> May I know the estimate as to what would be the duration to fix this?

Hi it'll probably be near the end of next week

Hi <@U02N4NXTTJR> I still see this hasn't been fixed. Any update on this?
Our Business folks rely on Secoda to look at the code. This is having a impact on us. I request you to Please correct this as soon as possible.

Hi Manasa, apologies for the delay. We have our eyes on it and are trying to get a fix out as soon as possible!

Hi <@U04S8N9KDD3> Thank you for responding. Is there a Estimated time to get this done?

Hi  <@U04S8N9KDD3> <@U02N4NXTTJR> Its been 22 days since I reached out to get this issue fixed. I still see this hasn't been fixed. Guys any update? This is having a major impact on us.

Hey <@U05TA1WM068> I apologize about the delays on this issue. We've had to do a complete refactor of our lineage to support staling old lineage, so there's been a lot of unknowns that have come up during that process. We've been continuously working on this during the last month and we're hoping to have an update released next week. If there are any further delays we'll make sure to update you.

Hey <@U01MHQR7DE2> Thank you for your response. Looks like there is a confusion. There was one incident which was related to lineage issue. But this one right here is about "*incomplete Creation queries"*. Where we are unable to see complete code.
So if we are still on the same page, the estimated fix will still be by next week for this one as well?

Apologies about the miscommunication. The two issues of incomplete lineage and creation queries are linked since lineage is derived from the creation queries. So once we push the updates it should resolve both issues.

Hey <@U01MHQR7DE2> Can you please check if you have access to this provided link below. If yes, can you please add our request items here in this link below and their estimated time of completion. This is for our Team and the business users to have track on the requirements.
<https://docs.google.com/spreadsheets/d/1IpgPCvm8begBqWtKVeJA8Eh2RuALppXHnhmxuT1MLtc/edit#gid=316153988>

Hi Manasa! We have regular syncs with the Cardinal team. Including one on the 25th. Would you like to join and we can address any requests there?

Hello, <@U04S8N9KDD3>. Thank you very much. That would be great. Please send the invitation to me.

Hi <@U04S8N9KDD3> Did you send me over the invite? I don't see anything in my mailbox so far.

The other users in our workspace able to log-in without any issues.

Thanks for the details <@U02H1V13V99>, we're investigating the issue and will provide some guidance shortly on how the issue can be resolved.

<@U02H1V13V99> can you ask Scott to try now please.

Can you let us know what might be the issue here?

Hey <@U05TZB94RM1> we're investigating why the integration failure is occurring and will provide guidance on how to fix the error shortly.

<@U05TZB94RM1> based on the error message, it seems that the user that you've connected MongoDB with doesn't have the correct permissions.

The required permissions are included in our documentation here. <https://docs.secoda.co/integrations/databases/mongodb#creating-a-database-user>. At a minimum the user needs `Only read any database`

Thanks Andrew, those are the permissions I gave the user.
I can confirm this new user can connect using the MacOS terminal.
I can also confirm that the IPs where whitelisted... in fact, I also temporarily opened it to any IP just to make sure.
Will give it another shot.

No joy yet... do you have any sort of error log on your side with some detail? Happy to try more, yet another hint would be super useful.
Thank you!

Ok, it finally worked... changed 2 things, so I am not sure what cured it...

1. Changed the name of the "mongo cluster" in the integrations tab, from the actual mongo cluster name, to the name of the database I am interested in.
2. When selecting the schema to crawl, I selected all databases, then ran the sync... then it complained that it could not access something in the "config" dB... then I deselected all the dBs except for the one I'm interested in, and voila!
Thanks <@U01MHQR7DE2>, hope this helps : )

Hey <@U05TZB94RM1> we ended up pushing a fix this evening, so I think that plus some of the changes you made led to the resolution. Thanks for the detailed explanation

We don't currently support column profiling for MongoDB at the moment.

Ok, thanks... is it in your product roadmap yet? Just curious... happy to help test when the time comes.

I've created a ticket with the team to add this to our backlog! Our MongoDB integration is fairly new, which is why we aren't currently supporting it.

Yes you can do this. If you go into the Dictionary, you can create terms and metrics there. Once these are created, you are able to tag them with Related resources such as columns. Check out this short video showing these steps. <https://www.loom.com/share/648eedca48374e1f9a2e3a48ff8b7c1a?sid=3e118aac-ddb1-4e8b-a65e-2d8bbedd2dfc>

Thank you Ainslie! :pray:... follow-up question... is there a way to do this from the "columns" view?  Since I have thousands of fields, and many of them repeat in different tables, I'd like to filter the columns table, and apply the relationship there... it'd be much more efficient for me.

Hm this is currently not possible, but you could test out using the <https://docs.secoda.co/secoda-api|API> to make the relationships.

You could also create a <https://docs.secoda.co/features/collections-1|collection> to group these different resource types (columns and terms) into a related folder.

That is expected behavior. There is no "Not PII" tag, however you can create on using <https://docs.secoda.co/resource-and-metadata-management/tags/custom-tags|Custom Tags>. Secoda can also autodetect PII using the <https://docs.secoda.co/resource-and-metadata-management/tags/auto-pii-tagging|PII identifier>.

Yep, custom tags in the settings would work for this use case! We plan to implement other custom governance tags in the future, like "sensitive" "confidential" "public" etc.

Ok, thanks Ainslie. Different companies call those tags differently, NISP, etc... so I hope the governance tags will also be customizable : )

For what it's worth, just tried and it's working like a charm again. Cheers

Thanks Carlos! Yes, it should be resolved

I've made a ticket for our team to investigate :slightly_smiling_face:

Hi Carlos, this has now been resolved. Please let us know if you're not seeing this on your end!

YEs, it looks correct now, thank you <@U053D21TN6A>, <@U04S8N9KDD3>

Amazing! Thanks for flagging this Carlos.

Thank you for the call out! I'll flag this to our team.

Screenshot 2023-10-06 at 12.04.04 PM.png

Screenshot 2023-10-06 at 12.04.14 PM.png

Hey <@U05TA1WM068> it looks like the other tables that aren't in the lineage graph haven't been synced into Secoda yet. For example, `small_parcel_facts_vw` isn't in Secoda. You'll have to ask your admin that the service account has the correct permissions to sync these tables.

Hi <@U01MHQR7DE2> Thank you for responding. No, we have synced everything in the non-prod workspace. And I have validated it myself we have all the tables and all the views.

<@U05TA1WM068> what URL are you accessing Secoda on?

Here <https://app.secoda.co/teams/b1981da5-9ce6-4e58-bcf7-1bf0ed1a5aa4/catalog?resource=table&amp;index=0&amp;filters=%7B%22cluster%22%3A%5B%22764fd28f-b3ad-4bb0-8b8b-6ee37b4b6f3b%22%5D%2C%22database%22%3A%22vndy-ofl-next-np-cah%22%2C%22schema%22%3A%22l1_opti_fact%22%7D|https://app.secoda.co/teams/b1981da5-9ce6-4e58-bcf7-1bf0ed1a5aa4/catalog?resource=t[…]vndy-ofl-next-np-cah%22%2C%22schema%22%3A%22l1_opti_fact%22%7D>

okay, I just noticed that these tables/views I was facing issue in the lineage no longer exists in NP. It has been removed by the team 2 days ago as it was causing some issue in our pipeline deployment.

I wasn't aware of this. They are planning to create this again sometime next week. Post that I'll validate these again. If the issue still persists I'll reach out here.

Hi Daniel! We are aware of this issue and hoping we can get a fix out asap. In the mean time, if you click enter after the email, it'll recognize it as an email provided!

Screen Recording 2023-10-26 at 11.35.56 AM.mov

Hi Kevin! The best way to do this would be from the Catalog. Choose the schema that you're hoping to add, add a Collection to one of the tables, and drag down to apply to all the other tables. See video below!

Sure, but thats manual... I would like to not have to do that every time we add a resource to the schema. Similar to how permissions work at the schema level.

Ah I see! This isn't currently possible, but I would definitely recommend adding it as a request in our feedback board <http://feedback.secoda.co|here>.

Sounds good, just wanted to make sure I wasnt missing a way to do that...thanks!

I believe the limitation here is that our system looks at the domain of the email first, and if there are no Allowed Domains set up in your workspace, and the user hasn't been explicitly added by their email, it will redirect them to a new workspace.

This logics ensures that not just anyone with a link can join the workspace, but let me see what we can do to toggle the logic on and off!

Screenshot 2023-10-27 at 12.49.33 PM.png

For additional context, here is where you can find Allowed Domains for your workspace.

Ok, that makes sense. Perhaps in place of that an email could be issued to admins when a new user join with the link. If that logic is toggled off.

Speaking of creating users... can you confirm its still not possible to create users via the API with a group? Docs show only Teams.

We just updated our docs for <https://api.secoda.co/api/schema/redoc/#tag/User-Groups|User Groups>. It would be two API calls - one to <https://api.secoda.co/api/schema/redoc/#tag/Users/paths/~1user/post|create the user>, and <https://api.secoda.co/api/schema/redoc/#tag/User-Groups/paths/~1auth~1group~1%7Bid%7D/patch|another to add them to an existing user group>.

PS the ticket for tracking improvements to the email domain logic can be found <https://feedback.secoda.co/feature-requests/p/workspace-invite-link-for-unrecognized-email-domains|here>. I'd recommend upvoting it to stay up to date!

This appears to happen across multiple endpoint types. user, collections etc

Hi Kevin! Can you share the full URL that you're sending the request to? As well, are you using Postman, a curl request, or running a script?

Sure, python....

```import json
import requests

payload = json.dumps({
  'first_name': 'Sample',
  'last_name': 'User',
  'email': '<mailto:sample@sample.com|sample@sample.com>',
  'teams': [
    'e8ac09ed-e51e-4e61-8eaf-59942c98c260'
  ],
  'role': 'Viewer',
  '_role': 'Viewer'
})

response = <http://requests.post|requests.post>("<https://api.secoda.co/user>", headers={"Authorization": f"Bearer {token}", "content-type": "application/json"}, json=payload).json()```

Silly thing that we've found with Django (the framework we use for our API development) is that there needs to be a backslash at the end of the URL -
`<https://api.secoda.co/user/>`

We're in the process of fixing this but some endpoints still require that backslah to work! Sorry about this!

Hey Carlos, hope you're well! Appreciate the feedback. Just for clarity, was it the order of the columns or specific column names that aren't matching between the table headers and the show/hide selectors?

A specific column name...
• "Children count" on the table header
• "# of replies" on the column selector (screenshot shows both)

Hey Carlos, hope you've been well! Wanted to follow up here as there were some recent changes pushed for the catalog since our last conversation. Let me know if you're still seeing the issue on your end with column names not matching and I can share that with our team.

Hi! The issue remains... screenshot 1 with "# replies" off, and screenshot 2, with "#of replies" on. Notice how it toggles a field called "Children_count"... not "# of replies"...

No big deal to me, but thought your team would like to know.

Hey Carlos, hope you've been well! The team has been working on a new version of the catalog view which should resolve this. Will keep you posted on when this gets released. How has testing been in general? Any additional feedback would be appreciated as well!

Screen Shot 2023-11-27 at 3.11.31 PM.png

Hey Kevin, hope you're well! If you select the share button at the top right of the resource (above the properties), it will bring up a window where you can set permissions:

Got it, sorry for the dumb question. :upside_down_face:

No worries at all, definitely a valid question!

Screenshot 2023-12-15 at 5.31.44 PM.png

Thanks Matt! In general, if files are archived, you should be able to see them within the archived/trash window. If you click command+k, you should be able to scroll and see the "trash" option:

When you click Trash, are you able to see the resources there?

I don't see where that menu is, I don't have admin privileges on our account if that is needed.

If you click the *alt* or *command* key on your keyboard followed by the "k" key, this window should pop up

Should I be on a specific window for this to appear because it's not working for me

Nevermind, control+k is what made it work

And I was able to find the doc I needed! Thank you Prab. :thankyou:

<@U05P6TS86M9> Hello, hope you are doing well. Wanted to reach out because I have lost access to the archived record again and when I try to go to the trash I get redirected to <https://app.secoda.co/403> . Is this something you can help with?

Forgot to mention that I had my other teammates try to access the trash and they are met wit the same behavior.

Yep, can see the same on my end. If you try changing the url from 403 to archived instead at the end - does it load up for you then? Reaching out to the development team to take a look into this for us as well.

Negative, that sends me back to the 403 page

Just tested in our test workspace and it seems that the page is only accessible by "Admins". Was there a recent change to your specific account's role in Secoda?

Interesting, I never had admin access in the first place so not sure how I was able to access it last time. I'll check with my team to see if the admin can access it.

Actually, got some more context for us Matt. There was a recent change where the trash bin access was updated to admins only, however I'm having the team look into this for us. In the meantime, I would recommend having an admin restore the page/resource you're looking for so you're able to access it.

Thanks for the updated context Prab. I've done just that and am waiting for our admin to restore the page. Thanks again for your time and help!

Okay our admin tried to access the archive and it's just and empty page for them (they are not seeing the 403 url, just an empty page).

Appreciate the update Matt. Sometimes the page can take time to load up, if they click refresh, are they still not seeing the list?

Hmm, definitely odd. For context, what is the email of the admin accessing the archived page?

<mailto:Kevin.Bennett@us.panasonic.com|Kevin.Bennett@us.panasonic.com> and I will add him to this thread as well so he is in the loop (CC: <@U02739P8464>)

I just tested on our end and they do seem to be loading up. <@U02739P8464> could you also test in Incognito mode if possible?

First row should not show up considering the filter criteria I did on Description

Three tables with Description MOVE TO BRONZE should not show up as they were deleted and created in schema bronze. This is the view for gold schema

This flag is not activated and I synced from the source several times

Hey Sinisa, hope you're well! Just looking into this for us now.

Hey Sinisa, got an update for us here. I've created a ticket with the development team regarding the issue with the description filter. Seems like it's specific to the contains condition but works correctly if you set it to "Equals".

For the resources showing up even though they should be staled, have the team looking into that for us as well.

Hey Sinisa! Got an update for us regarding the description filter. In the example shared, its matching "to" in the description of the time_offset and since it has multiple "to"s, it gets boosted higher. Using the default condition is more of a full text search that matches "move" "to" "bronze" terms individually. The "equals" condition allows you to filter for exact matches.

OK. I understand this. It is not intuitive but has the logic.

What remains is the other issue where I still see the table even though it is deleted and multiple syncs to the source are conducted

Appreciate your understanding here Sinisa! The team is still working on the issue with staled resources being shown in the catalog. Will keep you posted.

Do I understand this documentation well? If the view DDL is referencing table A in the create view statement, this table A should be added to Related and Lineage tabs of the View resource?

Hey Sinisa! That is correct. You should be seeing "Table A" in the related tab for the view.

Hi Prab.

I am not seeing this, that is why I am asking.

My views in Redshift are (by request) created with clause *with* *no* *schema binding*

Is it possible I am not getting automatic Lineage because of that?

I basically did not get automatic Lineage for any of the views in my gold schema

Thanks for the additional context Sinisa! Going to check with our development team here to confirm whether the way the views are being created is leading to no lineage getting made.

Hey Sinisa, hope you're well! For context, do you have any specific examples of expected lineage? For example, if you could share the link to a view in Secoda and the resource to which you expect it to have lineage to (e.g. table, view)?

basically none of the views created automatic lineage

but you can take as the example *gold.channels*

```create view gold.channels as 
select  
 t.channel_id,
 t.channel_ref,
 t.channel_name,
 t.used_for_replay,
 rac.replay_ad_channel_name as replay_channel_name,
 rac.replay_ad_channel_group as replay_channel_group,
 rac.rap_channel_id as rap_channel_id
from 
 gold.channels_mediapro t 
 left join gold.replay_ad_channel rac 
 	on t.channel_ref  = rac.replay_ad_channel_code 
with no schema binding;```

I expect that there is lineage and dependency to the tables *gold.channels_mediapro* and *gold.replay_ad_channel* based on the DDL of this view

Did you maybe find something for this? If it can help you we can have a sync

Hey Sinisa, the team is still working on this for us. One quick question for you - are there any examples of views that don't have the no schema binding clause and are also not showing lineage or that are showing lineage?

Hi. All my views are no schema binding, as they are mostly taking data from spectrum tables.
I will now create the test view and sync Secoda, so I can check this example of the "normal" view and lineage

This is regular view on regular tables I created for the test now

```create view gold.test_view as 
select 
 p.*,
 rap.replay_ad_channel_name
from 
 gold.programs p 
 left join gold.replay_ad_channel rap 
 	on p.channel_ref = rap.replay_ad_channel_code```

I synced Secoda and I see no Lineage from gold.test_view to gold.programs and gold.replay_ad_channel. I also don't see any Related tables.

So it does not work also for normal views. It is at least what I can conclude from this test

The user I am using for the sync is super user, so it should have all the privileges needed to extract the info, I guess

Appreciate the additional context Sinisa! Sharing this with the team as well.

Hey Sinisa, hope you're well! Just wanted to follow up to confirm that the update that should correct this was deployed. If you could run another sync, please let us know if you're still seeing any issues with lineage for these views.

Hey Sinisa! I've got the development team taking another look into this for us, will keep you posted on what may be causing this.

Hi <@U05P6TS86M9> Is there a chance we try again to fix this? Next week I am presenting Secoda to the other Teams inside the company. Would be great if I can show the Lineage feature as it is important and they will ask me about it. If you can not solve it I will be forced to manually add Lineage which is quite the time intensive action for which I am not sure if I can dedicate the time

Hi Sinisa, completely understand and will be sharing this with the team. They are working on this for us and should hopefully be able to provide an update soon. As soon as I have confirmation that the fix has been deployed, will share that here.

Hi <@U067DSW0TU3>, I am currently looking into the lineage issue and I believe it comes down to permissions/access for the `secoda_user` that has been created.

Just following up my previous message, could you run the following commands from a superuser or a user with adequate privileges:

```GRANT USAGE ON SCHEMA &lt;schema_name&gt; TO &lt;user_name&gt;;
GRANT SELECT ON ALL TABLES IN SCHEMA &lt;schema_name&gt; TO &lt;user_name&gt;;```

I am confused. The user I am using in Redshift integration is a superuser

can it be that I am missing some privileges if I am using a superuser

Can you try running the two commands for the schemas you have selected?

I will now, but I see no point to give the privileges to a superuser

```GRANT USAGE ON SCHEMA bronze_spectrum TO secoda_user ; --spectrum schema
GRANT SELECT ON ALL tables IN SCHEMA bronze_spectrum TO secoda_user;

GRANT USAGE ON SCHEMA bronze TO secoda_user ;
GRANT SELECT ON ALL tables IN SCHEMA bronze TO secoda_user;

GRANT USAGE ON SCHEMA gold TO secoda_user ;
GRANT SELECT ON ALL tables IN SCHEMA gold TO secoda_user;```

No. I don't see lineage generated for the views based on DDL

Here is what I got - no lineage and no related populated

Still investigating, we use a number of _views_ from Redshift to pull lineage metadata, it seems that when querying `information_schema.view_table_usage`, we are not getting back any results

information_schema.view_table_usage definitely does not have all metadata. this is not a good candidate to pull the metadata from

for what I can check information_schema.view_table_usage is not storing info for "*no schema binding*" views

if you check the thread I told you 14 days ago that all my views are *with* *no* *schema binding*

the issue is for sure not related to privileges as I made secoda_user a superuser 14 days ago as well and the issue was not solved

We initially were using a combination of `information_schema.views` and `information_schema.view_table_usage` but for your workspace when querying `information_schema.views` it does not return the *Query Definition*

We switched to `<http://pg_catalog.pg|pg_catalog.pg>_views` to work around this. That is why I was under the impression of it being some privilege issue.

Can you try querying  `information_schema.view_table_usage` does it yield any results at all?

it returns the result for the views which are created without the option "no schema binding". These views are not in the schemas I am loading with Secoda, as all my views I am loading to Secoda are with option "no schema binding"

so this is not returning the result

```select * from information_schema.view_table_usage
where view_schema = 'gold' and view_name = 'channels'```

but this is returning the result

```select * from information_schema.views
where table_schema  = 'gold' and table_name = 'channels'```

can you run this query in a query block in secoda:
```select * from information_schema.views
where table_schema  = 'gold' and table_name = 'channels'```
and see if you are getting a view_definitioin

are you currently logged in as `secoda_user` in your sql query program

<https://stackoverflow.com/questions/61103449/redshift-view-definition-permissions-issue>

this with show view works also for the views where user is not the owner, as said in this stack overflow link

We will create a ticket to come up with a workaround to parse the View Definition to determine the lineage.

Thank you Sonam. Please share if you know how much does it take for the workaround? Based on this info I need to decide if I am doing this presentation or I wait. Thank you for your support

Hey Sinisa, once I have some more context on the ETA to get this updated will follow up here! Either way I'll provide an update by tomorrow on whether we're able to get this completed before next week. To confirm, what day were you thinking of presenting?

Hi. I have presentation to onboard new teams to Secoda Thu next wek

Hey Sinisa! Quick update - the team was able to identify the issue and the update is just under review. As soon as I have confirmation that this has been deployed. If not by end of day, this should be deployed over the weekend.

Hi Prab. Is the update release? Should I try again?

Hi Sinisa, hope you're well! The update was released over the weekend. If you could run a sync for the redshift integration first, that would be great! Will keep an eye out of for the sync completion as well to then confirm whether lineage now shows.

I see now the relationships from the views

Awesome! Thanks for confirming Sinisa. If there's anything else we can help with, please let us know.

Hey Dallin, hope you're well! Just taking a look into this for us now.

Thanks for the screen recording Dallin, was definitely helpful! I wasn't able to directly replicate this in our test workspaces. If you test this out in Incognito mode on your browser, are you still seeing the same issue?

Yep still happening in incognito mode, and multiple people have said this is happening on their accounts from our company

I tried restarting and updating our secoda instance but that didn't fix the problem

Appreciate the context! Just reached out to our development team to look into this as well. Did this just start occurring today? Also which version of Secoda are you currently on?

Quick question Dallin, if you open up the chrome dev tools (right click and inspect in chrome), are you seeing any errors in the Networks tab when loading the resource?

Okay so no but the weird part of this is that while dev tools is open I can still see the table, but when I close it out the screen goes white again like the video. I can accomplish the same thing if I open the table with chrome on half the monitor, but when I stretch it back to a full size window then it goes blank again

So seems like some kind of front end bug where if window size is full then the data disappears, but it still is able to show with a smaller window size

Appreciate the additional troubleshooting Dallin! This context is great. Shared this with the team and created a ticket for this as well. Will keep you posted on any new updates from the team.

Hey Dallin! Just wanted to reach out and confirm that this should now be resolved with the latest version that was released. Please let me know if you're still seeing any issues on your end after updating and I will share that context with the team.

Looks like its working now properly! Thanks!

The description of the columns for one view shows empty but it has the content defined in last week. Is there a way to retrieve it?

Can you share the name of the View that you don't see the column descriptions for anymore?

Sent you a DM <@U02H1V13V99> to continue working through this :blush:

Hey Kevin, hope you're well! For context, if you don't click the enforce SSO option, users should still be able to log into the workspace using their emails. This should allow you to setup the SSO and test logging in without causing any issues with login for users. Is that an option that works for you or are you looking to enforce SSO login during the testing phase as well?

Got it, so if SSO is configured both login mechanisms work until its "enforced"

Yep, exactly! This will allow you to test in the actual workspace and ensure everything is setup correctly.

HI Prab, I can see where the integration was added by you all, and it redirects me correctly to sign in, but on the call back I am getting a Server Error (500) response. In the SAML logs I can see where the login was successful from the IDP side.

Hey Kevin! Would you be able to share a screenshot of the exact error you are seeing?Also, just to confirm which specific SSO method are you using?

If we Turn Off the monitoring for the Monitor it simply ignores and continues to initiate queries after 5 minutes

also, as we use spectrum feature this constant running of queries from Secoda is increasing our cost of the infrastructure significantly

We changed the pass so secoda can not access Redshift anymore. It is unacceptable that Monitors are running every minute killing our cluster and increasing our cost of infrastructure

Hello <@U067DSW0TU3> we are currently deploying a fix for this issue and will let you know when it's been deployed. I apologize about this. Once we do a deeper investigation of the issue, we'll provide a more detailed explanation to you about what happened.

Hey <@U067DSW0TU3> we've temporarily disabled all monitors while we're investigating and fixing the issue. Again, apologies about this and we'll let you know when we have an update on the situation.

Thank you Andrew. I received the email communication you have sent

Have you also disabled the Sync option? I tried two times today to sync the Metadata from Redshift but it just went to Queue stage, it was not starting. At the end I terminated both attempts.

<@U067DSW0TU3> what domain and workspace are you accessing from? It should be running normally.

it works today. I just have tried. Yesterday it was not working. But all good now. Thanks

Has anyone reported not having normal menu options today?

Context, there is no options on resources in the top right like there should be

Hey <@U02739P8464> are you able to share the broader context here. What page is this on?

This is on a tables page, there is no option to publish, edit security etc

If you click on the "i" icon it'll show all of this metadata.

Can you share the URL of the page you're accessing