Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
×
Join the Conversation
Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
- Find Answers
- :
- About jeffa2
jeffa2
Explorer
Member since:
06-15-2023
07-27-2023
Community Statistics
| Posts | 9 |
| Solutions | 0 |
| Karma Given | 2 |
| Karma Received | 0 |
| Member Since | 06-15-2023 |
Activity Feed
- Posted Re: Why can't I add an event to HEC in my splunk cloud trial env? on Installation. 07-27-2023 12:53 PM
- Posted Re: Why can't I add an event to HEC in my splunk cloud trial env? on Installation. 07-24-2023 04:38 PM
- Posted Re: Why can't I add an event to HEC in my splunk cloud trial env? on Installation. 07-24-2023 06:35 AM
- Posted Re: Why can't I add an event to HEC in my splunk cloud trial env? on Installation. 07-21-2023 07:55 AM
- Posted Why can't I add an event to HEC in my splunk cloud trial env? on Installation. 07-18-2023 07:13 AM
- Posted Re: Trying to use the Splunk OTEL collector on Linux, TOKEN is not working on Splunk Observability Cloud. 06-20-2023 05:33 AM
- Karma Re: Trying to use the Splunk OTEL collector on Linux, TOKEN is not working for bishida. 06-20-2023 05:33 AM
- Karma Re: Trying to use the Splunk OTEL collector on Linux, TOKEN is not working for bishida. 06-20-2023 05:33 AM
- Posted Re: Trying to use the Splunk OTEL collector on Linux, TOKEN is not working on Splunk Observability Cloud. 06-15-2023 08:27 PM
- Posted Re: Trying to use the Splunk OTEL collector on Linux, TOKEN is not working on Splunk Observability Cloud. 06-15-2023 08:24 PM
- Posted Trying to use the Splunk OTEL collector on Linux, TOKEN is not working on Splunk Observability Cloud. 06-15-2023 04:44 PM
Topics I've Started
07-27-2023
12:53 PM
I've reached the conclusion this is in fact some kind of network rule on our end, stopping TLS traffic to non-standard ports (443/8443). The team hasn't figured out what rule to modify. I know I can't change this port number in my trial account, but would someone be able to change port 8088 to port 8443 for me?
... View more
07-24-2023
04:38 PM
Do you know of any kind of network security/firewall rules in place in the trial environment that could cause connection issues?
... View more
07-24-2023
06:35 AM
Thanks for the ideas! Nslookup on both of these hosts worked: inputs.prd-p-ki5a7.splunkcloud.com prd-p-ki5a7.splunkcloud.com ...And this command worked fine against both on my ordinary network: curl -k https://<HOST>:8088/services/collector/event -H "Authorization: Splunk <TOKEN>" -d '{"event": "hello world"}' ...but from within my virutal environment from inside a VM, I am still getting this: curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to inputs.prd-p-ki5a7.splunkcloud.com:8088 Is there a way to turn off SSL in the trial environment? Or is there/would it be a different port number? Thank you! Jeff
... View more
07-18-2023
07:13 AM
hello! I am getting an error trying to add a "hello world" event into my splunk cloud trial environment. I'm looking for help to see what the issue could be. I am getting what looks like an SSL error. I added certs to my ubuntu VM but that didn't seem to help. Maybe it's a network fw error of some kind? Is the IP source of my env somehow blacklisted on your end? Not certain but think it could be the case, maybe you can help me?
In my virtual network, I can connect fine from my VM... here's a simple connection:
sudo telnet prd-p-ki5a7.splunkcloud.com 8088 Trying 44.206.98.245... Connected to prd-p-ki5a7.splunkcloud.com.
When I try this curl command …
curl -k https://prd-p-ki5a7.splunkcloud.com:8088/services/collector/event -H "Authorization: Splunk <token> -d '{"event": "hello world"}'
…I get this:
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to prd-p-ki5a7.splunkcloud.com:8088
...however if I try it on a different network, it works fine. Any way you can help me troubleshoot this one?
... View more
06-20-2023
05:33 AM
I revoked right after posting 😉 thank you for the help with this!!
... View more
06-15-2023
08:27 PM
oh wait, I think I see what you're saying! I changed to ingest token and it's working now... thank you!!!
... View more
06-15-2023
08:24 PM
I'm using an access token... I get it from the UI at General Settings -> Access Tokens. Here's a screenshot:
... View more
06-15-2023
04:44 PM
I'm trying to follow these instructions: https://github.com/signalfx/splunk-otel-collector/blob/main/docs/getting-started/linux-installer.md ...I set up a Splunk trial, and have copied a new token that I created with all read accesses. I am using the UI here: app.us1.signalfx.com When I use the token from the UI that I got from General Settings -> Access Tokens to perform an action with the script I downloaded from the instructions, I get an error. I run this: sh splunk-otel-collector.sh --realm us1 Here are the results: $ sh splunk-otel-collector.sh --realm us1 Please enter your Splunk access token: BHwgwl0s32kbI227gUzORw Splunk OpenTelemetry Collector Version: latest Memory Size in MIB: 512 Realm: us1 Ingest Endpoint: https://ingest.us1.signalfx.com API Endpoint: https://api.us1.signalfx.com Trace Endpoint: https://ingest.us1.signalfx.com/v2/trace HEC Endpoint: https://ingest.us1.signalfx.com/v1/log TD Agent (Fluentd) Version: 4.3.2 Your access token could not be verified. This may be due to a network connectivity issue or an invalid access token. .......any idea what could be going wrong?? Thank you!! Jeff
... View more
Labels
- Labels:
-
OpenTelemetry
