-
Notifications
You must be signed in to change notification settings - Fork 138
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
How to connect to Data Node to fix long messages not logged #61
Comments
@ili101 Hi, this is not so easy to accomplish. Is this a blocker for you? There are changes in the upcoming bugfix release for the DataNode and some more in 6.0 in that area that will help with making the type of changes you linked to. |
Also, the 32k limit and how to "solve it" seems a bit controversial. Maybe you can solve this completely different? |
Hi @janheise Unfortunately, as I can see all solutions to save more than 32k involve editing the settings with that API one way or another. |
@ili101 I hope it's not a misunderstanding: as far as I know, there is no solution to save more than 32k - it's only the question who cuts and ignores the rest. Personally, I think if you can cut it before putting it into the input, that is preferred because that means you are in control. |
No, it saves the whole thing but doesn't let you search on its content. So you need to find the record by another field and then you get the whole content. |
Hello. Can you give me a hint, please? |
Hi, I want to try to apply one of these solutions, for example, Graylog2/graylog2-server#873 (comment).
Using the "open-core" compose and default configurations on setup.
How do I connect to the Data Node to apply the fix? If I for example
curl -k -X GET "https://localhost:9200/_cluster/health?pretty=true"
I get "Authentication finally failed". Do I need to extract the certificate to connect or something similar? help appreciated.The text was updated successfully, but these errors were encountered: