Skip to content
This repository was archived by the owner on Dec 14, 2023. It is now read-only.

Conversation

olofbokedal
Copy link

I need to do this since some hosts block communication on non standard ports, e.g. 10000. But Logentries supports various ports, so this is easily avoidable by making the port configurable.

  • Removed the predefined constants.
  • Removed property for DataHub port.
  • Removed datahubPort argument from constructor.
  • Added port argument to constructor.
  • Return port property when calling getPort().

I'm not 100% sure about how the DataHub integration works, but this approach aims at keeping a single port for the entire instance by making it configurable via the constructor.

- Removed the predefined constants.
- Removed property for DataHub port.
- Removed datahubPort argument from constructor.
- Added port argument to constructor.
- Return port property when calling getPort().
Olof Johansson added 4 commits December 23, 2015 10:05
The address should be data.logentries.com for TCP connections, according to https://logentries.com/doc/input-token/.
The only supported port for TLS is 2000.
@StephenHynes7
Copy link

@olofjohansson sorry no one has looked at this sooner.

One thing I would like to see though is a default port to be used in case a user does not submit it. Ideally port 443 with SSL enabled.

private $use_datahub = false;
private $_datahubPort = 10000;

private $port = false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A default port should be specified (10000) to avoid breaking current usage.

- Added new parameter to constructor which sets the connection timeout to Logentires requests.
- The timeout parameter should be defined in seconds.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants