Srikanth Chekuri

Closing this since we main EPIC.

Merging with https://github.com/SigNoz/signoz/issues/5955

I don't see any immediate concerns with this approach. Since there is one workflow for each lang would it be possible to do this in main branch itself?

> I am more inclined towards having certain parts integrated into OTel and certain parts be in an independent repository. What parts do you think should be reside in this...

Probably I am missing something, How does this bloat up the spec? I can understand it will be a maintenance burden to official SIGs but that can be managed by...

Thanks for linking Yuri's comment, Now I understand what&where you meant by bloat. @aabmass what are your thoughts on this?

We could enrich it more info using utilities from contrib repos (ex: asgi/wsgi helpers to add route details for every framework instead of just flask). If the both sqlalchemy commenter...

Sounds good. It would be lot easier this way than dealing with virtualenvs and installing db on local machine.

Did we ever directly communicate with the users via some notification that we are deprecating these? This change should be preceded by identifying the views/dashboards/alerts that used the deprecated columns...

We don't support windows