<!channel> I am looking for pointers/expectations ...
# general
s
<!channel> I am looking for pointers/expectations regarding infrastructure monitoring and how we can build that part of the product to offer maximum value to you all. If you are setting up o11y for your infrastructure and resources, what are the most common things you'd look for to be available out of the box? The idea being you, as the user, should be able to quickly get insights and data without having to spend a lot of time sitting and configuring a bunch of dashboards or alerts on SigNoz. What are the relevant data points you'd want to explore and play with quickly?
i
just fyi, there are 5,079 users in this channel. When you do at channel, all of them get a notification
oh sorry, you're asking for user feedback:) my bad
t
@Shuvam Manna Default dashboards, or import of Grafana Dashboards
k
yes, import/translation of grafana json would be amazing
r
Honestly, ability to automatically provision dasboards and alerting rules by dropping configuration files into some directory structure would be awesome — this is how you auto provision the entirety of Grafana and Alertmanager on Kubernetes - by mounting configmaps to container volumes.
c
I just recently posted in the channel about this but extracting/flattening nested json to attributes dynamically. Both cloud watch and honeycomb do this without any upfront configuration and you can then access nested parts of the json string like
attributes.body.orders.[4].order_date
etc. This allows us to decouple developer log outputs from pipeline processors to map json fields to attributes. Instead developers are free to enrich json logging with new fields without us having to add more mappings etc https://docs.honeycomb.io/send-data/logs/structured/json/ https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CWL_AnalyzeLogData-discoverable-fields.html#CWL_AnalyzeLogData-discoverable-JSON-logs
v
CC: @nitya-signoz Feedback on logs