Acknowledgements
Describe the bug
We installed UTMStack v10.9.4 on one instance and v11.2.6 on a separate instance. We identified an issue with the JSON Inputs integration that prevents log forwarding on the newer version, even when using the examples provided in your documentation.
Regression Issue
Expected Behavior
The /v1/logs endpoint should accept POST requests containing a JSON array of log entries and return a 200 status with {"status":"received"}, as it currently does on v10.9.4. Both versions should behave consistently when receiving logs through the JSON Inputs integration, regardless of the payload content or log source configuration.
Current Behavior
On v11.2.6, the same POST request to /v1/logs returns a 404 page not found error, indicating the endpoint is either missing, renamed, or no longer exposed on the expected port. No logs are ingested, and no additional error details are provided in the response body.
Reproduction Steps
Send logs using Python requests library
import requests
import json
Define the URL
url = "https://site1.selfsign:8080/v1/logs"
logs = [] # Replace with your actual log data
payload = json.dumps(logs)
Define headers
headers = {
'Utm-Connection-Key': 'Connectionkey==',
'Utm-Log-Source': 'your log source (mandatory header)',
'Content-Type': 'application/json'
}
Make a POST request
response = requests.request("POST", url, headers=headers, data=payload)
Print the response
print(response.text)
Possible Solution
No response
Additional Information/Context
Below are the terminal outputs from both instances for comparison:
v11.2.6 — site1.selfsigndsite (failing)
Sending 3 logs to https://site1.selfsigndsite:8080/v1/logs ...InsecureRequestWarning: Unverified HTTPS request is being made to host 'site1.selfsigndsite'.UTMStack response: status=404, body=404 page not foundUnexpected server response: 404
v10.9.4 — site2.selfsigndsite (working)
Sending 3 logs to https://site2.selfsigndsite:8080/v1/logs ...InsecureRequestWarning: Unverified HTTPS request is being made to host 'site2.selfsigndsite'.UTMStack response: status=200, body={"status":"received"}Logs sent successfully!
UTMStack Version
11.2.6
Operating System and version
Ubuntu 24.0.4
Hypervisor and Version | Server Vendor and Model
Any
Browser and version
Any
Acknowledgements
Describe the bug
We installed UTMStack v10.9.4 on one instance and v11.2.6 on a separate instance. We identified an issue with the JSON Inputs integration that prevents log forwarding on the newer version, even when using the examples provided in your documentation.
Regression Issue
Expected Behavior
The /v1/logs endpoint should accept POST requests containing a JSON array of log entries and return a 200 status with {"status":"received"}, as it currently does on v10.9.4. Both versions should behave consistently when receiving logs through the JSON Inputs integration, regardless of the payload content or log source configuration.
Current Behavior
On v11.2.6, the same POST request to /v1/logs returns a 404 page not found error, indicating the endpoint is either missing, renamed, or no longer exposed on the expected port. No logs are ingested, and no additional error details are provided in the response body.
Reproduction Steps
Send logs using Python requests library
import requests
import json
Define the URL
url = "https://site1.selfsign:8080/v1/logs"
logs = [] # Replace with your actual log data
payload = json.dumps(logs)
Define headers
headers = {
'Utm-Connection-Key': 'Connectionkey==',
'Utm-Log-Source': 'your log source (mandatory header)',
'Content-Type': 'application/json'
}
Make a POST request
response = requests.request("POST", url, headers=headers, data=payload)
Print the response
print(response.text)
Possible Solution
No response
Additional Information/Context
Below are the terminal outputs from both instances for comparison:
v11.2.6 — site1.selfsigndsite (failing)
Sending 3 logs to https://site1.selfsigndsite:8080/v1/logs ...InsecureRequestWarning: Unverified HTTPS request is being made to host 'site1.selfsigndsite'.UTMStack response: status=404, body=404 page not foundUnexpected server response: 404
v10.9.4 — site2.selfsigndsite (working)
Sending 3 logs to https://site2.selfsigndsite:8080/v1/logs ...InsecureRequestWarning: Unverified HTTPS request is being made to host 'site2.selfsigndsite'.UTMStack response: status=200, body={"status":"received"}Logs sent successfully!
UTMStack Version
11.2.6
Operating System and version
Ubuntu 24.0.4
Hypervisor and Version | Server Vendor and Model
Any
Browser and version
Any