SenseOn Log Ingestion - FAQ and Quick Reference
Quick Reference
| Method | Destination | Notes |
|---|---|---|
| Syslog over TLS | <code-name>-logs.senseon.io, TCP 6514 |
On request. Octet-counted framing, standard syslog header. |
| JSON over HTTPS | https://<code-name>-logs.senseon.io/, TCP 443 |
On by default. One object or one array per request. |
| OpenTelemetry | <code-name>-logs.senseon.io, TCP 4317 or 4318 |
On request. Logs and metrics. |
| Azure Event Hubs | SenseOn pulls from your Event Hub | Nothing to send |
Connect by hostname with TLS 1.2. The Configuration Overview page gives the full list of rules.
Quick tests:
# Syslog over TLS
openssl s_client -connect <code-name>-logs.senseon.io:6514 \
-servername <code-name>-logs.senseon.io \
-verify_hostname <code-name>-logs.senseon.io -verify_return_error -brief </dev/null
# JSON over HTTPS, expect 200
curl -X POST https://<code-name>-logs.senseon.io/ \
-H "Content-Type: application/json" -d '{"test": "connection"}'
The openssl test needs OpenSSL 1.1.1 or later. The openssl that macOS includes is LibreSSL, which does not support -verify_hostname or -brief. On macOS, install OpenSSL, for example with Homebrew, and run that openssl.
Frequently Asked Questions
Q: How do I get my ingestion endpoint?
A: SenseOn gives you <code-name>-logs.senseon.io during onboarding. There is a hyphen before logs.
Q: SenseOn gave me an endpoint that ends in snson.net. Which do I use?
A: <code-name>-collector.snson.net is from an earlier version of the platform. Continue to use it with its original settings until SenseOn asks you to move.
Q: What log format does SenseOn need?
A: For syslog, send the format of the device (for example key-value, CEF or LEEF) in a standard syslog message. Do not convert it to JSON. For HTTPS, send any JSON object. If possible, include a timestamp and a source field. Refer to Recommended Format.
Q: Can I batch JSON logs?
A: Yes. Send the logs as a JSON array. Each element becomes one record. If a request has newline-delimited JSON with more than one object, the endpoint rejects it with HTTP 400.
Q: Can several sources share the endpoint?
A: Yes. For JSON, add a source field. This field shows which source sent each log. For syslog, the hostname and the application name in the header do this.
Q: My device can only send to an IP address, or my firewall only allows rules by IP. What are my options?
A: If the device supports TLS, ask SenseOn for a dedicated port that only your fixed egress IP addresses can get to. If not, send through a relay in your network. Refer to Devices that cannot send to a hostname.
Q: Which FortiGate versions can send directly?
A: FortiOS 7.4 sends SNI, and it sends directly to port 6514. FortiOS 7.2 was seen to send syslog with no SNI. Thus this version must use a dedicated port or a relay. For other versions, run the quick test from the network of the firewall. Then send from one firewall first.
Q: What network access do I need?
A: You must have outbound TCP to the hostname on the port for your method (6514, 443, 4317 or 4318), or to your dedicated port. There must be no TLS inspection on the path. For Azure Event Hubs, SenseOn connects to your Event Hub, so you do not open outbound access. If the namespace has firewall rules, allow the SenseOn egress addresses. Refer to Azure Event Hub.
Q: Is my data encrypted in transit?
A: Yes. All methods use TLS between your senders and SenseOn. With a relay, the traffic from your devices to the relay can be plain syslog in your network. Keep that traffic on a management network. The relay forwards to SenseOn over TLS.
Q: How do I test my setup before I send all my logs?
A: Run the quick tests in the Quick Reference section. Then send from one device. Ask SenseOn support to tell you if the data arrived. Add the other devices only after SenseOn support tells you that the data arrived.
Troubleshooting
Q: The connection is reset straight away.
A: On the shared ports, this means that the sender does not send SNI. The sender connects to an IP address, or its TLS library does not set the server name. Use the hostname. As an alternative, ask for a dedicated port.
For rsyslog, use the gtls driver, because the ossl driver in many releases sends no SNI. On 6514, the reset can also mean that syslog is not on for your organisation yet. On a dedicated port, a timeout or reset usually means that your logs leave from an address that SenseOn does not have.
Q: The syslog connection opens, then drops after I send messages.
A: Make sure that each message starts with a <priority> header. The usual cause is a custom template that starts lines with a timestamp.
Q: Fluent Bit returns HTTP 400.
A: Set Format json on the HTTP output, not json_lines. json_lines sends newline-delimited JSON, and the endpoint rejects it. Then make sure that the log shows HTTP status=200.
Q: The certificate is not from Let's Encrypt.
A: A proxy on your network inspects TLS. Exclude <code-name>-logs.senseon.io from inspection.
Q: Connections time out.
A: Examine these items:
- Outbound access on the port for your method
- DNS resolution for the hostname
- Any proxy on the path
On a dedicated port, make sure that your logs leave from an address that SenseOn has.
Q: My logs still do not appear.
A: Contact support@senseon.io. Send this information:
- Your organisation name
- Your ingestion hostname
- Your method
- The log source and its version
- Sanitised example logs
- Error messages
- When the problem started
- Your configuration files
Q: Can I send logs from AWS, Google Cloud or Azure?
A: Yes.
- AWS: Use a forwarder Lambda. Refer to AWS CloudTrail and CloudWatch.
- Azure: Use diagnostic settings to send logs to an Event Hub. Refer to Azure Event Hub.
- Google Cloud: Send logs from Cloud Logging to Pub/Sub. A Cloud Function then posts the logs as JSON. Refer to Configuration Examples.