Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

message field is empty #42

Open
sergiotocalini opened this issue Feb 13, 2020 · 6 comments
Open

message field is empty #42

sergiotocalini opened this issue Feb 13, 2020 · 6 comments

Comments

@sergiotocalini
Copy link

I've been using this solution for a while now and I have an issue on the logs shipped to logz.io, I cannot see the data in the message field, this is empty, but in all the rest of the field are filled (e.g. resourceID). Do you know how can I fix this issue?
Thanks in advance

@idohalevi
Copy link
Contributor

@sergiotocalini are you sure you have message field in the log? Kibana will always show it on the Discover page. If it's empty or doesn't exist Kibana will show an empty message field

@sergiotocalini
Copy link
Author

@idohalevi
Thanks for your reply.
Exactly that is the whole point, there is no message field on the log and I am trying to use Grok to parse some data and it is always based on the message field. Can you please help me with this or give me a grok example for no message field on logz.io?
Thanks in advance

@idohalevi
Copy link
Contributor

@sergiotocalini you can contact support and they will do the parsing for you. It's part of our service :)

@sergiotocalini
Copy link
Author

@idohalevi Thanks for the clarification.
I was trying to change the function on azure to provide the information on the message field but I will contact the support team then and see how can I solve this issue then. Because I would like to have the flexibility to do it by my own otherwise we will have to analise another solution like ELK.
Thanks for your support

@idohalevi
Copy link
Contributor

@sergiotocalini you can choose either way. This project is an open-source one so feel free

@Doron-Bargo
Copy link
Contributor

Hi @sergiotocalini - is this issue still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants