Hi @gsmith ,
thanks, but not entirely sure what you’re getting at with your reference to the Changelog.
In my case the Changelog does not even list the removal of the /api/sources endpoint, much less point to a functional equivalent. Why remove functionality that doesn’t hurt anybody and satisfies a need (else why would there be a GUI equivalent still existing), but no replacement?
I’ve found an older thread for the same issue, but this refers to the GUI dashboard only as well.
Is there no way to get the same information programmatically instead of paying eyeballs to look at a fancy dashboard? I thought that’s why computers were invented, to minimize routine tasks for humans…
The thread above says that “it’s simply a search, therefore /api/sources is redundant”, which is all well and good, but I have not found a way to properly access search results via API. I can construct a search and submit my search request to the API, but only a reference to a result set is returned and I fail to see how I can access the actual results and transform the output into a format roughly equivalent to the former output of /api/sources. I think this is what I’m missing at the moment.
I’ve asked a somewhat broader question because I’m not actually hung up on parsing this specific information in this specific way. If anybody has got another way of monitoring (active) sources or their dropping out of the Graylog instance without anybody manually clicking in the Graylog GUI, I’m all ears. That’s all I need/want.