search

newrelic / newrelic-salesforce-exporter

New Relic integration for Salesforce logs.
Apache License 2.0
10 stars 16 forks source link

The integration does not throw an error, but does not send data to New Relic #9

Closed mmattos-newrelic closed 1 year ago

mmattos-newrelic commented 1 year ago

Description

I'm helping a customer set up the integration, but despite not generating any error logs, the data is not sent to New Relic. Only the configuration file (config.yml) has been updated with data from the customer's Sales Force instance and with data from the New Relic account. No other modifications were made to the rest of the source code. Could this be a bug, or is there something else that needs to be modified/configured?

Steps to Reproduce

  1. Code has been downloaded to the customer's local machine
  2. Configuration file has been modified with customer data only.
  3. Integration was performed as instructed in README.md

Expected Behavior

SF log information sent to New Relic and visible through the standard Dashboard available in New Relic I/O

Relevant Logs / Console output

Key: axxxxxxxxxxxxxxxxxxxNRAL Output: sent 50 log messages from log file Logout/0AT8L000003tiIDWAY RPM of the test account: 4004742

## Your Environment SO: Windows 11 Home Single Language - 22H2 Python: 3.11.14
miransar commented 1 year ago

Solution has been provided to customer. As discussed with @mmattos-newrelic, closing this issue.

asllop commented 9 months ago

@mmattos-newrelic could you please revoke the key axxxxxxxxxxxxxxxxxxxNRAL. Even if you edited the comment, everyone can consult the historic of changes and see the key you accidentally leaked. Please report once you have done it so I can remove the security alert.

mmattos-newrelic commented 9 months ago

Hey, @asllop . What specific action do I need to take? Do you want me to remove the historic of changes? Thanks!

asllop commented 9 months ago

Hi @mmattos-newrelic, just revoke that key, and create a new one if you need. The key has been compromised already, removing any historic (if it's even possible) doesn't change that.

mmattos-newrelic commented 9 months ago

Now I got it. Thanks!

Miguel Mattos Senior Solution Consultant +55.11.9.4203-4744 @. @.>



On 9 Feb 2024, at 05:27, Andreu @.***> wrote:

Hi @mmattos-newrelic https://github.com/mmattos-newrelic, just revoke that key, and create a new one if you need. The key has been compromised already, removing any historic (if it's even possible) doesn't change that.

— Reply to this email directly, view it on GitHub https://github.com/newrelic/newrelic-logs-salesforce-eventlogfile/issues/9#issuecomment-1935512982, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXVRDYZWESNL36R5QW47SWLYSXMX5AVCNFSM6AAAAAA32B4IHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGUYTEOJYGI. You are receiving this because you were mentioned.

asllop commented 9 months ago

Thank you! I'll mark the security issue as resolved.