#extended process list?
1 messages · Page 1 of 1 (latest)
hi @broken relic , this isn't possible at the moment but we are really close to get a new feature out called Functions 🙂
you can already see the docs up https://learn.netdata.cloud/docs/nightly/concepts/netdata-functions
dammit, would be nice to have it now :/
ofc 
but nice
@mystic kestrel i think there is a bug in the ui
but it's nice, we didn't have issues now when i needed it.. but now it's nice to see actually
it is a side effect of something we did on the tables for functions and other feature to come out soon
we'll be polishing these out
on functions once you had a chance to try it with actual needing let us
would love to hear first-hand usage feedback
and if you have ideas of functions that could be useful to you also let us know
i will show my co-workers it tomorrow
trying to think what could be cool to get
@mystic kestrel on the UI part, maybe some auto fit columns width?
i'm hiding the filter list to not get scroll, but then it could be nice to click somewhere to auto fit all columns
like double clicking rows in excel
yes, that would be nice
it's a small thing
will keep a list of additional useful stuff, we also want to allow users to define more freeze columns, have a way to export the data from the table
hmm, i can't think of anything that functions could do.
maybe i don't 100% understand it's functionality
compared to metrics & dashboard
we have some ideas already:
- get slow queries from a DB collector, like PostgreSQL
- allow to trigger some action on the node, maybe even a netdata agent update on request
ah, that's a good point
netstat command also came up
ohhhh
I've got a huge thing
actually
i know it would require a "bit" from your side
but have it with history in it
e.g. the processes right now, i would need to identify which process at a certain time that is doing something
e.g. in the middle of the night when we sleep and the server is crunching away
so that should be active
that is more tricky, not saying we won't go there, but this is actually getting data in runtime
we don't store any datapoints/history from this
i kinda knew that
we just fire a request from Cloud to the Agent specific collector to be executed
ya, makes sense
but e.g. on cpu chart i could see at 3 am for example, the cpu was going crazy
would be nice to go back on the process list to see which process
yes, definitely we thought about that use-case but we decided to not go that path yet
i hope it will be added