You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with Ryan we have a module that we built called the logshipper. This is the terraform module that references the cg-logshipper in order to get the cgov system logs sent to new relic.
The idea of this logshipper application is as follows:
Create a logshipper application
Bind any necessary services to the logshipper
Generate a logdrain sysurl
Bind the drain to the core running application
Stream the firehose to newrelic logs
Considerations:
a logshipper-network-policy will need to be created from logshipper to https_proxy
fluentbit.conf is custom for our application, though it does not deviate heavily from the upstream version.
We give the logshipper a dedicated s3 so that the logs can be stored in a dedicated bucket
New Relic credentials are stored as a cloudfoundry_user_provided_service and will need to be configured.
The logshipper uses its own set of HTTP_USER and HTTP_PASS credentials
Ticket is subject to change as this is a temporary placeholder to give a brief overview.
The text was updated successfully, but these errors were encountered:
As discussed with Ryan we have a module that we built called the logshipper. This is the terraform module that references the cg-logshipper in order to get the cgov system logs sent to new relic.
The idea of this logshipper application is as follows:
logdrain
sysurlfirehose
to newrelic logsConsiderations:
logshipper-network-policy
will need to be created fromlogshipper
tohttps_proxy
fluentbit.conf
is custom for our application, though it does not deviate heavily from the upstream version.s3
so that the logs can be stored in a dedicated bucketcloudfoundry_user_provided_service
and will need to be configured.HTTP_USER
andHTTP_PASS
credentialsTicket is subject to change as this is a temporary placeholder to give a brief overview.
The text was updated successfully, but these errors were encountered: