#zincobserve

Troubleshooting Postman Request for ZincObserve

TLDR Juan experienced a "bad formarted" error using Postman with ZincObserve. vvv suggested checking headers and input. Prabhat advised using ZincSearch for non-log data.

Join the chat

May 09, 2023 (3 weeks ago)

Photo of md5-4b9e24e8a61417b7f4e7553444c6b367

Juan

05:02 PM

Hello everyone, i'm tried to indexing information to my organization, but when i send the request post by postman, the api retunr to me an error 500 and the text bad formarted so i don't undertand anything.
Someone can tell me that i do wrong

Thank you so much

Image 1 for Hello everyone, i'm tried to indexing information to my organization, but when i send the request post by postman, the api retunr to me an error 500 and the text bad formarted so i don't undertand anything.<br>Someone can tell me that i do wrong<br><br>Thank you so much

Image 2 for Hello everyone, i'm tried to indexing information to my organization, but when i send the request post by postman, the api retunr to me an error 500 and the text bad formarted so i don't undertand anything.<br>Someone can tell me that i do wrong<br><br>Thank you so much

Photo of md5-d70e3e1ae67062469c9fea6f2a5357a3

vvv

05:22 PM

Hi Juan,
That gibberish in the response is indeed confusing. Maybe a look at the Headers can provide some clues on why you are seeing those bytes?

05:22

vvv

05:22 PM

I tried to send a similar POST request to my local ZincObserve server started with cargo run. This is what I got:

Image 1 for I tried to send a similar POST request to my local ZincObserve server started with <code>cargo run</code>. This is what I got:

05:25

vvv

05:25 PM

The injest API (/_json) expects an array of objects as its input.

After I changed the input accordingly, the request succeeded:

Image 1 for The injest API (<code>/_json</code>) expects an array of objects as its input.<br><br>After I changed the input accordingly, the request succeeded:

Juan

05:30 PM

vvv

05:31 PM

Code links:
• /_json API endpoint
• the line that fails — we can see here that ZincObserve tries to parse JSON input into a Vec. This fails unless the input is a JSON array.

Juan

05:32 PM

I tried to do what you did but it doesn't work

05:41

Juan

05:41 PM

Can you explain me how i can use ZincSearch in my local

vvv

05:44 PM

See https://docs.zinc.dev/ZincObserve/quickstart/

Photo of md5-23052f31f8f3c4b1bb3297fbc3a2aec5

Prabhat

10:25 PM

Juan Looks like you are also trying to index non log data for indexing and search. Your use case appears to be suited for ZincSearch as opposed to that of ZincObserve. You should look at the documentation of ZincSearch instead - https://zincsearch-docs.zinc.dev/quickstart/

ZincObserve

ZincSearch is the simplest and easiest search system to get up and running. An open source easy-to-use search engine to solves your observability needs | Knowledge Base powered by Struct.AI

Generate Knowledge

Similar Threads

_search API Authentication Issue in Zinc Cloud

Ivan encountered an authentication error while using the _search API. Ashish clarified API limitations and Prabhat suggested using ZincSearch for their use case.

Troubleshooting Zincobserve Upload Error

Simon encountered a 500 error when uploading logs to Zincobserve. Hengfei suggested using `--data-binary "@demo.log"` instead of `-d`, which resolved the issue.

Troubleshooting ZincCloud API for Search Requests

Edicius is having issues making Search API requests using ZincCloud, and Prabhat informed that it is only possible with ingestion API endpoints but will be available soon.

1mo

Issues with Timestamp Format in Zinc-Observe API Query

Rex faced an issue with the timestamp format in Zinc-Observe API query. Hengfei pointed out that start and end times should be in i64 and in microseconds as per the search document.

3mo

Integrating ZincObserver and Resolving Log Issues

sparrow faced issues with ZincObserver integration, log filtering, and missing logs. Ashish and Hengfei provided solutions, including using str_match and an updated image. A future release will provide more error responses for ingestion.

2mo