TLDR Kaushik asked the community's preference on where to incorporate '_*Saved Views*_' under. Dave prefers the latter option, not wanting to sacrifice screen space. Pranay acknowledged the feedback.
Hey everyone, my name is Kaushik and I lead Product Design efforts at SigNoz. We recently started exploring _*Saved Views*_ feature in Traces and Logs, helping the users to create different page views with the Query builder. We are interested in learning if _*Saved Views*_ is really important for you and if yes how frequently would you create views ?
We are currently looking at couple of solutions:
a. Saved views as a secondary Nav under Traces and Logs (this solution would be great if you use and create views very often)
b. Saved views under the dropdown, users can directly run queries or select a view from the dropdown (this solution would be great if you use and create views once in a while)
We are collecting our dev, test, acc and production environment in one signoz environment; in graylog we have saved queries to quickly make right section per environment and microservice. This helps a lot to avoid repeativiness where you always want to narrow down on an environment.
personally i love option 2 more so not sacrificing screen space
thanks for the feedback Dave
Indexed 1061 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI