Skip to main content

Data source connection methods

Reading time: 0 minute(s) (0 words)
Explore the difference between the agent and direct data source connection methods

For a complete picture of your system's reliability and effective monitoring, the first step is connecting your data source so that Nobl9 receives the time series data needed to process and calculate metrics. Nobl9 offers two data source connection methods: the agent connection method and the direct connection method.

Which method to choose? How do they differ?

While the Nobl9 agent underpins both connection methods, the direct connection method simplifies setup because Nobl9 handles part of the configuration process. This makes it easier to get started.

Both methods securely transmit data to Nobl9, but they differ in their connection approach:

  • Direct connection method: Nobl9โ€™s servers connect directly to your network to query your data source. This requires allowing inbound connections from Nobl9.
  • Agent connection method: You deploy the Nobl9 agent within your network for outbound-only communication. This eliminates the need for open inbound ports.

For most data sources, you can choose either method. However, some data sources only work with the agent connection method.

When configuring either method, you specify the data source and provide the necessary details, such as custom options like query delay or historical data retrieval.

Agent โ€‹

With this method, the Nobl9 agent resides in your infrastructure and acts as a secure intermediary. It fetches time series data from your data source to Nobl9 using only outbound connectionsโ€”a crucial feature when network security restricts incoming connections.

In a nutshell, adding a data source with the agent connection method involves two main steps:

  • Agent creation: define the resource you need to fetch data from and choose which Nobl9 features you want to use.
  • Agent deployment: authorize your agent to Nobl9 and set N9 environment variables you need (depending on your data source).

Direct โ€‹

The direct connection method eliminates the need for deployment. For this to happen, Nobl9 directly accesses your data source using the inbound connection. Make sure Nobl9 can communicate with your data source:

  • Open a port for Nobl9 to use when sending queries to your data source.
    So that inbound connections with Nobl9 are allowed.
  • Provide your authorization details.

Nobl9 encrypts your authorization information and adheres to strict security practices, safeguarding your data during transmission.

Additionally, if your organization restricts inbound traffic to trusted sources, you may need to list Nobl9 IP addresses. This ensures secure and authorized connection.

Nobl9 IP addresses
๐Ÿ’ปip allowlist
IP addresses to include in your allowlist for secure access:

If you're using app.nobl9.com instance:
  • 18.159.114.21
  • 18.158.132.186
  • 3.64.154.26
If you're using us1.nobl9.com instance:
  • 34.121.54.120
  • 34.123.193.191
  • 34.134.71.10
  • 35.192.105.150
  • 35.225.248.37
  • 35.226.78.175
  • 104.198.44.161

As a result, there's no need for further deploymentโ€”your data source is immediately ready for use.

Now you know the difference between the agent and direct connection methods and can select the one that meets your reliability, security, and observability needs