You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey. Great to have a greylog running in our setup. Would be great to use it for error logs directly from the app running - so that we can improve the App without depending on user feedback alone.
I started to implement that: I created an input on greylog - see "System > Inputs" called "App Error Reports". Its listening already on port 12185 and I opened up the port on azure.
I think its because the port is not routed to the correct docker container - didnt wanted to mess something up, so it would be great if can get this port open and the API call working.
If we get to this point, then it would be great to have a skype to discuss the structure of the error data send by the app, to get the best results out of it. Not a high priority, bit would be great to have this working.
The text was updated successfully, but these errors were encountered:
Hey. Great to have a greylog running in our setup. Would be great to use it for error logs directly from the app running - so that we can improve the App without depending on user feedback alone.
I started to implement that: I created an input on greylog - see "System > Inputs" called "App Error Reports". Its listening already on port 12185 and I opened up the port on azure.
But I dont get a respose to a POST call with Potman to:
http://fourcores2016.cloudapp.net:12185/gelf
I wanted to follow this tutorial: http://docs.graylog.org/en/2.1/pages/sending_data.html#gelf-via-http
I think its because the port is not routed to the correct docker container - didnt wanted to mess something up, so it would be great if can get this port open and the API call working.
If we get to this point, then it would be great to have a skype to discuss the structure of the error data send by the app, to get the best results out of it. Not a high priority, bit would be great to have this working.
The text was updated successfully, but these errors were encountered: