TLDR dch asked about adding syslog-ng as a source for OpenObserve. Prabhat confirmed it possible, explaining it uses OpenObserve's _bulk API, and provided relevant resources. dch also asked about handling demo and real events in OpenObserve's cloud, which Prabhat explained. Mark mentioned working on an openobserve native syslog-ng destination.
syslog-ng supports sending data to elasticsearch using _bulk API. The same can be used to send data from syslog-ng to OpenObserve
thanks - is the API then?
and I would need to align syslog-ng format with that?
like so,
Yes.
also
this the_bulk API in OpenObserve
ok thats an excellent find - zinc was the old product name?
yes we built zinc earlier and then built OpenObserve
ok cool so you kept the external api and what you learned, and moved it to rust + sled. nice.
yes. We applied things we learnt with zinc in OpenObserve building it specifically for observability as opposed to a general purpose text search tool.
ok, that url from syslog-ng team works perfectly.
what I am not sure on, is how to delete the "Demo Organisation" in my cloud dashboard, and for the events to go into the custom organisation I created
but at least we have events now
oh,
no these are just "demo" events, not real ones.
> what I am not sure on, is how to delete the "Demo Organisation" in my cloud dashboard, and for the events to go into the custom organisation I created Are you using OpenObserve cloud or self hosted ?
in cloud its just demo data
You should ingest data in your own org
and change org accordingly.
I think we should have one more entry for syslog-ng just like filebeat and others
you can copy the details from filebeat for now for syslog-ng
I’m also working on an openobserve native syslog-ng destination; early progress is very promising. Basing it on the (very capable, and OSS) Splunk Connect for Syslog, which does a wonderful job classifying data — which makes querying on openobserve a breeze.
dch
Fri, 30 Jun 2023 07:51:44 UTCare there plans to support syslog-ng as source?